Before taking over a codebase: what to inspect
A practical technical assessment of ownership, deployability, data risks and the first safe change.
Journal
Software modernisation
Improve an existing product while understanding the business that depends on it. Read about codebase assessment, technical debt, migration, recovery and the boundaries of ongoing maintenance.
Journal
Improve an existing product while understanding the business that depends on it. Read about codebase assessment, technical debt, migration, recovery and the boundaries of ongoing maintenance.
Rewrite or improve gradually? A decision grounded in the business
Compare a full rewrite with incremental modernization using boundaries, migration effort and business continuity.
Prioritize technical debt by its effect on the business
Build a debt backlog around incidents, delivery friction and recovery risk rather than code aesthetics.
Plan a migration around data, cutover and a credible way back
A practical guide to rehearsal, reconciliation, write ownership and rollback during a software migration.
What software maintenance should actually include
Separate defects, product changes, security work and operations before agreeing a maintenance scope.
Let's make something useful.
A first product, a difficult workflow or software that needs a fresh start. Tell us where you are.