The blog · since 2015
Essays, playbooks and field notes from our CTOs, architects and leads. Written for people shipping real product.
Handing an AI your engineering conventions cleans up the code without fixing the architecture. A 5,000-line god class shrank to 500 lines across tidy domain files, and an independent reviewing agent still returned FAIL: authority never left the central object.
Handing an AI your engineering conventions cleans up the code without fixing the architecture. A 5,000-line god class shrank to 500 lines across tidy domain files, and an independent reviewing agent still returned FAIL: authority never left the central object.
Becoming AI-native in three years does not need a three-year technology roadmap. It needs a usage policy, a map of your data, one bounded experiment, and both the enthusiasts and the sceptics in the room. Build the ability to change, not the overhaul.
Infrastructure documentation goes stale because it is a second thing to maintain. Terraform plus cloud discovery plus a few query tools describes the system better than any diagram, and leaves humans to document only the why behind the odd decisions.
Hitting a wall with AI usually means hitting the wall of the chat box, not the wall of AI itself. Give a model memory, tool access and a browser, and the interfaces we built for humans become the integration. The bottleneck stops being the model and starts being your imagination.
Sentry silently drops transactions that blow past its span and payload limits, so the heaviest background jobs are exactly the ones missing from your dashboard. Capping span count and truncating span descriptions on bytes brings them back.
An AI-assisted note system captures faster than you can understand, and the gap compounds into internalisation debt: a dense graph of links attached to a thin mental model. The test of a knowledge base is not how much it holds, but how much you could still explain with the file closed.
A practical guide to evaluating fractional CTO providers in Belgium: the three criteria that matter most, how the four provider types differ, what an engagement should cost, and when a full-time hire is the better call.
Teams accrue learning debt when shipping always beats getting better. It stays invisible on every dashboard, compounds fastest under AI-speed change, and quietly caps the ceiling a buyer is willing to price.
Synthetic checks like curl and Lighthouse measure a request your users never make. A HAR file captures the real logged-in flow, and handed to Claude alongside the codebase it turns a wall of JSON into a ranked list of fixes that get implemented in the same conversation.
A back-end engineer set out to redesign a React app with an AI agent and came out actually knowing React. The unlock wasn't the prompting, it was understanding the code well enough to steer it. As the cost of entry collapses, knowing the technology matters more, not less.
A good technical due diligence report is smaller than you expect, separates fact-checked observations from labelled judgement, and answers the specific questions your deal depends on. No score. The real test: does it change what you do on Monday morning?
Analytics only shows the events you remembered to add, never the ones you forgot. Let Claude instrument features as it builds them, then run a skill that audits your tracking against your own docs and live data, flagging what's missing, noisy, or quietly broken.
Integrating a tool with Claude rarely needs an MCP server. A boring script wrapped as a named, version-controlled skill does the job, and the real value shows up when two skills combine: one tool tells you what happened, another tells you why.
17 lock-wait timeouts in two hours. The SELECT was doing exactly what it was supposed to. The problem was what InnoDB did silently in addition: a gap lock on the write path, invisible in logs, invisible in EXPLAIN, visible only in production.
Writing code by hand used to be the job. Soon it will be a hobby, like woodworking or growing your own veg. What a company pays for now is judgment: knowing what to build, catching the answer that looks right and isn't, deciding when it's good enough to ship.
AI & agentic tooling
We use AI and agentic workflows daily. From coding agents to AI strategy, we help teams adopt what actually works.
Read our AI insightsEngineering leadership
We <3 sharing content for CTOs, senior engineers and founders with real-world insights.
40+ expert authorsFor investors & VCs
Technical audits, codebase assessments, and risk analysis for portfolio managers making investment decisions.
Explore our investor content
Our staff engineers will get your software (back) on track and lead your engineering team. We prepare our exit from day one: our goal is to bring the software and the team to the right level for us to get out again.
Learn more about software engineeringOur CTOs in residence (or fractional CTOs) inject technical leadership into your team, ensuring the technical aspect of your business gets exactly the right attention.
Learn more about CTO as a serviceWe're the market leader for technical due diligence of SaaS companies in Belgium and The Netherlands, servicing clients all over the world. Investors appreciate our smooth process, sharp opinions and top-notch reports.
Learn more about auditingBehind-the-scenes support for your CTO or technical lead to enhance their skills, drive effective change, and grow their teams confidently.
Learn more about CTO coachingWe can help you find the best talent to join your team. Unlike other recruiters, we are CTOs and software engineers ourselves, and through getting our hands dirty, we know the skills required to make an impact.
Learn more about recruitingSometimes your struggles go beyond the technical. Do you need help evaluating the roadmap or sharpening the vision? What should you build in order to scale? Our product management experts know the way.
Learn more about product management
