Brutal Refactoring Game - LSCC Sep 2012 Hands on session

http://www.meetup.com/london-software-craftsmanship/events/82626042/

Transcript

1. Brutal Refactoring Game
2. Today Take a simple problem Use pair-programming Language agnostic Write code Add functionality only when the code is clean Refactor often Refactor a lot
3. Code smell A code smell is a hint that shows you might have a problem in your system. '
4. Code smell Sniffable Easy to spot Does not always indicate a problem
5. Refactoring Changing a software system without changing the behavior of the code and improving its internal structure
6. Refactoring Is NOT: Re-engineering Re-design Re-writing
7. Problem Tic-Tac-Toe Board 3x3 X plays first 0 plays second Result: winner or draw
8. Coding smells 1) Lack of tests 2) Name not from domain 3) Name not expressing intent 4) Unnecessary if 5) Unnecessary else 6) Duplication of constant 7) Method does more than one thing 8) Primitive obsession 9) Feature envy 10) Method too long (> 6 lines) 11) Too many parameters (> 3) 12) Test – not unitary 13) Test – setup too complex 14) Test – unclear Act 15) Test - more than one assert 16) Test – no assert 17) Test – too many paths
9. Slides and session by Adi Bolboaca http://www.mozaicworks.com adrian.bolboaca@mozaicworks.com @adibolb