One thing not to forget is that if you unleash refactoring on a grand scale you'... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		rumcajz on May 15, 2014 \| parent \| context \| favorite \| on: The Eternal Struggle Between Business and Programm... One thing not to forget is that if you unleash refactoring on a grand scale you'll end up with second version syndrome. Thus, management has a problem. To allow refactoring, they need to believe there's a technical person in charge that is able to keep the refactoring in check. But, as a manager, how would you asses that?

icebraining on May 15, 2014 [–]

Isn't the solution to allow very regular (daily?) refactoring, instead of pilling new stuff for weeks and months and then having a big refactoring party?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact