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

Confident refactors

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →
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
テストコードのないプロジェクトにテストを根付かせる
Avatar for Toru Takahashi tttol
0
140
開発にAIを組織として取り入れる一歩目とその後
Avatar for 渋谷悠司 yujishibuya
0
220
AI時代に求められる思考のパラダイムシフト
Avatar for NRI Netcom nrinetcom
PRO
1
150
はじめてのAI-DLC
Avatar for 吉田真吾 yoshidashingo
2
530
Agentic Design Patterns
Avatar for Guillaume Laforge glaforge
0
190
自作エディターをOSSにして分かった、一人に刺さる開発が世界を動かす理由
Avatar for Shinya Saita shinyasaita
1
380
まだ道半ば、AI-DLCを歩み始めている話
Avatar for 荒木 ARK news_it_enj
2
180
イベントで大活躍する電子ペーパー名札 〜その３〜 / ビジュアルプログラミングIoTLT vol.23
Avatar for you（@youtoy） you
PRO
0
140
シンデレラなんかになりたくない！ガラスの靴が割れた時代にどう歩く？
Avatar for Nomizo Nomizo nomizone
0
190
ソフトウェアサプライチェーン攻撃対策として今からサクッとできること
Avatar for GMO Flatt Security flatt_security
2
140
20260528_生成AIを専属DSに_Howの次にすべきことを考える
Avatar for NobuakiOshiro doradora09
PRO
0
200
Generative UI × A2UI で AI エージェントを作った話　AI-DLC も使ってみた！
Avatar for たけのこ kmiya84377
1
160

Featured

See All Featured
New Earth Scene 8
Avatar for Sydney Stone popppiees
3
2.3k
Scaling GitHub
Avatar for Zach Holman holman
464
140k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
Avatar for panda_program panda_program
122
21k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
Avatar for Chris Coyier chriscoyier
508
140k
How to train your dragon (web standard)
Avatar for Monica Dinculescu notwaldorf
97
6.6k
How People are Using Generative and Agentic AI to Supercharge Their Products, Projects, Services and Value Streams Today
Avatar for Helen Beal helenjbeal
1
190
Dominate Local Search Results - an insider guide to GBP, reviews, and Local SEO
Avatar for Greg Gifford greggifford
PRO
0
170
Paper Plane
Avatar for Katie Cordina Lindsey katiecoart
PRO
1
50k
Data-driven link building: lessons from a $708K investment (BrightonSEO talk)
Avatar for Szymon Słowik szymonslowik
1
1.1k
Building Experiences: Design Systems, User Experience, and Full Site Editing
Avatar for Michelle Schulp Hunt marktimemedia
0
510
WENDY [Excerpt]
Avatar for Tessa Abrams tessaabrams
10
37k
Jamie Indigo - Trashchat’s Guide to Black Boxes: Technical SEO Tactics for LLMs
Avatar for Tech SEO Connect techseoconnect
PRO
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