Interesting approach to gauge how accurate a profiler is. With some results in the Java ecosystem, so now you know which profiler to pick there.

It's a bit of a sour article but it rings so true... We let Open Source take the mantle in companies which are mostly free loaders and churn closed products, or even worse have them closed and DRM protected. There's really quite some work to still realize the Free Software goals.

A reminder that if there's too much complexity in your configuration the syntax used to represent it probably won't save you from issues.

Interesting tag... It's indeed been totally forgotten somehow.

Apparently people need to be reminded that "Don't Repeat Yourself" is more a guideline than a rule. So "The Rule of Three" is a way to do that (although I find ironic it's called a "rule").

It's kind of an unusual design choice... This is subtle, I think I'm still a bit on the fence regarding this one.

Well done everyone. This bullet was dodged... for now! This kind of fever comes back regularly unfortunately.

An illustration of why C++ can still be a relevant choice in new code. It all depends on the contraints you have for a given problem.

First rough benchmarks for CPython 3.14. It looks like the JIT isn't giving much improvement on the cases explored, the free threading on the other hand is a clear advantage for multithreaded cases. Of course as usual Pypy is still way faster. That said, like anything else: first measure in your own context before taking any decision.

Some relationships here are definitely shady. Be careful who you trust with your traffic.

It's out now, this is a big one with quite a few interesting features. Let's see how it's used in practice.

This is indeed an open question. Looks like it has the potential to lead to interesting boards in any case.

Interesting view... This explains quite well why most organizations have both formal and informal processes. I'm not sure I agree that the informal will always be fought against by management though. I've seen clever management which accepts the informal processes as long as it doesn't harm the organization.

I'm a bit on the fence regarding this article. That being said there's something I like about it: it's not always purely about money. It's also a good reminder that if the reward is in monetary form it's almost impossible to not somehow alter team dynamics with it.

I wouldn't frame it as always superior (I'd argue the article falls a bit in this trap). Still this can sometimes be an alternative to driving everything purely on project mode. Some organizations would benefit from such a change of perspective other less so.

This is definitely a skill which is hard to teach an learn. When it sticks it brings really nice results though...

Reminder that there are a few cases where you might not want your variables declared as const.

An explanation about where the SRP comes from and what it really means. It's very often misunderstood or overlooked.

I think the Open Agile Adoption ideas have been unfortunately unnoticed. It's thus hard to tell if it would have been fairly efficient. What's sure though is that the widespread mandate approach used during the past decade does a disservice to teams.

A bit old but still relevant. Don't focus on tools or the fashion "du jour", instead have a set of timeless principles and evaluate your work against them.