Rebuilding and modernising

• 2026-10-23Retiring an API version: the Deprecation and Sunset headersWhat the two standard HTTP headers for an ending API say, in plain terms, with each fact linked to its RFC. The date you announce, the link to your notes, what partners see.
• 2026-10-19A framework end-of-life calendar for product leadersSupport end dates for five widely used web frameworks and runtimes, as of 18 October 2026, each linked to the project's own release page, and what end of life means for security fixes and hiring.
• 2026-10-19Is it time to rebuild? A checklist for product leadersFive questions that show whether a product has started to hold the business back, to answer about your own product. No score decides for you.
• 2026-10-19Rebuild or refactor? A decision guideFour questions that decide whether an ageing product should be changed in place or rebuilt, with one example of each from our own record.
• 2026-10-18Questions to ask before anyone touches your codebaseBefore an outside partner changes your product, four sets of questions settle most of what can go wrong later. Who owns the work, what they can reach, who says yes, and how you leave.
• 2026-10-18The cost of waiting: how to talk about technical debt with your boardA board does not fund a list of code problems. It weighs what each month of waiting costs the roadmap. How to describe debt in those terms, and what to ask in the room.

All writing