Insights

Analysis, learnings and perspectives on IT transformation, artificial intelligence and modern architectures. Written by consultants who implement these technologies every day.

Featured

Developer working with specifications and AI-assisted code across multiple screens

SDD (Spec-Driven Development): the methodology that turns AI into controlled, predictable code

Latest articles

White desk with a stack of printed documents under a navy folder and a closed laptop, while in the background an out-of-focus person seen from behind, carrying a backpack, walks out through a glass door at dusk

Engineers deployed at the customer's site: the question is not who comes, but what stays when they leave

Two printed sheets on a white desk, one with several lines underlined in navy ink and the other unmarked, with a pencil between them and an out-of-focus person seen from behind by the window at dusk

A public tender technical proposal example, annotated paragraph by paragraph

On a white desk, a stack of technical drawings held by a navy binder clip, a small brass balance and a blank ruled index card, in a row: the specification, the check and the example

SDD, TDD and BDD: what each one adds when an agent writes the code

Diagram of three layers: a light grey sheet of text that the agent reads, a list of permissions with a padlock and a navy barrier that stops an action before it runs, in blue and navy on white

Claude Code for teams: CLAUDE.md is context, not control. What must be enforced goes in settings and hooks

Diagram of an automated judge: a grid of cases enters a navy bar; one lane leaves with automated checks and the other with a ticked box next to a person signing, in blue and navy on white

LLM-as-judge: when to trust the judge and where a person has to sign

A development team's desk at dusk: one screen shows a pull request's automated checks, the other the dashboard of tests that run overnight

Evals on every pull request: what runs per PR, what runs nightly and what it costs

A product team's worktable: a printed specification with its acceptance criteria ticked off and a laptop showing the approved merge review

Your spec is already an eval: turn acceptance criteria into the merge gate

A long engineering work desk with four laptops in a row, each showing blurred code on screen with a printed document beside it, nobody present, at dusk

Leadership4 Oct 2026

The four perspectives of a development team working with AI: people, processes, tools and indicators

A bound printed document with a pen on top, next to a laptop with blurred code on the screen, on a wooden work desk at dusk

What a software development tender should ask for so that AI reaches the code

A senior developer points at a line of code on the monitor while a junior developer at their side thinks through the answer: a code review session at dusk

Leadership3 Oct 2026

Junior developers and AI: the agent writes the code and nobody learns to review it

A security engineer checks a row of open laptops at dusk in an empty office: taking inventory of the MCP servers each person on the team has configured

MCP servers: the integration that gets installed without going past anyone

A developer compares an old code listing printed on continuous fanfold paper with the same module on screen, at dusk in an office: specifying the behaviour of legacy code before an AI agent changes it

Before an agent touches your legacy code: specify what it does, not what it should do

Two developers review a pull request together on a monitor during a technical interview, one pointing at a line of code, in an office at dusk: hiring developers who can review the code AI generates

Leadership30 Sept 2026

If an agent can pass your technical test, you're assessing the agent: what to measure when hiring developers

A civil servant goes through a paper case file, pen in hand, while reading a draft on screen in a public office at dusk: human oversight of AI in public administration

Why giving AI to every civil servant doesn't improve productivity (and what does)

A hand turns a metal knob on a dark control panel at dusk, a metaphor for the default effort level that changes in Claude Opus 5.5 and explains part of its cost reduction

Opus 5.5: what really changes, and why 40% isn't your number

Contact

Want to put these ideas to work in your team?

Let's talk about how to transform your organization with AI, DevOps and modern architectures.

What happens next

You write to us. Two lines are enough.
We reply within 24 working hours and set up a call.
On the call we tell you whether we can help and where to start.

Prefer to talk? Call us 682 384 429

Tell us what you want to solve

Tell us who you are and what you need.