250 likes | 1.44k Views
How to keep maintenance projects alive and kicking
E N D
When code gets older Tips for keeping maintenance projects alive and kicking Sven Peters Ambassador Atlassian
Sven Peters Ambassador @svenpet svenpet.com
Disclaimer my Experience
“ Nothing has a more profound or long- lasting negative effect on the productivity of a software team than a mess. Nothing. “ Robert C. Martin
How long does it take? 8 hours no Tests! grüneWiese We need it in 6! OK, I‘ll do it in 4!
Broken Windows
Don‘t stop the Engines
THE DEVELOPER THE MANAGER THE SCRUM MASTER There is no Plan B
readability improve
comment no
test automated
Legacy Code Change Algorithm by Michael C. Feathers 1. Identify Change Points 2. Find Test Points 3. Break Dependencies 4. Write Tests 5. Make Changes and Refactor
ingle Responsible Principle pen Closed Principle iskow Substitution Principle nterface Segregation Principle ependency Inversion Principle
Root Cause Analysis You Ain‘t Gonna Need It Single Level of Abstraction Favour Composition over Inheritance Seperation of Concerns DRY Don‘t repeat yourself KISS - Keep it simple, stupid
Clean Code Developer von Stefan Lieser & Ralf Westphal clean-code-developer.de
Sven Peters Atlassian @svenpet