Some weeks the work is what you build. This one was what you settle. Fourteen items reached Done across four projects and not one of them was a new feature — nothing released, nothing added, nothing a visitor to any of these systems would notice had changed. It was a week of accounts and of subtraction: the practice's own books opened and put in order, an integration relieved of logic it had outgrown, a client's site relieved of a form it should never have had to carry, and a club's small obligations settled while they were still small. The internal tool that has dominated this journal for a month was not touched at all.
It began at home. A practice that keeps other people's systems in order has no excuse for neglecting its own, and the first three items closed were the practice's own accounts. The year-end position was worked through properly rather than glanced at — the figures assembled, read, and understood while there is still time to act on what they say. The VAT position was analysed alongside it, which is the sort of thing a small company puts off until the quarter it can no longer be put off. And then the third item, which is the one that matters beyond this year: the bookkeeping itself was put on an automated footing, so that next year's figures largely assemble themselves rather than being assembled, by hand, by the person who can least afford the evening. Three items, no code shipped, and a meaningful reduction in the standing cost of simply existing as a business.
Outward, the enterprise e-commerce work was mostly a matter of taking things away. The integration that creates orders had for some time been carrying a publishing step for an order-integrity check that no longer served any purpose — a piece of machinery kept running because removing it had never quite been anybody's job. It was removed. The global sales-channel configuration was then brought into line for the order-management update path, so that the channels the system thinks it is serving are the channels it is actually serving. Neither change adds a capability. Both make the thing beneath easier to reason about, and a system that is easier to reason about is one that breaks less often and is repaired faster when it does.
The other two items closed there produced no code whatsoever, and were among the more valuable of the week. A partner brand sits inside the group whose orders must eventually be understood by the finance system, and before anything can be safely changed about that path somebody has to be able to say, plainly and without guessing, how it presently works. So the week was spent reading it: how those orders in fact make their way into the finance system today, and which payment methods that brand is genuinely using — not which ones the documentation claims, nor which ones anyone remembers configuring, but which ones appear in the traffic. Research of this kind is easy to skip and expensive to have skipped. You cannot fold one system into another until you can describe the first one honestly, and the point of the week's reading was to be able to describe it.
— On subtraction —A system is improved as often by what is taken out of it as by what is put in. The difficulty with removal is that it leaves nothing to show for itself.
For the retained veterinary practice the week was more visible, and more directly felt by the people who actually use the thing. Its senior-pet clinic page had been leaning on an embedded third-party form — the sort of expedient that gets a page working on a Tuesday and is still there three years later, sitting awkwardly in the design, keeping its own copy of data it has no business keeping, and quietly training clients to distrust the page it sits on. It was taken out. In its place went a proper booking route and the surrounding content rewritten around it, so that a client who wants an appointment is offered one rather than a form. Alongside it, the prices page: a fee change takes effect on the first of September, and it was published now, in July, with a plain notice saying what is changing and when. Clients will read it, some will grumble, and not one of them will be surprised in September. That is a small thing to do and very nearly the whole of good stewardship.
Beneath the same site, the unglamorous half: the machine that sits behind it had its firmware brought up to date — a chore nobody thanks you for and everybody would miss — and another clear-down of accumulated contact-form entries, on the principle that data one no longer needs is not an asset but a liability, and the safest place for it is nowhere.
And the local dog-training club, whose treasurer stepped down last week, produced this week the practical residue of that handover. The insurance was chased and settled. The latest payments were reconciled and the instructor's fees worked out and paid. And a shared mailbox was stood up for class bookings, so that enquiries now arrive somewhere a committee can reach rather than in one particular person's personal inbox. That last is precisely the sort of thing nobody asks for and everybody needs: the small structural repair that outlasts whoever happens to hold the post, and that makes the next handover a smaller occasion than this one.
What did not move deserves recording too, since a journal that reports only motion is a brochure. The internal developer tool — proved, documented and, as this journal said last week, all but ready to be handed to a stranger — stands exactly where it was left. Not a single item was touched. The family-history web application's cloud foundations are likewise open where they were open: the hosting, the database and the pipeline all begun and none of them finished, and no movement on any of the three this week. There is no drama in either fact. There were only so many hours, and they went to the books and to the people to whom they were owed. But it would be a poor record that let a quiet week look busy by declining to mention what stood still.
Two things are genuinely in flight, and both belong to the e-commerce work. The first is a defect still unexplained: discount codes going missing on one of the group's storefronts, somewhere between the order being placed and the system that is supposed to honour it. It is being hunted, and it has not yet been caught; the honest report is that we know the symptom and not the cause. The second is a piece of plumbing worth considerably more than it sounds — a trace identifier carried through every one of the integration services, so that a single order can be followed end to end across the whole chain instead of being reconstructed, afterwards and hopefully, from four separate logs that do not quite agree. It is the difference between debugging and guessing, and it is the sort of investment that only ever looks obvious in hindsight, on the night it saves you.
Looking ahead: the missing discount codes want an explanation and will get one; the trace identifier wants finishing, and will make every week after it cheaper; the internal tool still waits on the last short step between documented and released; the family-history foundations go on being foundations. And the retained clients go on being kept, as they always are.
Fourteen items to Done across four projects — the practice's own accounts read, its VAT understood and its bookkeeping automated; an integration made simpler by removal and better understood by reading; a client's page relieved of a form and given a real way to book; a fee change announced in July for September; a club's affairs settled and its post made easier to hand on. Nothing was shipped. Nothing was released. The tool of our own sat exactly where it was put down. And it was still a week's work — of the kind that does not photograph well, and that keeps a small practice solvent, its clients unsurprised, and its own house in the order it would insist upon anywhere else.