Good reasons to use [closed, open) intervals. If you didn't know where it was coming from, here it is.

Nice CSS trick to make collapsable trees without too much fuss.

A bit heavy handed in the way it tries to paint Root Cause Analysis as evil. Still it has good points about its shortcomings. In particular I appreciate the emphasis on complexity which indeed points to have contributing factors and unexpected outcomes. Definitely things to keep in mind for any postmortem efforts.

This sudden rise of the Fediverse is indeed a chance. Let's hope it's not wasted. Good list of things to pay attention to in this article.

I love this kind of explorations. Where does the term boilerplate code come? Let's find out.

Don't believe too good to be true marketing claims by vendors. Clearly something went wrong there and the benchmark has been gamed.

Interesting take of the cognitive overload in bigger teams which end up with more responsibilities. Indeed splitting the teams and the responsibilities can then be a way out.

There are indeed a few architectural problems with the Fediverse as it is. Can this be solved? Hopefully yes.

Interesting take about how performance optimizations can sometimes leverage even more performance gains than you would expect.

Interesting look at the perception of cellphones before they even existed.

Interesting point of view, also lays out nicely how social networks degenerated into social media. I appreciate this kind of perspective.

Success is a two sided coin. Clearly this mass exodus of Twitter users will overwhelm existing Mastodon users and a few instance administrators. It's understandable that is can be perceived as some kind of assault from people not used to the customs. How will the preexisting culture hold? The Pandora box is now opened we shall see.

Good thinking about the recent Mastodon users increase. Highlights fairly well why it's desirable, why it's a better social media platform but also the challenges ahead... including resources consumption.

A simplified mental model of complexity in software projects. It's not completely accurate but is valuable in the way it is easy to reason about it and probably use it for decision making.

Illustrated with Java, still this highlight fairly well the caveats of mutable collections in multithreaded code.

This is a clever and important use of =delete which I sometimes miss in other languages.

Interesting food for thought. Not necessarily easy to see it used in as many fields as the article claims. Maybe a bit too much on the techno solutionist side at times. Still, that sounds like an interesting guideline and path to explore.

OK, that looks like shell history on steroids. Definitely something I will try out.

OK, this is funny. Clear over-engineering non sense for the sake of it.

A good reminder of what's truly at the root of the container idea.