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

Confident refactors

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →
Avatar for Mehdi Lahmam B. Mehdi Lahmam B.
June 19, 2017
Technology
1
140

Confident refactors

Avatar for Mehdi Lahmam B.

Mehdi Lahmam B.

June 19, 2017
Tweet

More Decks by Mehdi Lahmam B.

See All by Mehdi Lahmam B.
Beyond code: Becoming a Product Engineer
Avatar for Mehdi Lahmam B. mehlah
0
39
Possible to measure developer productivity?
Avatar for Mehdi Lahmam B. mehlah
0
48
PG FDW FTW
Avatar for Mehdi Lahmam B. mehlah
0
180
Product culture
Avatar for Mehdi Lahmam B. mehlah
0
80
OpenAPI and AsyncAPI specifications as contracts
Avatar for Mehdi Lahmam B. mehlah
0
670
Technical Debt
Avatar for Mehdi Lahmam B. mehlah
1
300
Data informed growth
Avatar for Mehdi Lahmam B. mehlah
0
250
Serverless Ruby and AWS Lambda
Avatar for Mehdi Lahmam B. mehlah
0
180
Middleware all the things
Avatar for Mehdi Lahmam B. mehlah
2
870

Other Decks in Technology

See All in Technology
AI駆動PjMの理想像 と現在地 -実践例を添えて-
Avatar for オカムラ masahiro_okamura
1
110
Digitization部 紹介資料
Avatar for Sansan, Inc. sansan33
PRO
1
6.8k
こんなところでも（地味に）活躍するImage Modeさんを知ってるかい？- Image Mode for OpenShift -
Avatar for Masataka Tsukamoto tsukaman
0
130
Contract One Engineering Unit 紹介資料
Avatar for Sansan, Inc. sansan33
PRO
0
13k
Context Engineeringが企業で不可欠になる理由
Avatar for Hirosato Gamo hirosatogamo
PRO
3
570
20260204_Midosuji_Tech
Avatar for Takuya Yonezawa takuyay0ne
1
150
FinTech SREのAWSサービス活用/Leveraging AWS Services in FinTech SRE
Avatar for maaaato maaaato
0
130
SREのプラクティスを用いた3領域同時 マネジメントへの挑戦 〜SRE・情シス・セキュリティを統合した チーム運営術〜
Avatar for coconala_engineer coconala_engineer
2
640
会社紹介資料 / Sansan Company Profile
Avatar for Sansan, Inc. sansan33
PRO
15
400k
Sansan Engineering Unit 紹介資料
Avatar for Sansan, Inc. sansan33
PRO
1
3.8k
コスト削減から「セキュリティと利便性」を担うプラットフォームへ
Avatar for SansanTech sansantech
PRO
3
1.5k
制約が導く迷わない設計 〜 信頼性と運用性を両立するマイナンバー管理システムの実践 〜
Avatar for ないとー bwkw
3
920

Featured

See All Featured
Ecommerce SEO: The Keys for Success Now & Beyond - #SERPConf2024
Avatar for Aleyda Solis aleyda
1
1.8k
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
Avatar for Akash Hashmi akashhashmi
0
270
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
Avatar for Aleyda Solis aleyda
2
9.5k
Optimising Largest Contentful Paint
Avatar for Harry Roberts csswizardry
37
3.6k
Navigating the Design Leadership Dip - Product Design Week Design Leaders+ Conference 2024
Avatar for Andy Polaine apolaine
0
170
Color Theory Basics | Prateek | Gurzu
Avatar for Gurzu gurzu
0
200
The untapped power of vector embeddings
Avatar for Frank van Dijk frankvandijk
1
1.6k
DevOps and Value Stream Thinking: Enabling flow, efficiency and business value
Avatar for Helen Beal helenjbeal
1
94
Believing is Seeing
Avatar for Spiro Bolos oripsolob
1
54
The agentic SEO stack - context over prompts
Avatar for schlessera schlessera
0
640
The Art of Programming - Codeland 2020
Avatar for Erika Heidi erikaheidi
57
14k
Between Models and Reality
Avatar for mayunak mayunak
1
190

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