CodeCrafting Clean builds, thoughtful code, UK engineering culture.

CodeCrafting

Clean builds, thoughtful code, UK engineering culture.

Latest Articles

The Red Handle Nobody Pulls: Making Feature Flag Kill Switches Inspection-Ready
Build & Delivery

The Red Handle Nobody Pulls: Making Feature Flag Kill Switches Inspection-Ready

Feature flags are useful until the day you need one and discover it is undocumented, untested or blocked by a dependency nobody remembers. This is a practical inspection routine for kill switches: named owners, expiry dates, tested rollback and a rehearsal you can actually trust. Treat the red handle like a fire door, not a decoration.

Whose Turn Is It, Really? On-Call Without the Martyrdom
Engineering Culture

Whose Turn Is It, Really? On-Call Without the Martyrdom

On-call works best when everyone knows whose turn it is, what counts as an interruption and how the burden is shared. This is a practical look at rota design for small UK teams, humane escalation, handover notes and the quiet cultural signals that stop one person becoming the permanent night shift.

Shed Logic: Build Boundaries Your Team Can Explain
Architecture

Shed Logic: Build Boundaries Your Team Can Explain

A good software boundary is less cathedral, more garden shed: small, purposeful, clearly owned and easy to point at. This piece looks at how to audit a tangled build graph, choose boundaries that follow real changes, and write them down so a new starter can explain the architecture without drawing a whiteboard maze.

The Boundary Moved, the Report Didn't: Modelling UK Places Over Time
Build & Delivery

The Boundary Moved, the Report Didn't: Modelling UK Places Over Time

UK postcodes, council boundaries and ONS area codes look like fixed facts until a boundary review lands. This is a practical guide to storing geography as dated claims with provenance, so old reports still answer old questions and new imports do not quietly rewrite history.

A Small Sign Before the Skip: Retiring Code Without Losing Its Story
Build & Delivery

A Small Sign Before the Skip: Retiring Code Without Losing Its Story

Deprecated code often vanishes with no record of why it existed or what replaced it. This is a practical case for small, discoverable retirement markers, backed by a lightweight register and a lint rule that points people towards the exit.

Checked, Dated, Stuck On: A Maintenance Tag for Every Dependency
Build & Delivery

Checked, Dated, Stuck On: A Maintenance Tag for Every Dependency

Every office kettle in Britain wears a little label saying when it was last looked at and when it's due again. Your package.json deserves the same courtesy. Here's a lightweight, risk-tiered review cadence for third-party code that doesn't collapse into a January panic.

Give Way, Not Guesswork: Signposting Your API Like a British Junction
Build & Delivery

Give Way, Not Guesswork: Signposting Your API Like a British Junction

A decent roundabout doesn't need a marshal standing in the middle waving you on — the paint, the signs and the layout do the work. Good APIs behave the same way. Here's how junction design translates into endpoints, errors, versioning and docs, plus a checklist to run before your next release.

The Door Marked Exit: Proving Your Customer Data Can Actually Leave
Build & Delivery

The Door Marked Exit: Proving Your Customer Data Can Actually Leave

An export button is not a feature you can leave until a compliance deadline. It is a promise that your data model, support process and storage choices can survive contact with the outside world. Here is how to rehearse that exit before anyone actually needs it.

Listed Buildings, Listed Decisions: A Register for Your Codebase
Engineering Culture

Listed Buildings, Listed Decisions: A Register for Your Codebase

Blue plaques do not record every resident; they mark the ones worth remembering. Your repository can do the same for the choices that keep it standing. Here is a lightweight way to write decision records that help the next engineer, not just the historian.

Where the Pennies Go: Modelling Sterling in Code Without Lying to Anyone
Build & Delivery

Where the Pennies Go: Modelling Sterling in Code Without Lying to Anyone

Billing bugs almost never start with bad arithmetic — they start with bad modelling. A practical look at integer pence, VAT rounding, discounts and refunds, plus a set of tests you can lift straight into your own suite.

When the Trains Stop, the Runbook Starts: Rehearsing Incidents on Disrupted Days
Build & Delivery

When the Trains Stop, the Runbook Starts: Rehearsing Incidents on Disrupted Days

Most incident drills happen on a calm Wednesday when everyone is at their desk. This one happens when the trains are cancelled, the phone signal is patchy, and the on-call engineer is on a rail replacement bus. Here is how to run a quarterly disruption drill that produces runbook fixes rather than a box-ticking performance.

When Clever Code Costs a Sprint: A Quarterly Boring-Code Audit
Engineering Culture

When Clever Code Costs a Sprint: A Quarterly Boring-Code Audit

Every codebase has a few clever bits that felt brilliant to write and feel expensive to change. Here is a lightweight quarterly audit to find them, score them and replace the showiest ones with code your team can actually maintain.

The Tuesday That Wasn't: Teaching Your Scheduler About the UK Calendar
Build & Delivery

The Tuesday That Wasn't: Teaching Your Scheduler About the UK Calendar

Your cron job runs at 06:00 every weekday, right up until the morning it fires into a bank holiday and nobody is there to catch the fallout. This is a practical look at modelling UK holidays properly — including Scotland's separate dates, substitute days and the awkward weekend rules — and why calendar logic belongs in product code, not a single line in a crontab.

Two Tills and a Back Room: Sizing Software for the Team You've Got
Build & Delivery

Two Tills and a Back Room: Sizing Software for the Team You've Got

Small product teams keep borrowing enterprise architecture like a corner shop borrowing a warehouse forklift. This is a practical look at what your scale actually justifies — and how to tell the difference between useful structure and expensive decoration.

The Empty Desk Rule: Shipping Software When the Country Logs Off
Build & Delivery

The Empty Desk Rule: Shipping Software When the Country Logs Off

Most bank-holiday deploy freezes are habit dressed as policy. Here is how to turn the Christmas and bank-holiday calendar into an explicit risk budget — mapping release windows to real support capacity, separating deploy from launch with flags, and writing down what the pause is actually protecting.

Before the Mug Goes Cold: A Team Budget for Local Build Speed
Build & Delivery

Before the Mug Goes Cold: A Team Budget for Local Build Speed

Local build times are usually treated as a personal irritation, but they are really a shared team cost. This is a practical way to measure the developer feedback loop, agree a kettle-test target, fix the worst offenders and stop the gains from quietly slipping away.

The Bars Will Vanish: Designing UK Apps for a Network That Isn't There
Build & Delivery

The Bars Will Vanish: Designing UK Apps for a Network That Isn't There

Most of us build on office fibre and then ship to a country of wet hills, packed trains and festival crowds. Here's a practical approach to optimistic updates, durable queues and offline states that don't eat the user's work.

The Hour That Runs Twice: Testing Your Stack Against GMT and BST
Build & Delivery

The Hour That Runs Twice: Testing Your Stack Against GMT and BST

Every October your scheduled jobs get a second chance to fire, and every March one of them silently doesn't. A practical look at making the UK's twice-yearly clock change a tested behaviour rather than an annual surprise.

The House With No Number: Designing UK Address Forms for Real Places
Engineering Culture

The House With No Number: Designing UK Address Forms for Real Places

Postcode lookup gets you eighty per cent of the way and then quietly gives up on the flat above the shop, the farm with a name and no number, and anything bound for a BFPO. A field guide to address capture that expects the mess.

From Background Hiss to Clear Signal: A Warning Budget for Small Teams
Build & Delivery

From Background Hiss to Clear Signal: A Warning Budget for Small Teams

Compiler warnings are easy to ignore until they become the weather in your team. A warning budget gives you a way to baseline the noise, ratchet the build and triage what matters without turning code review into a blame session.