Ever wondered how to make a code formatter? This post does a good job showing the main problems you might encounter. The impact of Unicode is especially funny. Very interesting stuff.

Nice post. Explains well why the answer is not a number to target. You want to impact the distribution.

Nice exploration of the important areas in the kernel.

An evolving list of how to write idiomatic Go.

Interesting class of data structures with funny properties. Looks like there's a lot to do with them.

This is an important concept in Rust... but clearly it's harder to grasp than you'd expect.

Nice little Python trick using bidirectional generators.

Makes sense, the "boyscout rule" has a psychology impact as well.

A long piece which explore the reasons why Rust is likely not the best pick for enterprise software. It's niche is clearly system programming but beyond that and because of its qualities in that space it quickly become a sharp and dangerous tool.

Interesting endeavor... this is nice to have an attempt at a formal definition with no axiom introduced.

This is definitely a problem. It's doomed to influence how tech are chosen on software projects.

This is an interesting way to frame the problem. We can't rely too much on LLMs for computer science problems without loosing important skills and hindering learning. This is to be kept in mind.

A good reminder that you should always bring several perspectives when teaching something. This a a simple framework which can be used widely in our field.

Be wary of the unproven claims that using LLMs necessarily leads to productivity gains. The impacts might be negative.

Definitely a good list of lessons to learn when you're a junior developer.

Nice primer on the impact of too many branches in your code on the CPU. This is sometimes a good way to boost performance when you're mindful about that.

Nice trick for cleaner interruptible python scripts indeed.

A bit long and a bit too much framed in a "vs Python" fashion for my taste. That said it contains good advice on how to prototype or start simple with Rust. It's aligned with some of the advice I give as well. People tend to turn to low level details too quickly forcing themselves into a corner. There are better ways to handle it.

This is definitely a neat trick. This way you can flush stdout regularly without modifying the code of a command.

It's a not niche indeed but has its place in some applications.