Understand Legacy Code understandlegacycode.com

5 talks on Legacy Code: The Legacy of SoCraTes, 1st edition

understandlegacycode.com·318w

Focus refactoring on what matters with Hotspots Analysis

understandlegacycode.com·319w

Don't make Clean Code harder to maintain, use the Rule of Three

understandlegacycode.com·320w

Are functions that simply call another function a bad design choice?

understandlegacycode.com·321w

What is wrong with boolean parameters?

understandlegacycode.com·322w

5 coding exercises to practice refactoring Legacy Code

understandlegacycode.com·323w

Dive into an unfamiliar codebase from its edges

understandlegacycode.com·324w

The key points of Working Effectively with Legacy Code

understandlegacycode.com·325w·Hacker News, r/programming

5 arguments to make managers care about technical debt

understandlegacycode.com·326w

The Ship of Theseus to NOT rewrite a legacy system from scratch

understandlegacycode.com·327w

Is it up to the newer developer to pay back others' technical debt?

understandlegacycode.com·328w

Use the Mikado Method to do safe changes in a complex codebase

understandlegacycode.com·328w

3 steps to add tests on existing code when you have short deadlines

understandlegacycode.com·329w

What is Legacy Code? Is it code without tests?

understandlegacycode.com·329w

Log in to enable infinite scrolling