Change Quote by Andrew Hunt
““Don't be a slave to history. Don't let existing code dictate future code. All code can be replaced if it is no longer appropriate. Even within one program, don't let what you've already done constrain what you do next -- be ready to refactor... This decision may impact the project schedule. The assumption is that the impact will be less than the cost of /not/ making the change.””
About This Quote
Source Book: The Pragmatic Programmer, 1999
Encourage continual improvement by refactoring code when it no longer fits, even if it risks schedule delays.
In simple terms: Update code when needed, not when convenient.
Key Takeaway
Refactor proactively, accept short‑term cost for long‑term health.
Themes
software development
maintenance
agility
Mood
pragmatic
reflective
Type
advice
technical
When to use this quote
- legacy system upgrades
- feature additions
- team code reviews
- project planning
Key Concepts
technical debt
refactoring
risk management
Questions to Reflect On
- How do you balance technical debt against delivery deadlines?
- When is it justified to postpone refactoring?
A Different Perspective
Refactoring can delay releases and may be resisted by stakeholders.
![“I kind of pride myself on coming onto things that are well-oiled machines and finding a way to bring what I bring and fit in, and raise it to another level if I can. And this [Code Black ] has been another one of those really fun success stories, much like Parks And Recreation, although obviously…” quote by Rob Lowe](https://sms4smile.com/quotes/img-quotes/ea3/rob-lowe-855_black_i-kind-of-pride-myself-on-coming-onto-th_6557.jpg)
