All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why Refactoring Should Not Be on the Backlog: Continuous Code Improvement

By

dhorthy

4mo ago· 5 min readenOpinion

Summary

Ron Jeffries argues against putting refactoring stories on the product backlog, explaining that refactoring should be done continuously as part of regular development work rather than treated as separate backlog items. He contends that deferring refactoring leads to accumulating technical debt, which slows down feature development and degrades code quality over time. The article advocates for the agile practice of continuous refactoring as an integral part of the development process, not something to be scheduled or backlogged.

Key quotes

· 4 pulled
There has recently been a lot of noise on the lists, and questions at conferences, about putting refactoring 'stories' on the backlog.
Even if 'technical debt' has grown up, this is invariably an inferior idea.
When our project begins, the code is clean. The field is well-mowed, life is good, the world's our oyster.
We can build features smoothly and easily, though we always seem to take a few little twists and turns.
Snippet from the RSS feed
This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated.
Copyright © 1998-forever Ronald E Jeffries

You might also wanna read