Understand Legacy Code understandlegacycode.com

What you can do when code is really hard to review

understandlegacycode.com·290w

The key points of The Legacy Code Programmer's Toolbox

understandlegacycode.com·293w

Approval Tests, TCR, and Menders

understandlegacycode.com·295w

When should you stop refactoring Legacy Code?

understandlegacycode.com·295w

4 developers working their way through Legacy Code

understandlegacycode.com·297w

Where should you put the documentation?

understandlegacycode.com·300w

Start cleaning your Legacy codebase with The Daily Refactoring Hour

understandlegacycode.com·304w

Identify who to ask for help with Knowledge Maps

understandlegacycode.com·305w

Quickly improve code readability with Proximity Refactorings

understandlegacycode.com·306w

The key points of Software Design X-Rays

understandlegacycode.com·306w

7 techniques to regain control of your Legacy codebase

understandlegacycode.com·307w

If you mock, are you even testing?

understandlegacycode.com·309w

Convince managers to address Tech Debt with Enclosure Diagrams

understandlegacycode.com·310w

Demine your codebase in 30min with Exploratory Refactoring

understandlegacycode.com·311w

7 practices for a successful code handover

understandlegacycode.com·311w

Reveal the structure of long methods with an online Word Counter

understandlegacycode.com·313w

A quick way to add tests when code has database or HTTP calls

understandlegacycode.com·314w

Bring Legacy Code under tests by handling global variables

understandlegacycode.com·315w

Earn future maintainers esteem by writing simple ADRs

understandlegacycode.com·315w

Is it fine to use "AND" in a function name?

understandlegacycode.com·317w

Log in to enable infinite scrolling