This is a good praise for the work of maintainers. They're fighting off entropy and this should be well regarded.

This is something I've definitely seen indeed. There are clearly a threshold effect in the amount of code you have to manage. Solutions working at smaller amounts don't work anymore a couple of order of magnitudes higher, and vice versa.

Want to start a new project? Here is what you're signing for.

Indeed, if you benefit from Free Software you'd better engage with it. Maintainers should stop bending backwards to please free loaders.

Indeed, if we weaken the learning loop by using coding assistants then we might feel we go faster while we're building up the maintenance cliff. We need to have an understanding of the system.

Indeed, most complaints against "Don't Repeat Yourself" (DRY) are really arguments against a strawman. Of course you can go wrong, it's like everything else it's about balance... reducing the DRY guideline to a caricature to get rid of it won't help.

Nice automation for such updates. I'm discovering endoflife.date this looks very handy.

Interesting take on building software that lasts. I'm not sure I'm fully aligned with this but its good food for thought.

This stays true, most projects are maintained by a single person and that's a problem. Where is the support from all the businesses benefiting from FOSS?

The situation is still complicated for maintainers... And companies benefiting from their free labor don't get it. This leads to really stupid situations.

Nice little comparison of raw loops and ranges in C++. As always, measure before making assumptions... Unsurprisingly it ends up on the usual readability vs performance debate.

The whole field is unfortunately a bit fuzzy. That said, this article gives interesting ideas about what to pay attention to when writing code to ease the readability.

I like this. Sometimes a simple word can make all the difference in the way we behave. Code stewardship is indeed a better word.

People really need to be careful about the short term productivity boost... If it kills maintainability in the process you're trading that short term productivity for a crashing long term productivity.

This is a worthy questioning... We try to reuse, but maybe we do it too much? For sure some ecosystems quickly lead to hundreds of dependencies even for small features.

This is a good goal, I wish them luck.

There is some good advice in this piece. If you want to maintain something for a long time, some aspects need to be thought out from the beginning.

Definitely a good advice, I see very complex expressions in if (or while BTW) conditions way too often. They tend to accumulate over time.

Interesting approach to structure CSS custom properties. Should help a bit with maintainability.

Very interesting piece... shows how someone can end up maintaining something essential for decades. This is a lesson for us all.