Post

Adding an LLM to the mix is like adding a gambling layer. Maybe next time you win the jackpot. 🎰

so yeah, the tooling, the packaging, the deployment, so many patterns to context switch

I think rust is a bad example for that particular point because its use is to expose and formalise complexity that already exists, rather than create it where it otherwise wouldn't. Writing correct unmanaged code is *hard*. Scala definitely tries to elide complexity though

It's almost a bad dream that we used to have to manually declare and initialise our dependencies, and then wire them manually together in XML. But we just moved the complexity elsewhere.

Java Enterprise Edition was first released in December of 1999. ¯\_(ツ)_/¯

*me looking up how to open a file properly in {{some_language}}*

Note that the applications themselves largely haven’t gotten more sophisticated. 99% of apps are lists of stuff from a database with CRUD operations.

I feel increasingly like an old crank but I've been saying for decades that if you can't read and write the code in a text editor then it's too complex. I'll admit to a sliver of hyperbole, but I think it stands up practically too when taking into account abstractions that only leak in useful ways.

And there are CRUD frameworks in many major languages but I'm not 100% convinced they're that much easier than using connection strings and SQL. Sure, for user management, no one should build that from scratch, but other things? 🤔

... which puts things that matter, like f. e. architectural skills, deep into the background.

For me the tools had a sweet spot some years ago. The languages and frameworks I use haven't evolved that much, but got a bit more convenient. But in the same time the tools got worse, slowing me down, get indeterministic UI, so I really have to concentrate and be careful. Weird.

Well put.

When they work, they correctly express the intent of a highly compressed statement as code edits. Then again, that is of course also how and where they fail ;)