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
37

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
9
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
410
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
160
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
40
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
120
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
2
750
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
130
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
270
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
360

Other Decks in Technology

See All in Technology
D8d463da5ab4a99265ffc1d12e76cbc9?s=48 sagara
1
400
A645e7c3a6635ead8fa323c583769591?s=48 hololab
0
630
13d936e697fe0f4fa96f926d0a712f6c?s=48 sansanbuildersbox
PRO
0
150
0a60519567997c093a11175b27c35b16?s=48 riita10069
0
140
53850955f15249a1a9dc49df6113e400?s=48 line_developers
PRO
0
2.5k
B1cc148711c6a37a5c922b6e72a4ad52?s=48 upura
5
5.9k
404139d782ec666acea93dffc86e089f?s=48 sylph01
2
340
76df086a2bef4b357cf29acb07959cce?s=48 m_coder
4
4.3k
6eecc52120fba9d87d982684211182ec?s=48 mochico
2
400
8fa31051503b09846584c49cd53d2f80?s=48 asei
1
810
413a764e6df9d7f2adbddb0b278ebb7e?s=48 sosai
0
170
D0acab281cd715f03af84f51ebd71faa?s=48 utam0k
4
510

Featured

See All Featured
D09fad3e36ae6841f54820be0e907f7a?s=48 rocio
156
12k
24fc194843a71f10949be18d5a692682?s=48 gr2m
86
11k
E837d2996f52008ace055a08fbfff992?s=48 frogandcode
129
20k
245cee81a9c424266e5e401d844ea881?s=48 lara
596
62k
20bfe76b3d6105641f879fe45cfc9272?s=48 bkeepers
PRO
55
4.8k
016edace78ffe826f2348d1e0c504afd?s=48 maggiecrowley
16
910
A415db3ac9e9668acbc1fb36eead84ac?s=48 mthomps
45
2.5k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
688
180k
78b475797a14c84799063c7cd073962f?s=48 holman
464
280k
Aff5641764408271f7bc398f2097edd0?s=48 denniskardys
223
120k
282d599b414022eba5096510f675b6e2?s=48 chrislema
231
16k
C620790ae5bf5b50c245b2e0ef95f338?s=48 deanohume
294
28k

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