Short and to the point reminder: our job is never only about the tech. It always encompass some people related concerns, be it inside teams, between teams, or the impact on the users.

Comprehensive guide to have SSH keys stored in the TPM chip. Clearly it's still a very manual process.

Well, what can I say? This is excellent news and I'm excited to see it happen. Let's hope more governments do the same. It'll take a while of course, so we'll have to be patient.

The stats are clear there. Beside in term of experience, RSS feeds are so superior to newsletters... I wish more bloggers would give up on the newsletter focus. There's also a good point in this post: as soon as you have a newsletter you will sit on a database of email addresses, it's definitely a liability.

Long but very precise piece about why you can likely ignore LLM for development purpose. Starting from older Fred Brooks work is spot on. Indeed whatever will remain of LLM based tools in the years to come, it's much smarter to focus on fundamental skills than chase the new tools. At least, I'm trying to do my share in getting myself and others better at the craft.

Nice little commands to use to discover quickly the state of a code base... Or rather of its team.

Definitely interesting approach. I think neurosymbolic approaches are what we ultimately need so I'm probably biased. At least it means using LLMs for what they're good at (language skills) and only that. Then rely on proper code symbolic models which do the reasoning heavy lifting. I'd expect it can give nice output with smaller models.

Oh this is super neat and convenient! I didn't know about those glob patterns modifiers in zsh.

Lots of interesting measures to reduce the risk of supply chain issues. Definitely to be considered on your projects.

So many string types! They all have a purpose of course. It's a good reminder that something mundane like a string type is not that simple.

Failing DRAM chips are real. Here is the case of debugging a single bit flip.

It's getting clearer that the industrial LLM complex will have a hard time meeting its targets.

Indeed, the giant managed to make itself weak. This means opportunities for other ecosystems to grow faster than before.

A good explanation and illustration of how natural monopolies work. This is why you want to regulate infrastructure properly.

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.