It's just impolite to point your flaws. Of course it makes etiquette harder to learn as you don't notice. This is a small list of things to pay attention to. Liked the writing as well.

An important piece in my opinion. Obviously with my political leaning it all feels to me like it was just a question of time before we got there. Still it's valuable to read this kind of insider views.

Another interesting type introduced C++26. This should make it easier to deal with owning polymorphic types at runtime.

Go read the full paper of course, but in case you won't this is a quick summary which kind of does the job. There are obvious limitations to the study: most notably time as it's only a few minutes use each time. And yet that raises clear questions on longer term use... There is clear recovery after a few minutes but does it still exist after weeks or months of prolonged use? How fast would it be? Clearly we don't know yet.

Interesting account of Zotero history. Another venerable software which passed a nice milestone.

It doesn't have to be something mysterious indeed. It's a skill one can learn.

A good list of the things to keep in mind and prepare in case everything goes wrong and someone else need to take over the services you self host.

Interesting essay even though I don't like the whole part about singularity. I found this section was a distraction to the more interesting arguments. Indeed, I liked a lot the concept of decoherence and its ties to complexity.

The essay also makes a good job of showing how it's something we have to deal with and likely the worst kind of technical debt. I also shows how it impact productivity obviously. It's all valuable and things I encounter on a regular basis.

And of course, since everything has to talk about LLM these days, it build an interesting case on how and why using those tools especially with harnesses to pump out more code is actually increasing decoherence. Exactly what we don't want.

This is unfortunately a common default choice indeed. I wish it wasn't though. People using it are locking themselves in a sub par offer for a financially driven convenience... If they'd account for the impacts they'd realise it costs them way more than they think.

This has a satirical undertone but it has a very good point. Those companies are just sucking the life out of very human activities.

Nice resource listing many tools available around RSS. Plenty to choose from including self-hostable options (but not only).

Looks like a very neat setup. Probably a few good ideas to borrow in there.

The article equates effort with lines of code a bit too much for my taste. That said I think this model can be useful to describe how maintenance works in a given project.

Unexpected metaphor but it kind of works. Indeed, architecture work is expensive, that doesn't make it unnecessary.

I'm not agreeing with some of the points in here. That said the core position of "it should be about collaboration not automation" I'm very much aligned with. It's after all at the center of how we designed AI systems in my team twenty years ago. We really wanted systems helping the user in their task and so co-constructing the result with the support of the machine rather than some kind of "oracle"

Or how Amazon manages to enshittify things even outside of its platform...

Between this and the scrapers behavior... the disregard for infrastructure and best practices is obvious. It's just another externality those so called "labs" don't want to deal with. And well, it makes for a marketing stunt each time isn't it?

Unfortunately it's true. Terrible bosses are generally the one who can't handle feedback and so won't change.

Looks like connecting everything isn't the best idea after all.

Interesting opinion piece on how autocracies benefit greatly from the current AI arm race. But the short term benefit will also create new weaknesses.