Field guide
Field guide
Short, practical reading for people responsible for an ageing application.

The rewrite trap
Full rewrites promise a clean slate, but they must reproduce years of quiet business rules, often undocumented, while the old app keeps changing. Many stall halfway. Before choosing a rewrite, try listing what the app actually does. If the list surprises you, the rewrite would have too.
Characterisation tests
When nobody is sure what the code should do, write tests that record what it does now. They are not a judgement of correctness; they are an alarm that tells you when a change altered behaviour. They make refactoring safe.
End of life, explained
When a framework or runtime reaches end of life, security fixes stop. The app keeps working, but new vulnerabilities stay open. Plan upgrades a year ahead of end-of-life dates, not a week after.
Taking over from another supplier
Secure ownership of the domain, hosting, repository and third-party accounts first. Then get a handover session if possible. Only after that should code changes begin.
A backup you have not restored is a hope
Schedule restore tests to a separate environment and record how long they took. That number is your real recovery time.
Little and often beats big and rare
Applying updates monthly means each one is small and easy to test. Leaving them for two years turns a routine job into a project.