>learn the meaningful stuff, you will never code in your job implying the code that can be thrown away is the code they get paid for hmmmm

> The idea began with two friends reading together at a bar in San Francisco, annoyed by the assigned reading of a demanding book club. Because everything was invented in San Francisco in the last 20 years.

Touch screens are awful for operating while you focus elsewhere. I miss touch typing and I sure like adjusting car controls without looking away. What's that, trust driverless cars you say? Never, and the basilisk be damned.

https://www.youtube.com/watch?v=jdaPJLJCK1M&t=6s remember that anyone can manipulate these algorithms

You forgot the rest of the title.

Fantastic tutorial: http://learnyousomeerlang.com/book

That's mostly it. Personally I find Elixir's syntax confusing. For example:

Losing the ; and . function endings from Erlang you can put same-named functions throughout your module. I tried doing

def create def handle(:create)

def update def handle(:update)

But the compiler warns. So that loss isn't helpful.

Atoms require a : because variable names are lowercase.

Uppercase variable names and lowercase module names is easier to read in Erlang.

The syntactic sugar is too clever for readability imo.

The package management through mix is decent. I used to use an erlang.mk file, looking at hex it looks like the Erlang ecosystem is quite evolved.

Phoenix + Ecto seem to be very actively maintained, useful if you're writing web apps.

When I tried Cowboy a few years ago some of the documentation was out of date, so that's a point in Elixir's favor.

> Uppercase variable names and lowercase module names is easier to read in Erlang

This is ENTIRELY subjective and not a rational argument. It's in fact the exact opposite for me, but my prior language was Ruby.

Well at least you aren't mad enough to revolt because then change might occur. Ah right, revolt is impossible due to economic conditions.

Hah. I interviewed for a [growing in popularity and market share] top 20 cryptocoin. They had some curious choice of words in their "freelance" contract, notably that it would use German copyright law to transfer rights of all inventions I ever made.

I pointed out that a couple of the phrases in the contract, when combined, indicated they would have IP rights to EVERYTHING I did not just work they paid me for.

They moved on to another candidate.

> Hah. I interviewed for a [growing in popularity and market share] top 20 cryptocoin. They had some curious choice of words in their "freelance" contract, notably that it would use German copyright law to transfer rights of all inventions I ever made.

IANAL but I really doubt that would be legal under german IR/IP laws.

Things like this motivate me to stay in California and work for small companies for the rest of my life, so that California Labor Code § 2870 applies and I get to keep the rights to independent inventions if I'm careful.