Profile picture
, 5 tweets, 2 min read
My Authors
Read all threads
Today I am working through the final written chapters for #ProgrammerPassport LiveView. Some of you have asked why we're covering so much Elixir in a program for programming language exploration

more >
Programmer Passport exists to help developers accelerate their careers by guiding them to make intellectual breakthroughs in computer science.

Call it guided curiosity.

Developers who hunger to learn progress faster. We nurture that.
Some breakthroughs are around *nuance*. Looking at different frameworks within the same ecosystem is a great way to reason about new things.

So I teach several wildly different programming models in Elixir because it helps developers understand nuance.
I choose a single language, Elixir, for these deeper dives because it fits the way I think, and that makes the teaching better.

Elixir is a great language for 2020 based on its vibrant ecosystem and excellent use of concurrency.
Groxio #ProgrammerPassport mixes in other languages because it's critical to also return to the beginner's mind, several times. Our most important skill as a developer is learning.

If you can do so and maintain a positive, open mindset, you'll experience more success.
Missing some Tweet in this thread? You can try to force a refresh.

Keep Current with Bruce Tate

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Related hashtags

#ProgrammerPassport

More from @redrapids see all

Profile picture
Bruce Tate
@redrapids
Long @elixirlang / @elixirphoenix tweet... beware.

1- Layers

In the Workerbee book, we recommend layers for do-fun-things with big-loud-workerbees (boundary).

The data-functions-tests in the core are often wrapped in a boundary.
2- Mappings of services

In a typical @elixirphoenix app, the layers are:

Services separate a functional core (schema(s) and pure-ish module(s) in a context directory)

boundary is in a *context*.

Changesets get created in an ecto *schema* and applied in a *context*.
3- Mappings of layers in a live view

- The *render*, either in templates or a render function, is in the *core* layer

- Handlers are boundary concerns... all data must go through a boundary layer, often a context.
Read 5 tweets
Profile picture
Bruce Tate
@redrapids
Goose bumps.

I am preparing my talk for India's FP conf and ran across some quotes from Joe Armstrong passage. I read them avidly. Bear with me as I list a few of them. Tweaked slightly to fit the twitter format.
“The next programmer we hire must read all of ‘A la recherche du temps perdu.”’
“All seven volumes?”
“Yes.”
“Will it make them better at punctuation and make them get their quotes right?”
“Not necessarily, but it will make them a better programmer. It’s a Zen thing....”
Knowing a small amount about many languages is a useful skill. I often find that I need to understand a bit of Python or Ruby to solve a particular problem. The programs I download... are often written in a variety of languages and need a little tweaking before I can use them.
Read 9 tweets
Profile picture
Bruce Tate
@redrapids
Struct wizards Activate!

#elixirnewbie

1. The shorthand sigil syntax is great for structs.

defmodule User do
destruct ~w[name email]a
end

The ~w is a sigil with an array of words; the trailing a makes these atoms; the [] instead of () is a valid use of delimiters.
2. Structs are maps, with one extra key:

u = %User{}
-> %User{email: nil, name: nil}
Map.keys u
-> [:__struct__, :email, :name]
u.__struct__
-> User
3. Structs don't implement any Map protocols:

u[:name]
-> ...User does not implement the Access behaviour
u |> Enum.map(f(x) -> x end)
-> ...protocol Enumerable not implemented for %User...
Read 5 tweets

Embed code for your website

×
Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!