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

Confident refactors

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest. →
Avatar for Mehdi Lahmam B. Mehdi Lahmam B.
June 19, 2017
Technology
150
1

Confident refactors

Avatar for Mehdi Lahmam B.

Mehdi Lahmam B.

June 19, 2017

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
53
Possible to measure developer productivity?
Avatar for Mehdi Lahmam B. mehlah
0
60
PG FDW FTW
Avatar for Mehdi Lahmam B. mehlah
0
190
Product culture
Avatar for Mehdi Lahmam B. mehlah
0
94
OpenAPI and AsyncAPI specifications as contracts
Avatar for Mehdi Lahmam B. mehlah
0
690
Technical Debt
Avatar for Mehdi Lahmam B. mehlah
1
310
Data informed growth
Avatar for Mehdi Lahmam B. mehlah
0
270
Serverless Ruby and AWS Lambda
Avatar for Mehdi Lahmam B. mehlah
0
190
Middleware all the things
Avatar for Mehdi Lahmam B. mehlah
2
880

Other Decks in Technology

See All in Technology
AIAgentと取り組むKaggle
Avatar for shuto goya 508shuto
2
600
A Harness for Behaviour: how to get AI to generate code that does what we intend, or "TDD in the age of AI"
Avatar for Matteo Vaccari xpmatteo
0
440
LLM時代のリファクタリング戦略_AIエージェントによる段階的・安全なTS移行方法
Avatar for PLAY, inc. play_inc
0
190
Generative UI × A2UI で AI エージェントを作った話　AI-DLC も使ってみた！
Avatar for たけのこ kmiya84377
1
230
電子辞書Brainをネットに繋げてみた(自力編)
Avatar for らすぴー raspython3
0
190
イベントストーミングと Kiroの仕様駆動開発で実現する 要件の認識合わせプロセス
Avatar for syobochim syobochim
6
670
AI時代の私の技術インプットとアウトプット術
Avatar for tonkotsuboy_com tonkotsuboy_com
13
6.9k
イベントで大活躍する電子ペーパー名札 〜その３〜 / ビジュアルプログラミングIoTLT vol.23
Avatar for you（@youtoy） you
PRO
0
150
【ハノーバーメッセ振り返りイベントat名古屋】データは集約からAI起点の収集に ～組織内・組織間でのデータ連携～
Avatar for 田中 聖也 tanakaseiya
0
130
責任あるソフトウェアエンジニアリングの紹介4章・5章 / RSE_Ch4-5
Avatar for id ido_kara_deru
0
340
Python開発環境にハーネス適用を検討する
Avatar for yuuuka yuuka51
1
530
Gradle×GitHub_ActionsでCI時間を約50%短縮 ジョブ分割の設計と落とし穴 / Cutting CI Time by ~50% with Gradle and GitHub Actions: Job-Splitting Design and Pitfalls
Avatar for 冨澤宝斗 takatty
0
190

Featured

See All Featured
Building the Perfect Custom Keyboard
Avatar for Naoto Takai takai
2
770
Crafting Experiences
Avatar for Bethany Jepchumba bethany
1
160
The Illustrated Children's Guide to Kubernetes
Avatar for Chris Short chrisshort
51
52k
ReactJS: Keep Simple. Everything can be a component!
Avatar for Pedro Nauck pedronauck
666
130k
How Fast Is Fast Enough? [PerfNow 2025]
Avatar for Tammy Everts tammyeverts
3
580
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
Avatar for Tammy Everts tammyeverts
55
3.3k
16th Malabo Montpellier Forum Presentation
Avatar for AKADEMIYA2063 akademiya2063
PRO
0
130
How to Talk to Developers About Accessibility
Avatar for Jason CranfordTeague jct
2
210
We Are The Robots
Avatar for Honza Javorek honzajavorek
0
230
The AI Search Optimization Roadmap by Aleyda Solis
Avatar for Aleyda Solis aleyda
1
5.8k
Navigating Team Friction
Avatar for Lara Hogan lara
192
16k
The Anti-SEO Checklist Checklist. Pubcon Cyber Week
Avatar for Ryan Jones ryanjones
0
140

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