Google I/O Extended: Refactoring Smelly Code

Originally, this was intended to be a series of blogposts demoing smelly code and refactoring patterns that can be improved to reduce the number of WTFs in the code. Later became a tech talk with hands-on demos before presented at developer forums and 2015 Google I/O Extended in Colombo, Sri Lanka.

Transcript

1. Code Quality Code @kosalanuwan
2. get some paper, put it in a typewriter, type FADE IN ... and keep typing - Peter Falk told to Paul Reiser
3. PRE DEMO: Movie Script
4. A computer program is the most complicated thing on earth, second to a woman's brain - Marvin Silva
5. PRE DEMO: What it looks like
6. Why do you have to care? - Understandability - Readability - Changeability - Extensibility - Maintainability
7. 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
8. The costs: - Respond to change - Cost of change - Technical debt
9. My gut says it’s clean, so I believe it - KP
11. Code Quality Code @kosalanuwan less WTFs
12. How to practice? - Code kata - Pair programming - Design/Code reviews - Peer reviews
13. 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
14. DEMOS
15. Other things that go with it? - KISS - Boy scout rule - Root cause analysis - Following standard conventions - Class design principles
16. When you are matured with these principles and patterns it will become difficult for you to think without those - KP
17. Happy Coding J @kosalanuwan http://kosalanuwan.github.io/talks