There are pros and cons to using a forge, same thing when not using a forge. Let's not forget you don't have to use one though. Also this piece mentions git bundles which I didn't know about, it looks interesting.
Nice exploration of the microcode patching flaw which was disclosed recently. This gives a glimpse at the high level of complexity the x86 family brings on the table.
Translation and localisation is a complex topic too often overlooked by developers. This is a modest list of widespread misconceptions. If you get in the details it get complex fairly quickly.
Another illustration that with race conditions all hell can break loose. It's not only about data corruption or deadlocks. This case is explored in depth which is nice, also compared across several languages.
Sure it makes generating content faster... but it's indeed so bland and uniform.
Interesting piece, we indeed need to move beyond from the "for hackers by hackers" mindset. I don't even think it was really the whole extent of the political goals when the Free Software movement started. Somehow we got stuck there though.
Looks like an interesting toolkit to make your own code checkers.
This is an important concept in Rust... but clearly it's harder to grasp than you'd expect.
Behind the movie this is a big win for Blender. It proves Blender is viable for full length movies at this point. The movie was nice too. :-)
Nice little Python trick using bidirectional generators.
Friendly reminder that AI was also supposed to be a field about studying cognition... There's so many things we still don't understand that the whole "make it bigger and it'll be smart" obsession looks like it's creating missed opportunities to understand ourselves better.
Makes sense, the "boyscout rule" has a psychology impact as well.
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.
Nice post explaining the need of ACPI or Device Tree and how they are leveraged by kernels.
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.
Or why you need to own at least some part of your infrastructure.
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.
Nice performance comparison of file handling in multithreaded context. It's surprising how slow MacOS seems to be there.
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.
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.