Why you should write quality code and how to effectively use tools to do it.

1. Code Quality Paulin Solutions LLC

4. Why Bother?

5. What your client sees

6. What you see

8. Why would you do this to another Human Being!?!?

10. Good or Bad? protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException { if (req != null ) { if (req.getParameter( "type" ) != null ) { String reqType = req.getParameter( "type" ); if (reqType == "FOO" ) //Do something }}}

11. Good or Bad protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException { String type = req.getParameter( "type" ); if ( FORWARD_TYPE .equalsIgnoreCase(type)) { countForward(req, resp); } else if ( BACKWARD_TYPE .equalsIgnoreCase(type)) { countBackwards(req, resp); } else { throw new RuntimeException( "This type is not supported." ); }

12. Bad Code Smells!

13. I've learned to live with the smell why else should I care?

14. Reduce Bugs

15. Lower Maintenance Effort

16. It's Easier to Extend Good Code

17. Create Good Code Karma

18. Give your client the warm and fuzzy feeling. Quality Code = Trust

19. Components of Code Quality

20. Good Code Should Work! Functional/Non-Functional

21. Components should be testable

24. Rule of thumb for writing testable code...

25. Practice good design!

26. Good code should be easy to maintain

27. Readable

28. Stay DRY

29. Avoid Excessive Complexity

30. Ummmmmm that sounds like a lot of work!

31. Making sure it works

37. Putting it all together

39. Parting thoughts Don't write crappy code. I know where you live.