Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tampere Goes Agile 2013 - Managing a Clean Codebase

1,035 views

Published on

By Janne Rönkkö

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Tampere Goes Agile 2013 - Managing a Clean Codebase

  1. 1. Maintaining a Clean Codebase Janne Rönkkö Passionate Software Developer
  2. 2. About Me
  3. 3. 2007 79
  4. 4. Agenda ● Tools to improve code ● How we do it ● Experiences
  5. 5. Use version control
  6. 6. Implement Learn Measure
  7. 7. No bad code allowed! ● Code reviewing ● Continuous integration ● Testing
  8. 8. Do review your code
  9. 9. Invest your time in reviews 45%-70% of defects are found in code reviews but only 15%-50% using unit tests. From Clean Code “I believe that peer code reviews are the single biggest thing you can do to improve your code” Jeff Atwood
  10. 10. Benefits from code reviews
  11. 11. Readability may not be sacrificed
  12. 12. Review reasonable change at a time
  13. 13. Nothing shall be left unreviewed ● Looks ● Functionality ● Tests ● Change
  14. 14. Good change history matters
  15. 15. Show your code to others
  16. 16. Don't Repeat Yourself
  17. 17. Automate every repeating tasks
  18. 18. Run all automated tests for every change
  19. 19. Verify your implementation
  20. 20. Test your change yourself
  21. 21. Let someone else try your change
  22. 22. Test immediately
  23. 23. How long one iteration takes? Implement Learn Measure
  24. 24. Prevent instead of reacting
  25. 25. Do not publish unapproved changes
  26. 26. Agenda ● Tools to improve code ● How we do it ● Experiences
  27. 27. Tools we use ● Git ● Gerrit ● Buildbot / Jenkins
  28. 28. Use tools that fit
  29. 29. Coding Review CI Test Done
  30. 30. Review with common sense
  31. 31. All the commits are reviewed, bad ones are fixed
  32. 32. Agenda ● Tools to improve code ● How we do it ● Experiences
  33. 33. “We have become more disciplined”
  34. 34. “That is a nice way of doing that”
  35. 35. Reviewing is fast
  36. 36. Reviewing has improved our code
  37. 37. Agenda ● Tools to improve code ● How we do it ● Experiences
  38. 38. Bad Code Not Allowed
  39. 39. Janne.ronkko@vincit.fi http://www.vincit.fi/

×