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
Introduction Code reviews. For many developers, they are a necessary evil — a box to check in the development process. However, I have come to appreciate them as a powerful tool for elevating code quality, fostering collaboration, and improving team dynamics. Today, I want to share my journey from viewing code reviews as a mundane task to recognizing their critical role in successful projects. L
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
Building Translation Pipelines for Maritime Documentation — A Developer's Guide As maritime companies scale globally, they face a technical challenge that goes beyond just translating documents. Naval documentation involves complex terminology, strict regulatory requirements, and multiple stakeholders who need access to accurate, up-to-date translations across dozens of languages. If you're buil
Why your servers should die after every deployment How many times have you logged into production to "quickly fix" something, only to create a snowflake server that behaves differently than everything else? If this sounds familiar, you're dealing with configuration drift, and immutable infrastructure might be the solution you need. Immutable infrastructure follows one simple rule: never modify a
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
A pod gets created. It gets an IP. Then it dies. A new pod replaces it. New IP. Now imagine you have ten pods of the same app, and they restart all the time. Which IP do you call? You can't. That's the problem Services solve, and the answer is more interesting than "Kubernetes assigns a stable IP." This post walks the full picture in five parts: why Services have to exist, what happens when you cr