Follow me on Twitter:
Blog Post Categories
- Announcements {19}
- Articles {2}
- Bits and Pieces {74}
- Blogosphere {1}
- Bonuses {2}
- Build in Small Batches {27}
- Collaborate {38}
- Create CLEAN Code {34}
- Implement the Design Last {11}
- Integrate Continuously {30}
- Off-Topic but Interesting {3}
- Rants {82}
- Refactor Legacy Code {24}
- Say What, Why, and for Whom Before How {22}
- Seven Strategies {38}
- Specify Behaviors with Tests {17}
- Write the Test First {27}
Archives
Privacy Policy
(c) 2024 To Be Agile
Refactor existing code when you need to add features so there’s a space for the new features in the existing system before you add it.
Retrofitting Tests
Retrofitting tests into legacy code is difficult process but can give us the ability to redesign and improve the quality of that software as we go. It is generally a good idea to add tests before refactoring code. Tests serve as a safety net so if I make a mistake in refactoring the test will …
Continue reading “Retrofitting Tests”
Read MoreIs Your Legacy Code Rotting?
Some businesses think that software is a write-once activity. It is true that once written software does not change but the world around us does and static software quickly becomes out of date. Code rot is real. Even if a system was well written at one time we often cannot anticipate how a system will …
Continue reading “Is Your Legacy Code Rotting?”
Read More