shinzui

What a waste of tokens.

It’s amazing how many of those types of problems are easily avoided or solved with event sourcing and CQRS.

The premise of the article is flawed. I read a lot of code, and that's how I learn and discover new things.

Because TypeIDs are compatible with UUIDv7 and are supported by libraries in many languages.

Hurl is better than any of those GUIs. You can version your Hurl files and use them for CI/CD.

The title should have been breaking up with Angular. I posit that they would have had a much different experience using react with relay and graphql.

Lens is one of my favorite libraries, but I can understand why optics, in general, is a divisive topic. Like many things in Haskell, you won't appreciate optics without suffering through a steep learning curve.

Optics don't just save you a few keystrokes. Instead, they make tedious code that you would never write trivial. And more importantly, they're composable. So it's impossible to appreciate their effectiveness without using them on a real-world app. For example, I've worked in an app with three layers, each with its record types, and without the lens library, the pain of converting between records would have been insufferable. Instead, most developers would couple the three layers together to avoid the problem, which makes the codebase brittle.

DDD offers a lot of benefits regardless of the programming paradigm. We heavily use DDD in Haskell.

DHH’s preferred architecture is a rails monolith with a single database behind it that you keep scaling vertically. I believe both Hey and Basecamp are still using that architecture.

It's worth noting that Basecamp's architecture relies on vertical scaling, which can get very expensive in the cloud.

DevOps (the term), like Agile, made sense when it was introduced but lost its meaning as the industry evolved.

I use nix-darwin to automate that.