Code Quality for a Fresh Start
Download as PPTX, PDF0 likes596 views
The document discusses principles of writing high quality code, including understandability, readability, changeability, extensibility, and maintainability. It notes that poor code quality can lead to increased costs and technical debt when responding to changes. Some characteristics of bad code mentioned are rigidity, fragility, immobility, and needless complexity. The document provides recommendations for improving code quality such as using good IDEs, static analysis tools, builds, test automation, source control, and continuous integration. It also suggests practices like code katas, pair programming, code reviews, and following standard conventions.
Code Quality for a Fresh Start
- 2. get some paper, put it in a typewriter, type FADE IN ... and keep typing - Peter Falk told to Paul Reiser
- 3. A computer program is the most complicated thing on earth, second to a woman's brain - Marvin Silva
- 4. PRE DEMO: What it looks like
- 5. Maybe it breaks down. Maybe a better program is created to replace it - happens all the time - The Oracle told to Neo
- 6. Why do you have to care? - Understandability - Readability - Changeability - Extensibility - Maintainability
- 7. The costs: - Respond to change - Cost of change - Technical debt
- 8. How do you write bad code? - Rigid - Fragile - Immobility - Design debt : Technical debt by taking shortcuts? - Environment debt : Technical debt by not running build, test, and other tasks - Needless complexity - Needless repetition - Opacity
- 9. I know it when I see it! - KP told to The Wife
- 10. My gut says it’s clean, so I believe it - KP
- 11. When you are matured with these principles and patterns it will become difficult for you to think without those - KP
- 12. Where to begin? - Good IDE - Static analysis tools - Builds - Test automation tools - Source control - Continuous integration
- 14. How to practice? - Code kata - Pair programming - Design/Code reviews - Peer reviews
- 16. Other things that go with it? - KISS - Boy scout rule - Root cause analysis - Following standard conventions - Class design principles
- 17. What can you do TODAY? - Naming conventions - Methods - Design principles - Dependency injection - Encapsulate conditionals - Polymorphism to If/Else or Switch/Case - Exception over return codes
- 18. DEMO: Standard naming conventions
- 19. DEMO: Methods
- 20. DEMO: Query from command
- 21. DEMO: DRY up yourself
- 22. DEMO: Dependency injection by hand
- 23. DEMO: Encapsulate various things
- 25. DEMO: Replacing errors and exceptions
- 26. Do you swear to write software, the whole software and nothing but well-crafted software so help you God! - The Software Craftsmanship Oath
- 28. Code Kata: - Reverse my array - Fizz Buzz
- 29. New requirements: - Optimize, don’t use any other arrays