A very uplifting essay in my opinion. Starts with a historical perspective on the webmaster role to then evolve into a manifesto about creation on the web.
The executive summary is good. This is also a nice source of reference papers and studies on the topic. It shows quite well why the work is moving to the harnesses rather than the models. Indeed models probably won't improve much in terms of reliability. It all points once again towards a needed shift of people attention from the shiny toys and towards team practice instead.
Neat trick to monitor systemd services.
Very good opinion piece going back to Naur's and Brook's important papers about software production. It's a sobering take on how LLM can't bring the promised productivity gains. This is not saying it can't bring productivity gains of course but it'll never be as dramatic as what the current hype cycle pushes people to believe.
I like this article somehow. Indeed I'd like to see more guilt in the people shipping bugs in production (myself included probably). Also I'm very much aligned with the proposed approach to tame issues: thinking, types, tests, and telemetry.
A good piece showing some of the problems with how the term technical debt is widely misused. There's a problem with the metaphor itself, you rarely have the information level needed to call it debt.
Interesting slide deck about coaching in tech circles. Clearly provides good inspiration both for coaches or if you're the one requesting to be coached.
Excellent piece about code reviews. But it goes further than that and shows how our skills could improve. By tackling this question it does a good job showing we don't know where the ceiling is in terms of skills in our craft.
A nice and simple approach to sandbox a command. Of course with the system integration it's a bit porous bit it might be a good base for quite a few uses.
When more concurrency might not help. Illustration with the case of database queries.
Careful how you use DISTINCT or ORDER BY on very large tables. You might want to reevaluate (after checking if there's a problem of course).
Interesting tool. Maybe more chances for C++ and Rust hybrids?
Another nice addition to the standard for dealing with embedded assets.
Yes please! The amount of email system which get it wrong nowaday is really kind of sad.
Interesting policy. I think it strikes a good balance.
Indeed, so many things to do to deter bottom feeders. Lots of good funny ideas in there.
Long and nice guide about watchdogs in an embedded context.
This campaign is definitely worth a try. Hammering people with cookie banners exhibiting dark patterns isn't exactly a good way to seek people consent.
Indeed Atom is a better standard than RSS for feeds.
And indeed that makes it as important as the final product.