1 / 45

W jax wenn-code altert

Slideshow about W jax wenn-code altert

svenpet
Download Presentation

W jax wenn-code altert

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sven Peters / Atlassian Wenn Code altert Tipps, wie Wartungsprojekte frisch bleiben

  2. Sven Peters Ambassador @svenpet svenpet.com mobro.co/svenpet

  3. Disclaimer my Experience @svenpet svenpet.com

  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. ? Maintenance projekt

  6. ? 5 years

  7. ? 1M+ lines of code

  8. ? 2M+ lines of code

  9. ? lost overview lines of code

  10. Hardware Bath Tub Curve

  11. Software Bath Tub Curve

  12. Software Bath Tub Curve

  13. greenField

  14. How long does it take? 8 hours no Tests! grüneWiese We need it in 6! OK, I‘ll do it in 4!

  15. more cooks!

  16. too many cooks... ...spoil the broth

  17. REWRITE

  18. REWRITE

  19. Broken Windows

  20. Don‘t stop the Engines

  21. THE DEVELOPER THE MANAGER THE SCRUM MASTER There is no Plan B

  22. Boy Scout Rule Leave the campground cleaner than you found it.

  23. Toolchain The

  24. readability improve

  25. Naming “ Any fool can write code that a computer can understand. Good programmers write code that humans can understand. “ Martin Fowler

  26. comment no

  27. test automated

  28. Legacy Code Change Algorithm by Michael C. Feathers 1. Identify Change Points 2. Make Changes and Refactor

  29. 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

  30. Clean Code

  31. ingle Responsible Principle pen Closed Principle iskow Substitution Principle nterface Segregation Principle ependency Inversion Principle

  32. 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

  33. Clean Code Developer von Stefan Lieser & Ralf Westphal clean-code-developer.de

  34. Evolve Clean Code Developer &

  35. Sven Peters Atlassian @svenpet

More Related