Technical subjects.
Answers you can decide on.
Content for executives, IT departments, product leads and the teams that build and operate their digital tools.
20 articles
Blog & analysis

CTO, squad or expert reinforcement: which model should you choose?
Three ways of working together, three ways of splitting responsibility. How to pick the one that matches what you are actually missing.
Read the article ↗
Production incident: what to prepare before you call
A short brief can save an hour on an incident. Here is what it contains — and what it must never contain.
Read the article ↗
RTO and RPO: asking the right business questions before the architecture
Two numbers decide your continuity architecture. They are defined with the business, not in an infrastructure spreadsheet.
Read the article ↗
Preparing a rebuild: the SEO decision checklist
Most traffic losses after a rebuild come from decisions taken too late. Here are the ones to settle during framing.
Read the article ↗
What does an hour of downtime really cost?
A simple calculation is enough to settle a continuity budget. You just have to count what matters, and only once.
Read the article ↗
An untested restore does not exist
Backups all succeed, until the day you try to restore. What a drill reveals, and how to run one without risk.
Read the article ↗
Migrating to Kubernetes without stopping the business
A successful migration is invisible. It is prepared environment by environment, switched in stages, and always keeps a way back.
Read the article ↗
Technical debt: measure it before raising it with management
Debt you cannot quantify stays a complaint. Translated into risk, delay and cost, it becomes a decision.
Read the article ↗
Hiring or bringing in an expert: what lead time really changes
Between a three-month hire and reinforcement within days, the difference is not only the calendar: it changes what you can hand over.
Read the article ↗
Private AI: what “sovereign” means technically
The word covers four very different requirements. Telling them apart avoids paying for a constraint you do not have — or forgetting one that matters.
Read the article ↗
RAG: why your answers are wrong, and how to fix it
When a document assistant gets things wrong, the model is rarely to blame. The problem almost always sits before it.
Read the article ↗
Automating a process: where humans must stay in the loop
Automating what is repetitive is easy. Deciding what stays validated by a person is the real design work.
Read the article ↗
Core Web Vitals: the three projects that actually move the needle
Many optimisations cost a lot and change nothing. Three projects concentrate most of the measurable gain.
Read the article ↗
URL migration: the redirect plan that avoids the collapse
Changing addresses is a routine and brutal operation. What makes it safe fits in four rules and one mapping file.
Read the article ↗
A fast website starts with less code
Before optimising loading, ask what needs to exist at all. Most pages ship an application in order to display text.
Read the article ↗
Taking over an existing project: the ten entry checks
Before writing the first line, ten checks say whether the takeover is feasible, expensive, or impossible as things stand.
Read the article ↗
APIs: evolving without breaking your integrations
A published API is a contract. Evolving it takes fewer versions than discipline about what is guaranteed.
Read the article ↗
Incident response: collect the evidence before cleaning up
Cleaning a compromised server without looking for the entry point guarantees a repeat. The order of the steps matters more than their speed.
Read the article ↗
Hardening an exposed server: the minimal list that changes everything
Reducing the exposed surface costs little and removes most attempts. Six measures, in order, and one frequent trap.
Read the article ↗
Paid search: connecting media budget to genuinely useful enquiries
An ad account optimised on the wrong conversions spends efficiently for a useless result.
Read the article ↗No article matches this search.
Let’s talk about what is blocking you.
An emergency, a profile to find or a project to structure: let’s start with your need.