Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Confident refactors

C74bdcd3fa7c3d3f23290f46430b1463?s=47 Mehdi Lahmam B.
June 19, 2017
Technology
1
35

Confident refactors

C74bdcd3fa7c3d3f23290f46430b1463?s=128

Mehdi Lahmam B.

June 19, 2017
Tweet

More Decks by Mehdi Lahmam B.

See All by Mehdi Lahmam B.
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
400
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
140
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
15
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
110
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
2
730
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
120
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
270
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
350
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
51

Other Decks in Technology

See All in Technology
Ad2155c75c67c0100dd008ad10858de5?s=48 legalforce
PRO
0
150
966e29b84ae7dbde170f66b0bc75b7a6?s=48 ishiayaya
PRO
0
820
Baf3de0f86a61c06c8fb9539d4958bf5?s=48 jozono
6
1.2k
61e7dc2e84a1a1c4ac1a8e2c552fee07?s=48 tutsunom
1
330
3f0d60d6727ea76dfc9f7863f8e035c4?s=48 aizurage
0
120
65d8522e6ea1d11c8f6343027b2e1688?s=48 yashi8484
0
130
D069523c85d56ebf004c9695bca578c0?s=48 kenichimunezawa
0
820
7b3e0dbc0d712ad5df602d9f9e5e4209?s=48 sei88888
5
410
B1bddcb899ec3060fe9913f3cb70dbb6?s=48 lmt_swallow
0
200
53850955f15249a1a9dc49df6113e400?s=48 line_developers
PRO
1
530
3373c144fef1d3518b9b3f24a6b46ad0?s=48 lmi
5
3.5k
B1dca90d4b3ffd2ccd918774e1ba170d?s=48 hmatsu47
2
140

Featured

See All Featured
2bb923c57a1fdc3a2eb484bb8d565fd2?s=48 ufuk
56
5.5k
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
267
17k
Dafc4723e9a1c067796c0fec6f509774?s=48 lemiorhan
628
47k
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
494
110k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
498
130k
A9179349dd2bdc67f377719f56d85656?s=48 garrettdimon
289
110k
5f83ef806155b403c3393160ce51f955?s=48 jlugia
217
16k
0bce06bd06ee7a2c4f5500f25dcf7f18?s=48 paulrobertlloyd
71
3.7k
B47b288784fda77a94aeb234ca743c24?s=48 keavy
107
14k
1f74b13f1e5c6c69cb5d7fbaabb1e2cb?s=48 sferik
612
55k
D09fad3e36ae6841f54820be0e907f7a?s=48 rocio
155
11k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
683
180k

Transcript

  1. Confident Refactors

  2. Mehdi Lahmam @mehlah

  3. 25kV Rails app, started in Feb 2009 Never rewritten 23k+

    commits from 52 contributors

  4. Ruby is a massively successful language!

  5. Early success Making it easy to make new things

  6. Later success Making it easy to maintain old things

  7. Today, let’s refactor some legacy code

  8. Today, let’s refactor some legacy code

  9. Refactor - verb To change the design of code without

    changing its observable behavior.

  10. Refactor - verb To change in advance of a new

    feature or bug fix, making the job easier.

  11. Today, let’s refactor some legacy code

  12. Legacy - noun Old code.

  13. Legacy - noun Code without tests.

  14. Legacy - noun Code that we don’t like.

  15. Legacy - noun Code we don’t understand well enough
 to

    change confidently.

  16. Today, let’s refactor some legacy code

  17. Refactoring is hard

  18. Refactoring legacy code is very hard

  19. Easy to accidentally break functionality

  20. Legacy refactors feels unsafe

  21. Legacy refactors are hard to sell

  22. Business priority Cost / risks

  23. Business priority Cost / risks New features

  24. Business priority Cost / risks New features Bugs fixes

  25. Business priority Cost / risks New features Bugs fixes Testing

  26. Business priority Cost / risks New features Bug fixes Testing

    Refactoring

  27. Business priority Cost / risks New features Bug fixes Testing

    Refactoring no selling needed easy to sell can often sell very hard to sell

  28. Selling refactoring is hard ⏲ ⛔

  29. Business priority Cost / risks Refactoring

  30. Too much pressure ⏳ ⚒

  31. Refactors are scary

  32. What techniques we have? PDD - Pray Driven Development Fowler’s

    refactoring book Characterization testing A/B testing, experiments

  33. Refactors as surgeries

  34. Refactors as surgeries Requires careful planning Follow a clear process

    Multiple observations Flexible tools Things can get bloody

  35. 1. Plan 2. Cut 3. Record 4. Validate 5. Refactor

    6. Verify 7. Compare 8. Fallback 9. Delete Clear process
  36. None
  37. None
  38. None

  39. Cut

  40. Record

  41. Validate ✅

  42. Refactor <Insert magic here />

  43. Verify

  44. Compare ⚖

  45. Fallback

  46. Delete ✂

  47. We dit it

  48. We dit it Time to celebrate hard