2024 Public Training Schedule
November 18 – 21, 2024 – Agile Analysis and Design Patterns
Half-Day Sessions
December 9 – 12, 2024 – Agile Analysis and Design Patterns
Half-Day Sessions
Follow me on Twitter:
Blog Post Categories
- Announcements {19}
- Articles {2}
- Bits and Pieces {74}
- Blogosphere {1}
- Bonuses {2}
- Build in Small Batches {27}
- Collaborate {38}
- Create CLEAN Code {34}
- Implement the Design Last {11}
- Integrate Continuously {30}
- Off-Topic but Interesting {3}
- Rants {82}
- Refactor Legacy Code {24}
- Say What, Why, and for Whom Before How {22}
- Seven Strategies {38}
- Specify Behaviors with Tests {17}
- Write the Test First {27}
Archives
Privacy Policy
(c) 2024 To Be Agile
- February 26, 2009 ( 2 comments )
- Rants
I often ask my students if they prefer to write new code or maintain existing code. Ok, it is a silly question. Most people say they rather write new code, not just because it is more fun but also because it seems the worse bugs show up when we try to modify existing code to meet a different purpose than it was originally intended. Since senior developers tend to prefer working on new and exciting projects, it is often junior develpers who get stuck maintaining existing systems.
I heard a long time ago that Sony was experimenting with a practice of having their new hires fresh out of engineering school work on their new products and their senior engineers focus on redesigning existing products. Looking at the mountains of legacy code that most of my clients have and knowing it is often their critical assets I wonder if we should do something similar and try harder to make legacy code more manageable.
-
Pingback: Surgery on Legacy Code – 1
-
Pingback: レガシーコード手術 - プログラマーのフロントライン
{2 Trackbacks }
Previous Post: « “That’s Not TDD”
Next Post: On Techniques for Agile Trainers »