I usually ask gpt4o as my ref doc.

The opening screen in this game is why I ended up working at IBM for 8 years.

Yep. The problem with the story of bikeshedding is that it assumes people know bike sheds but not nuclear reactors. There are plenty of cases of people who are great at nuclear reactor design but have no idea how workers should park their bicycles.

I was big on Rails scene when it was huge in 2008, and saw a big exodus from it. I found so many of the "Rails" problems were solved by learning two languages: ruby, and sql. People would go to crazy lengths to avoid looking at the queries they'd actually run. I can admit to not really learning ruby as a language by itself, and can now see how much better my old code would've been if I wasn't just blindly shoehorning Railscasts in there.

Similar problems for people who learned angular but not typescript, laravel but not php, etc.

Crypto "currency"

I absolutely loved this article. Super well written with interesting insights.

That is very kind - glad to hear that you enjoyed it.

I'm the same camp. I use async/await because they exist and it's usually a good idea to use similar approaches to other devs, but I question why we even needed async/await in the first place. It's a big deal to add syntax to a whole language, and a small one to add a function to a library. We have

  const foo = async function() {
    const user = await fetchUser()

But if they'd just made a Promise.coroutine, you could equivalently do this without needing to change the language:

  const foo = co(function* () {
    const user = yield fetchUser()

There's some unpopular cases like async iterables or async generators, but for the most part we could've done the same thing without extending the language. I remember the v1 of koa that had yield everywhere and people thought it was confusing af. Then they released with await and suddenly it made sense to people.

Interesting take. One could argue that by adding async functions on top of classic and generator ones we now have three different colors for the functions instead of just tw.

Async await is a syntactic sugar for functional continuations. These are “free” for C stacks, in a sense. Coroutines are not, because you have to yield and resume across C calls sometimes. The common argument for async await is that you avoid making system interfaces resumable. Another argument is that await explicitly marks yield-across points and there’s no sudden yield through an incomplete or potentially unsynchronized state.

Probably why LotR translated so well into film, while Dune is very hard to capture in live action. The first book at least has some big battles and over the top villains to anchor the whole thing. Children of Dune is like 90% discussing religion and its appropriate role in government. Especially all the chosen-one tropes that are fun in a movie are pretty brutally deconstructed in Children.

Everyone gets murdered, commits suicide, transformed into crazy magic people or giant sandworms, or repeatedly dies then comes back in different forms over centuries.

LotR had them do a bunch of hero shit, then everyone either went home to hang out at the pub for a while, or took a boat out west.

Lukecool is perfect for my wife. She gets acid reflux very easily and needs to drink ice cold water always. Needing to describe an offending glass of water as "not ice cold" is clumsy and inaccurate, but saying it's lukewarm is inaccurate. Lukecool works for that range where it's definitely cool, but you could put your finger in it and reliably tell that it's well above 0°.

You could say “chilled water”

Chilled sounds pleasant. The utility of lukecold is you're saying it's cold but not cold enough.