When code gets_older
2 likes2,860 views
When code gets older, it requires maintenance projects to keep it alive and functioning properly. These projects can be challenging due to technical debt and complexity that has accumulated over time. The document provides tips for successful maintenance projects, including refactoring code to improve structure and readability, adding automated tests, practicing principles like single responsibility and open/closed, and using techniques like root cause analysis.
1 of 24
Downloaded 25 times
More Related Content
What's hot (20)
Ad
Viewers also liked (20)
Ad
Similar to When code gets_older (20)
More from Sven Peters (20)
When code gets_older
- 1. When code gets older Tips for keeping maintenance projects alive and kicking Sven Peters Ambassador Atlassian
- 4. Nothing has a more profound or long- lasting negative effect on the productivity of a software team than a mess. Nothing. “ “Robert C. Martin
- 5. green Field
- 6. grüne Wiese How long does it take? 8 hours We need it in 6! OK, I‘ll do it in 4! no Tests!
- 9. REWRITE
- 10. REWRITE
- 11. WindowsBroken
- 13. no Plan B There is THE SCRUM MASTER THE DEVELOPER THE MANAGER
- 15. commentno
- 16. test automated
- 17. Code Change Algorithmby Michael C. Feathers Legacy 1. Identify Change Points 5. Make Changes and Refactor 2. Find Test Points 3. Break Dependencies 4. Write Tests
- 18. Clean Code
- 19. nterface Segregation Principle pen Closed Principle iskow Substitution Principle ingle Responsible Principle ependency Inversion Principle
- 20. DRY Don‘t repeat yourself KISS - Keep it simple, stupid Favour Composition over InheritanceRoot Cause Analysis SingleLevelofAbstraction Seperation of ConcernsYou Ain‘t Gonna Need It
- 21. Clean Code Developer von Stefan Lieser & Ralf Westphal clean-code-developer.de