Journal

What we are learning

Technical notes, decisions we had to defend, and things that did not work.

Published
4 articles
Latest
October 27, 2026

We publish what we would have wanted to read: the reasoning behind a choice, the constraint that forced it, and the cost we only discovered afterwards.

Latest articleThe exit plan nobody writesEU law bans cloud exit fees from January 2027. It says nothing about your service provider, your repositories, your secrets or your domain name. Here is what an exit plan contains when you actually want to be able to leave.reversibilitymanaged-servicessovereigntycontractsRead the article

More articles

  1. Human and LLM: why mastering your software is still the best guaranteeA developer working with an LLM often produces more than a developer alone, who produces better than an LLM alone. But that ordering holds on one condition, and it is the one that matters to a client.aillmengineeringqualitysecurityUpdated October 26, 2026
  2. What a Kubernetes cluster asks of you the week after go-liveOn 11 December 2024, a telemetry service saturated every one of OpenAI's Kubernetes control planes for 4 hours 22 minutes, after a staging test that passed. Here is what a cluster asks for every week, and what going live never tests.kubernetesdevopsinfrastructureoperationsUpdated October 26, 2026
  3. External technical leadership: the decisions you can delegate, and the ones you cannotPast roughly two and a half days a week, an external technical director costs more than an employee. Here is the arithmetic with its assumptions, the decisions an outsider can genuinely settle, and the ones whose accountability never leaves the executive.strategytechnical-leadershipgovernancecomplianceUpdated October 26, 2026

Ready to take your technology back?

Tell us where you are stuck. A real person reads every message and answers within 48 working hours, with a concrete first step.

Talk to us