Brutal Refactoring Game @XP Benelux 29 11 2013

  • 246 views
Uploaded on

Do you know you can have legacy code in 15 minutes? This is a session where you can find out how to refactor often and soon toward clean and easy to change code.

Do you know you can have legacy code in 15 minutes? This is a session where you can find out how to refactor often and soon toward clean and easy to change code.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
246
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Brutal Refactoring Game www.mozaicworks.com
  • 2. Us Adi Bolboaca: Programmer, Trainer, Coach Erik Talboom Software Craftsman coach, trainer www.mozaicworks.com
  • 3. 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 www.mozaicworks.com
  • 4. Code smell A code smell is a hint that shows  you might have a problem in your  system. '  www.mozaicworks.com
  • 5. Code smell Sniffable Easy to spot Does not always indicate a problem www.mozaicworks.com
  • 6. Refactoring Changing a software system  without changing the behavior of  the code and improving its  internal structure www.mozaicworks.com
  • 7. Refactoring Is NOT: Re-engineering Re-design Re-writing www.mozaicworks.com
  • 8. Problem Tic-Tac-Toe Board 3x3 X plays first 0 plays second Result: winner or draw www.mozaicworks.com
  • 9. Coding smells 1) Lack of tests 2) Name not from domain 9) Feature envy 10) Method too long (> 6 lines) 3) Name not expressing intent 11) Too many parameters (> 3) 4) Unnecessary if 5) Unnecessary else 6) Duplication of constant 7) Method does more than one thing 8) Primitive obsession 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 www.mozaicworks.com
  • 10. Contact me Unit testing workshop @adibolb Remote pair-programming TDD workshop Refactoring workshop Working FAST and Safe with existing code Legacy code retreat Code retreat www.mozaicworks.com
  • 11. Brutal Refactoring Game Extend your mentoring & training capacity Accelerate learning through communities of practice Grow your functional leaders and top talents http://www.mozaicworks.com adrian.bolboaca@mozaicworks.com @adibolb www.mozaicworks.com
  • 12. Read more http://blog.adrianbolboaca.ro/2013/04/the-hi www.mozaicworks.com
  • 13. Brutal Refactoring Game Q&A, Beer & More... www.mozaicworks.com