3. Catch more mistakes
Confidently make more changes
Built in regression testing
Extend the life of your codebase
Better predictability and reliability
8/12/2019 Java Best Practices 3
5. Any fool can write code that a
computer can understand. Good
programmers write code that
humans can understand."
Martin Fowler
8/12/2019 Java Best Practices 5
6. 8/12/2019 Java Best Practices 6
https://llewellynfalco.blogspot.com/p/sparrow-decks.html
19. You are not allowed to write
any production code unless it
is to pass a failing unit test
You are not allowed to write
any more of a unit test than
is sufficient to fail, and
compilation failures are
failures
You are not allowed to write
any more production code
than is sufficient to pass the
one failing unit test
8/12/2019 Java Best Practices 19
31. Add Continuous Integration to build code
Add minimal unit tests, add code coverage
Add GUI tests
Test all new features
Slowly refactor existing code.
8/12/2019 Java Best Practices 31
34. Take baby steps
Metrics should evolve
Stay objective
Don’t be driven by metrics or reporting
Automate everything
8/12/2019 Java Best Practices 34
35. Java Best Practices
Usual Suspects
Code Complete
by Steve McConnell
Clean Code
by Bob Martin
Effective Java
by Joshua Bloch
Test Driven Development
by Martin Beck
Refactoring
By Martin Fowler
Effective Unit Testing
By Lasse Koskela
Working Effectively
By Michael Feathers
Design Patterns
By Gamma et al.
36. Java Best Practices
Not So Usual Suspects
Java by Comparison
by Simon Harrer et al.
ProGit
by Chacon Straub
Practical Unit Testing
by Tomek Kaczanowski
Clean Coder
by Bob Martin
Refactoring Workbook
By William C. Wake
Head First Design Patterns
By Eric Freeman et al.
Head First OOAD
By Brett McLaughlin et al.