It's written and illustrated in a C++ context, but the advice is widely applicable. You should know well the libraries you use on your projects.
Looks like the protocols landscape for writing LLM based agents will turn into a mess.
Or why it's important to deeply understand what you do and what you use. Cranking features and throwing code to the wall until it sticks will never lead to good engineering. Even if it's abstractions all the way, it's for convenience but don't treat them as black boxes.
Interestingly this article draws a parallel with organizations too. Isn't having very siloed teams the same as treating abstractions as black boxes?
Quite some food for thought here.
Nice docker recipe indeed for small and secure containers when you just want to ship a statically linked binary.
A nice example which shows the value proposition of Rust is not simply memory safety. Having a stricter type system and properly designed based types help a lot to catch mistakes early.
Good advice on how to learn Rust. I recommend quite some of it.
The ranges are improving in the STL. This is definitely welcome.
There are many opportunities to redactor. This one is aligned with Kent Beck's quote: "first make the change easy, then make the easy change".
This remains the best explanation of why we should have more use of auto in C++ code.
Definitely a handy catalog for designing distributed systems.
You have to know which battles to pick. If you don't... This article shows well what will happen. And it'll indeed turn into a curse.
Looks like a nice tool to navigate mistakes with Rust complex type system.
Even with conservative estimates some uses are very much energy hungry... Especially when they support a surveillance apparatus. Many reasons to not get there.
Little known docker feature but definitely useful for remote execution.
An excellent introduction to LaTeX! Also does a good job to push more modern constructs (I learn a couple). I hope it'll push people to pick up LaTeX more often, it mustn't become a dying art form.
A bit of an unusual view about cohesion. The approach is interesting though.
Nice piece, aren't we loosing something when we eliminate boredom from our life?
When hype meets group think, you can quickly create broken culture in your organization... We're seeing more examples lately.
I like this piece. In most case it's the thinking which is important not the writing. So even if the language is subpar it's better if you write yourself... except if it's not worth the effort in the first place.
Looks like the productivity gain promises are still mostly hypothetical. Except on specific limited tasks of course but that doesn't cover for a whole job. Also, when there is a gain it's apparently not the workers who benefit from them.