An excellent article, that troubleshooting skill is really important in many fields... In particular software engineering. It's hard to teach and learn but it makes all the difference.

It like this parallel. The bigger the endeavour, the more complexity... And that will require thinking in very different ways for each order of magnitude.

Nice post explaining the need of ACPI or Device Tree and how they are leveraged by kernels.

Or why you need to own at least some part of your infrastructure.

Nice performance comparison of file handling in multithreaded context. It's surprising how slow MacOS seems to be there.

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.

I admit I'm more and more tempted to pay for my search service as well. It's unfortunately not FOSS... But it's not like the alternative are better there either anyway.

There's clearly a tension on that topic and the expectations from engineering managers tend to change over time. I like the proposed answer here and the distinction made between writing code and being in the code.