This is an interesting metaphor. I'll try to keep it in mind.

Interesting conservation work. Video games being part of our culture, especially indie ones, it's important for such work to happen and be funded.

Nice reasoning. It very well highlights the tradeoffs coming the choice they made. And of course the decision might change if the situation changes.

A bit sarcastic, but makes its point efficiently. It's important to realize that more code to maintain is definitely not what we need.

Definitely this. I think this could have turned into a good term until it was used for everything under the sun. It's about maintainability first, not just about what you like or not.

Good musing about simple code and complexity. We definitely should avoid unwarranted complexity in our code, or at least try to prevent it's spreading.

Nice list of things to keep in mind when working on projects, even small personal ones. This greatly improve maintainability in the long run.

This is definitely well put, users shouldn't feel entitled. Maintainers do what they can (even if there's a company backing up your favorite FOSS project) and if you use the software for free with no support contract... things will be done when they're done.

Good reminder of why "tech debt" is not a so bright metaphor. I find it useful sometimes but clearly it became overused in the industry (often a sign of something loosing its meaning whatever it was). That's why lately I'm talking about complexity, some of it being legitimate so you need to keep the illegitimate one at bay. I like the focus on maintenance in that post. Also there are a couple of good ideas on how to schedule the maintenance tasks in your project.

Interesting simple exploration. This seems to confirm that there's a lot of hype all around. Whatever the language, even if it is hot today it probably won't look as fun tomorrow when you'll have to maintain millions of lines of it.