
Software Engineering Radio - the podcast for professional software developers SE Radio 656: Ivett Ördög on Rewrite versus Refactor
Feb 20, 2025
Ivett Ördög, with over 15 years of experience in software development, discusses the critical choice of rewriting versus refactoring in software projects. She challenges the dogma of 'never rewrite,' emphasizing the importance of customer value and phased implementation. Ivett shares insights on legacy code, the nuances of technical debt, and offers strategies for gaining management support on large projects. With practical examples, she highlights when to opt for a rewrite and how to avoid catastrophic pitfalls in scaling and communication.
AI Snips
Chapters
Books
Transcript
Episode notes
Success Often Creates Legacy
- Successful companies often carry legacy code because keeping codebases perfectly clean is expensive.
- Early tradeoffs to move fast usually create maintainability burdens later.
CSV Import Turned Into Performance Nightmare
- A PHP codebase written by junior engineers mixed logic, templating, and DB calls and became extremely hard to maintain.
- An import routine did per-field SQL updates and required rewriting behavior to fix performance.
Dashboard As Informal Tests
- Ivett refactored her own rushed frontend but found the backend easy to change despite lacking tests.
- A dashboard page acted as a live feedback loop, replacing formal tests for safe refactoring.






