A bit dated perhaps, and yet most of the lessons in here are still valid. If performance and parallelism matter, you better keep an eye on how the cache is used.

If you expected another outcome on the average developer job from the LLM craze... you likely didn't pay attention enough.

Another example of attack vectors emerging with adding more and more LLM agents in the development process.

Interesting advanced features of GraalVM to better manage the memory of complex Java programs.

Not only the tools have ethical issues, but the producers just pretend "we'll solve it later". A bunch of empty promises.

An honest attempt at "vibe coding"... but once again the conclusion is "when it grows to non-trivial size, I'm glad my experience allowed me to finish the thing myself".

Both TDD and design docs complete each other well indeed. They just don't focus on the same activities in the project. That said, both later provide important insights on all the decisions taken to produce some code.

LLMs are indeed not neutral. There's a bunch of ethical concerns on which you don't have control when you use them.