Shows the problem with layer cakes in applications or how you might want to go toward onion architectures.

Examples of how i3 and go stamp versions. This is indeed good habits to ease dealing with errors in production.

Cryptic title to be honest. But this is a good explanation of why any "agile transformation" better start close to the code and in particular with automated tests. If you can crack that nut (and it take time), the rest will follow naturally.

Excellent piece, it show quite well the problem of skipping the "grunt work". Without it you can't really learn your trade (be it astrophysics or anything else). It also shows how the incentives on scientific careers are wrong. It's not new, but when LLM agents become available, things are definitely changing for the worst.

So much this... There are so many organisational problems that churning code faster is likely not what you need. When did we start to obsess with the number of lines of code?

A friendly reminder that one can go far mainly with awk.

It feels like it's supercharging an old bias... We tend to confuse confidence for competence.

Real innovations come from constraints. The frugal AI movement is clearly where we will see interesting things emerging. Interestingly, those approaches are closer to what AI is about as a research field than the industrial complex which got unleashed with all its extractive power.

The price hike on RAM due to the LLM as a service bubble is really killing interesting fields. Can't we have nice things? Will the arm race end soon?

You got bluray discs to encode for use on your NAS? This looks like a nice option.

Are you sure your understand how your reverse proxy works and the impacts it can have in production?

A good reminder of why destructors shouldn't throw. It really has to be a last resort measure and only carefully considered. There's a reason why they are nothrow by default since C++11.

Are we surprised? Of course depends on the browser and they're looking mostly for extensions. Clearly they try hard to map what people use, it's corporate espionage.

Git bisect won't help much for flaky tests... but maybe this bayesian approach can.

Interesting color coding for hex editor. It indeed brings interesting properties.

Indeed be careful at how you use strings when interacting with C APIs. String views are likely not what you want in that context. There is a reason why they don't have c_str().

Vendor toolchains should see only a limited trust. Like in this case they're often partial or old.

You're self-hosting? Better keep in check what happens to the people who depend even indirectly on your services when you're gone.

Interesting article which goes deep in comparing joins vs denormalised big tables. The conclusion is in the title, bit it's worth a read for the other insights.

I vehemently agree with this piece. Fakes are unfortunately underrated. They're the most powerful test double, I wish more projects would invest in them (can be quite an investment, which the article doesn't quite show unfortunately).