Technical Beauty — Episode 34 Open the sudo CHANGELOG and search for the word "security". Make a cup of tea first. The list is rather long for a tool whose entire job is to ask three questions: who are you, what would you like to run, and may you. In July 2015, Ted Unangst grew tired of negotiating with the sudo configuration on OpenBSD and wrote his own. He called it doas: dedicated OpenBSD appli
Vendredi matin, 9 h 15. Françoise est dans son cockpit — trois écrans, à gauche l'Excel-pointeuse qu'elle tient à jour depuis quinze ans, à droite Sage, et au milieu Rembrandt depuis trois semaines. Sa tasse à la main, celle avec sa tête imprimée dessus que quelqu'un lui a offerte à Noël. Elle pivote sur sa chaise et me lance depuis son bureau : « Michel, combien on a d'inscrits pour la rentrée, d
« Hold on, we need to talk, this doesn't add up » Friday morning, 9:15 AM. Françoise is in her cockpit — three screens: on the left the Excel attendance sheet she's kept up to date for fifteen years, on the right Sage, and in the middle Rembrandt for three weeks now. Cup in hand, the one with her face printed on it that someone gave her at Christmas. She swivels in her chair and calls over from
Building a Translation Pipeline for International Contract Bidding If your company bids on international contracts, you've probably dealt with the translation bottleneck. Technical proposals need precise translation, certified documents have strict formatting requirements, and procurement deadlines don't wait for anyone. After seeing how UK public procurement translation requirements can make or
Practical post for engineers who've hit the wall where an AI proof-of-concept works on clean data but can't connect to the legacy systems that hold actual production data. Disclosure: I work at Ailoitte, which builds AI integration layers connecting legacy infrastructure to production AI. Sharing what the engineering actually looks like. AI models expect structured, consistently formatted data. Le
You write a detailed design doc. You paste it into your AI assistant. You wait. The output compiles. Tests pass. And yet — it's not quite what you designed. The auth middleware is in the wrong layer. The error handling pattern differs from the rest of the codebase. The field names don't match the schema. You fix it. Next task, same thing. This happens constantly, and it's not a model capability pr
Go is a compiled language — the code is converted into machine‑readable form before execution. From a beginner’s perspective, this means Go catches many errors during compilation, giving you cleaner, faster, and more predictable performance at runtime. Go is widely used for: API development CLI tools Microservices architecture Backend server. DEVOPS activity So it fits perfectly with the kind of
If you've tried building an AI agent in the last six months, you've hit the same wall: there are half a dozen frameworks, each with a different philosophy, a different API surface, and a different definition of what an "agent" even is. I spent a weekend writing the same simple agent — "read a GitHub issue, classify it as bug/feature/question, and post a comment" — in six different frameworks. This