The ‘Boy Scout Rule’ and Kent Beck’s idea to “First make the change easy, then make the easy change” are probably the two most important bits of advice I received in my career.
I attribute most of my success to following those rules.
And maybe I’m just applying my own biases, but all the best developers I’ve worked with seem to follow those rules as well.
I love Gleam, but I would start with Elixir if you're interested in learning about how powerful the BEAM & OTP are.
There's not much documentation/resources around OTP in Gleam. When I was playing around with it I often found myself referring to the Elixir docs and then 'translating' that knowledge to Gleam's OTP implementation.
Gleam is still very new so this is totally understandable, and both are great languages so you'll likely have a lot of fun learning either of them.
Erlang is a much better language to learn if you're interested in learning about the BEAM and OTP, and the book "Programming Erlang"[0] is an excellent resource for learning it.
I've used Elixir since 2015 and in fact learned it first. I still think "Programming Erlang" is a much better book than any other for actually learning Erlang and BEAM/OTP principles. Erlang as a language is simpler, leaving more time and energy for learning the actual important bits about OTP.
DHH posts are starting to read like the ramblings of a mad man.
people who've traded in their Trump Derangement Syndrome diagnosis for a Musk Derangement Syndrome
holy tenants of the woke religion
the day-to-day antics of the meme lord at large
Maybe the political culture is different in America, but I can't imagine anyone in real life ever talking like this. And if they did, you'd have a real concern for their well-being.
This may sound a little odd, but I want to be more hedonistic.
I’ve spent my entire adult life up to now saving and investing so that I could buy a house. Now that I’ve done that it would be nice to indulge just a little bit.
> I have not reached the point of why aria label is code smell before giving up
The main point was that they often see it used to label non-interactive elements, when it should only be used for interactive elements. It's a useful point to make, but that's not a code smell, that's faulty code.
The author should have chosen a better title, e.g. "Think twice before using aria-label".
I attribute most of my success to following those rules.
And maybe I’m just applying my own biases, but all the best developers I’ve worked with seem to follow those rules as well.
reply