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

Want more?

C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
340
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
1
120
C74bdcd3fa7c3d3f23290f46430b1463?s=48 mehlah
0
100
7cbd3f5f922d798cc312eaf596de7ae6?s=48 iamctodd
2
530
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
14
880
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
6
480
766b9746b59e6f09e280cd33cf4ed419?s=48 skipperchong
0
300
61857dafbd287b3027c4dcea9008ad3c?s=48 carmenhchung
8
620
06f8b41980eb4c577fa40c41d5030c19?s=48 keathley
9
330
C0390e8b11079f8761c0cd3274ed61cb?s=48 productmarketing
3
360
C35e01544a0dd94a2cf1619ee8a42ebb?s=48 clairelew
5
900
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
1
230

Transcript

  1. 1.

    Confident Refactors

  2. 2.

    Mehdi Lahmam @mehlah

  3. 3.

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

    commits from 52 contributors
  4. 4.

    Ruby is a massively successful language!

  5. 5.

    Early success Making it easy to make new things

  6. 6.

    Later success Making it easy to maintain old things

  7. 7.

    Today, let’s refactor some legacy code

  8. 8.

    Today, let’s refactor some legacy code

  9. 9.

    Refactor - verb To change the design of code without

    changing its observable behavior.
  10. 10.

    Refactor - verb To change in advance of a new

    feature or bug fix, making the job easier.
  11. 11.

    Today, let’s refactor some legacy code

  12. 12.

    Legacy - noun Old code.

  13. 13.

    Legacy - noun Code without tests.

  14. 14.

    Legacy - noun Code that we don’t like.

  15. 15.

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

    change confidently.
  16. 16.

    Today, let’s refactor some legacy code

  17. 17.

    Refactoring is hard

  18. 18.

    Refactoring legacy code is very hard

  19. 19.

    Easy to accidentally break functionality

  20. 20.

    Legacy refactors feels unsafe

  21. 21.

    Legacy refactors are hard to sell

  22. 22.

    Business priority Cost / risks

  23. 23.

    Business priority Cost / risks New features

  24. 24.

    Business priority Cost / risks New features Bugs fixes

  25. 25.

    Business priority Cost / risks New features Bugs fixes Testing

  26. 26.

    Business priority Cost / risks New features Bug fixes Testing

    Refactoring
  27. 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. 28.

    Selling refactoring is hard ⏲ ⛔

  29. 29.

    Business priority Cost / risks Refactoring

  30. 30.

    Too much pressure ⏳ ⚒

  31. 31.

    Refactors are scary

  32. 32.

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

    refactoring book Characterization testing A/B testing, experiments
  33. 33.

    Refactors as surgeries

  34. 34.

    Refactors as surgeries Requires careful planning Follow a clear process

    Multiple observations Flexible tools Things can get bloody
  35. 35.

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

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

    Cut

  40. 40.

    Record

  41. 41.

    Validate ✅

  42. 42.

    Refactor <Insert magic here />

  43. 43.

    Verify

  44. 44.

    Compare ⚖

  45. 45.

    Fallback

  46. 46.

    Delete ✂

  47. 47.

    We dit it

  48. 48.

    We dit it Time to celebrate hard