Working With Legacy Rails Apps

Ca839bc293e4ca6f9fa327cf95a414a9?s=47 Ahmed Omran
July 10, 2015
Programming
0
49

Working With Legacy Rails Apps

Ca839bc293e4ca6f9fa327cf95a414a9?s=128

Ahmed Omran

July 10, 2015
Tweet

More Decks by Ahmed Omran

See All by Ahmed Omran
Ca839bc293e4ca6f9fa327cf95a414a9?s=48 this_ahmed
2
100
Ca839bc293e4ca6f9fa327cf95a414a9?s=48 this_ahmed
1
90
Ca839bc293e4ca6f9fa327cf95a414a9?s=48 this_ahmed
0
25
Ca839bc293e4ca6f9fa327cf95a414a9?s=48 this_ahmed
4
4.7k

Other Decks in Programming

See All in Programming
52cc8a838bf44a589d2572833b2dd1b9?s=48 palkan
2
280
3b38214ae9927683d69680cb6161852b?s=48 jorgecastilloprz
0
1.7k
774a937b74096e82576b37678d00aeca?s=48 kishino
1
100
9987516c273a7874b12b742e7aef828f?s=48 smellman
1
540
42a6a049ac8f5265f31858a9509217fb?s=48 uhooi
0
140
15934fa2aa7b2ce21f091e9b7cffa856?s=48 manfredsteyer
0
150
E120f1fcd6d2811ea5e06d110566a543?s=48 tanakarian
0
290
15934fa2aa7b2ce21f091e9b7cffa856?s=48 manfredsteyer
0
140
3f2e97dc4e6a5daaf1cb8a406c533176?s=48 knqyf263
2
330
D6fcc16462fbe93673342da3ff5d8121?s=48 xhochy
0
110
75cf8176bf14811428f77d8fe737f0d5?s=48 konstantin_diener
0
110
D1804d3c315cbb850aaa88d2fbadc3cf?s=48 keitheis
0
160

Featured

See All Featured
25c7c18223fb42a4c6ae1c8db6f50f9b?s=48 mojombo
358
62k
3d6ace9554821d552146413bcdf874f6?s=48 trishagee
18
1.5k
245cee81a9c424266e5e401d844ea881?s=48 lara
15
2.5k
E76911cbe088e5b850d966de3fc7435b?s=48 robhawkes
52
2.7k
245cee81a9c424266e5e401d844ea881?s=48 lara
590
60k
Ef32e0b1ac5082450dc8c1fca3a26b5c?s=48 cherdarchuk
66
260k
11c84dff30266b907714802088852677?s=48 jasonvnalue
82
8k
D67fff74178013024d833b3eec6cf27f?s=48 lynnandtonic
268
16k
C157b16234f1e75e8eac3698c1d4414a?s=48 ddemaree
274
31k
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
166
19k
C86443373fbfe92996aa882d0d7a59f8?s=48 imathis
479
150k
C0b42577cfc2b321be3474618107e933?s=48 samanthasiow
56
6.2k

Transcript

  1. Working With Legacy Rails Apps @this_ahmed

  2. Working With Legacy Rails Apps @this_ahmed

  3. legacy code • untested code (Michael C. Feathers) • code

    someone else wrote (old gems, outsourcing, maintainers left) • difficult to work with • risky to change • but serves a useful function

  4. googling legacy code …

  5. every project has legacy code?

  6. None

  7. • learning & experimenting • ambitious applications • big project,

    developer churn, hiring outside help • bad code … even with the best of intentions • “Technical debt”
  8. None

  9. –Robert C. Martin “Even the most disciplined development team, knowing

    the best principles, using the best patterns, and following the best practices will create messes from time to time.”

  10. in the face of legacy code you can …

  11. None

  12. or…

  13. None

  14. Useful techniques

  15. Rebuild Refactor

  16. –Robert C. Martin “…taking a tangled, opaque, convoluted system and

    slowly, gradually, piece by piece, step by step, turning it into a simple, nicely structured, well-designed system.”

  17. Boy Scout Rule Clean up around you work area. Small

    fixes; small refractors.

  18. cover and modify • add unit test • test passes

    • modify code • test passes

  19. use mock objects to break dependencies

  20. None

  21. mock dependencies

  22. break complicated dependencies with seams

  23. None

  24. seam => put in method + stub

  25. first step to later refactor

  26. i don’t understand this code…

  27. Ask someone

  28. code archeology

  29. code archeology git blame / Github

  30. code archeology search code for context git blame / Github

  31. code archeology project management ticket git blame / Github search

    code for context

  32. code archeology git blame / Github project management ticket commit

    message search code for context

  33. review • boy scout rule • cover and modify •

    break dependencies with mocks and seams • understand code with archeology

  34. some parting thoughts

  35. unit test

  36. None
  37. None

  38. • code review • small git branches • add lots

    of context in pull request / commit message