When code gets_older

4,471 views

Published on

How to keep maintenance projects alive and kicking

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,471
On SlideShare
0
From Embeds
0
Number of Embeds
2,480
Actions
Shares
0
Downloads
22
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

When code gets_older

  1. When code gets older Tips for keeping maintenance projects alive and kicking Sven Peters Ambassador Atlassian
  2. Sven Peters @svenpet svenpet.com Ambassador
  3. Experience my Disclaimer
  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!
  7. REWRITE
  8. REWRITE
  9. WindowsBroken
  10. the Engines Don‘t stop
  11. no Plan B There is THE SCRUM MASTER THE DEVELOPER THE MANAGER
  12. readability improve
  13. commentno
  14. test automated
  15. 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
  16. Clean Code
  17. nterface Segregation Principle pen Closed Principle iskow Substitution Principle ingle Responsible Principle ependency Inversion Principle
  18. 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
  19. Clean Code Developer von Stefan Lieser & Ralf Westphal clean-code-developer.de
  20. @svenpet Sven PetersAtlassian

×