A/06Accelerators
Modernisation Starter
Change an old system without switching it off.
The problem it solves
A rewrite from scratch is the most expensive way to find out what the old system was really doing. The behaviour that matters is often undocumented and lives only in the code. Replacing it safely means capturing that behaviour first, then moving one piece at a time while the old system keeps serving users.
A toolkit for moving an ageing application forward safely: an inventory of what it really does, tests that pin its behaviour, and scaffolding to replace it piece by piece.
What’s inside
- ✦An inventory of code and dependencies, including the parts nobody remembers owning
- ✦Characterisation tests that record what the system does today, before anything changes
- ✦Routing scaffolding that sends one capability at a time to new code — the strangler-fig pattern
- ✦Side-by-side comparison of old and new outputs
- ✦A decision log of what was moved, when, and why
How a project uses it
- 01Inventory the system and agree the first slice to move
- 02Pin its behaviour with tests
- 03Build the replacement behind a switch and compare the two
- 04Move the next slice — or stop, if the rest is fine where it is
What it is not
- A big-bang rewrite
- An automatic code translator
- A commitment to replace everything
Works well with
- A/05
AWS Landing Zone
Infrastructure as code from the first commit.
An OpenTofu and Terragrunt foundation for AWS: an explicit dependency graph, a pinned toolchain in a container, and CloudFront hosting behind a strict Content-Security-Policy. This website is deployed on it.
- AWS
- OpenTofu
- Terragrunt
- CloudFront
- A/04
LLM Evaluation Harness
“Is it better?” — with an answer that is a number.
Regression testing for prompts, models and retrieval: a versioned set of cases drawn from your own history, scored on every change.
- Evaluation
- CI
- Regression testing
- Model comparison
Start a project
Want this under your project?
Tell us what you are building and what you already have. We will tell you whether this accelerator fits, what it would need adapting, and where it would not help.
No form and no automated follow-up sequence. An email reaches an engineer, and the first reply is either a real question or an honest “not us.” We work in English, remotely, across European time zones.
We reply to every message that isn’t automated.