Doesn’t mean the author didn’t offload the task of writing to an AI. Also, Forbes blogs don’t have editorial oversight, only the official magazine articles.

Good article, and easy to follow. I learned more than I’d expected from this one.

Well, that was a thoroughly incoherent ramble.

What do you mean by “need attention”? What problem are you actually having?

Most stakeholders only need to hear about major milestones. They don’t get release notes. They get weekly or monthly memos on what the department is accomplishing.

Unless you’re developing open source or developer APIs/SDKs, end users don’t care about release notes. The KB needs to get updated, and meaningful feature improvements get announced in newsletters or blog posts every N weeks. A good customer experience team will take care of this based on raw release notes, and also notify customers who reported bugs when those bugs are fixed.

Engineers working on the product get raw release notes.

Engineers integrating the product ideally get something edited a bit to be maximally useful when working out how to upgrade — Django’s release notes are something to aspire to.

A lot of the ways we produce food are more environmentally damaging than they have to be. Runoff from farms that are careless about containing it and the use of finite aquifer water to grow water-intensive crops in desert regions being just a couple out of many many examples.

And we’ve all been regretting it ever since.

If you don’t know the language better than the LLM, you can’t notice when it’s making terrible decisions. Use the LLM to accelerate your ramp-up and make you more productive while learning, but it’s not a replacement for learning.

The most obvious value here is for HTMX, which requires a lot of partial templates.

Depends.

Who’s your user base?