The Journal.

The books, and the quiet work of subtraction. Fourteen items to Done across four projects, and not a new feature among them. The practice turned first to its own house — the year-end accounts and the VAT position analysed, the bookkeeping put on an automated footing; then outward, where an enterprise e-commerce order integration lost a layer of logic it had outgrown and gained an honest map of how a partner brand's orders and payments actually reach the finance system. The retained veterinary practice's site had an embedded third-party form taken out and a real booking route put in its place, and a September fee change published well ahead of the day it takes effect. A local dog-training club's handover was settled, and the internal developer tool stood exactly where last week left it.

Proof, and the apparatus of publication. The internal developer tool took thirty of the week's thirty-six closed items — not new faculties this time but the two things that turn a working instrument into a releasable one: a full automated test suite that proves it behaves — unit, property-based, snapshot and component tests, with benchmarks and coverage — which paid for itself at once by surfacing two genuine faults; and the public scaffolding a tool needs before strangers can use it — reference documentation for each cron dialect it speaks, a cookbook of worked examples, and the privacy, security-disclosure and credits apparatus that lets it stand in the open. Alongside it, a family-history application's cloud foundations stayed in flight, and the smaller retained work was quietly kept.

The inward tool, given its working faculties. The internal developer tool took twenty-one of the week's thirty-four closed items, carried from a face to an instrument that does its three jobs: a schedule you can type and read back in plain language, a calendar that shows the days it will actually fire — month, week and agenda, exportable to a real diary or spreadsheet — and a compare mode that sets two schedules side by side and marks the difference. Alongside it, a clinical canine massage practice's site gained its audit, telemetry and bot-protection layer ahead of launch, and the smaller retained work was quietly kept.

The inward week, continued — and the inward thing given a face. The new internal developer tool took thirteen of the week's eighteen closed items, carried from a working core to the surface a person actually touches: a visual design system and layout shell, working state held in a shareable link, and an end-to-end test harness wired into CI. Alongside it, a clinical canine massage practice's contact pipeline was proven and switched live, and the smaller retained work was quietly kept.

A week turned inward. A new internal developer tool — a cron-expression calculator, describer and comparer — took the bulk of it: thirty-two items, from an empty repository and CI pipeline through a complete domain layer and three cron parsers to a working set of services, while the enterprise e-commerce support carried on and the retained clients were quietly kept.

The mirror image of last week. The new clinical canine massage practice took the bulk of it — thirty-seven items, from signed paperwork through a scaffolded repository and provisioned cloud to a working, tested contact pipeline — while the internal platform's modelling advanced and the retained clients were quietly kept.

A building week, and mostly out of sight. The internal quantitative sports-analytics platform took the bulk of it — twenty-six items, from data ingestion through modelling to a working execution service — while a new client engagement's foundations were laid and the retained clients quietly tended.

Closing week. The company-website infrastructure programme reached its formal end — DNS authority returned to GoDaddy, legacy hosting cancelled, observation closed — while a new local-client engagement began the right way, with foundations before code.

The week after. Phase 7 closed as an epic, telemetry sharpened, uptime watched from the outside, mirrors and archives put in place — and an enterprise e-commerce go-live entered its post-cutover hyper-care phase.

Launch week. Two production go-lives in seven days — the new company website went live at thecodeabides.co.uk, and an enterprise e-commerce platform reached its own cutover milestone alongside.

Two long-running engineering arcs converging in the same seven days — a new company website on Azure built feature-complete, and an enterprise e-commerce client cutover commenced. Forty-nine items to Done across three projects.

A quieter week, by design. The headline activity was unglamorous and important — a comprehensive npm package upgrade sweep across five Node.js microservices, kept on cadence as a matter of supply-chain hygiene.

Five active projects, including the kick-off of a new internal initiative — a quantitative sports analytics platform moved from idea to scaffolded codebase, with progress alongside on greenfield development, enterprise e-commerce, and client IT.

A founding week. The full application scaffold for a bespoke web platform came together on a .NET 10 / C# 14 stack with Onion Architecture across five projects, and the CI pipeline that will carry the work was wired up alongside.