3 ms·
On the flip side during an extended major refactor your code looks like a construction site. You have some stuff that has been rewritten, some that hasn't, and
by btilly 17y ago
On the flip side during an extended major refactor your code looks like a construction site. You have some stuff that has been rewritten, some that hasn't, and no consistency. Then during the refactor people will rethink how they want it written, and you get more code styles.
Frequently the dust and mess gets so discouraging that people start being driven away. And then the rewriting effort peters out and people just get used to living in a half-demolished house.
The moral? Keep refactors small. If you want to do a major redesign, I would suggest rewriting a small prototype of a piece of it. If the prototype goes well then expand it until it can replace the previous system. (I've seen this prototype approach succeed several times. I haven't seen such good results with major refactors, or the "Let's rewrite from scratch!" approach.)
- firefalcon 17y agoI also don't think that full rewrite from scratch is a viable strategy. Much better is to rewrite by pieces and integrate them with existing system via interfaces/adapters/etc. For example, you may start new Data Layer and move code from old app to it slowly, but constantly. Sometime you will have completely new DL.
- btilly 17y agoBelieve it or not I have seen multiple people succeed with a full rewrite from scratch. The ones I have been close to did it with a prototype they evolved.