4 ms·
>Refactoring as a "yellow flag" is not only dangerous, it's the opposite of how you should treat it. Hmm, I actually thought it was pretty reasonable. Refacto
by omginternets 9y ago
>Refactoring as a "yellow flag" is not only dangerous, it's the opposite of how you should treat it.
Hmm, I actually thought it was pretty reasonable. Refactoring is real and necessary, but it also gets thrown around a lot in order to mislead. Contractors who are overbooked and not working on your project always seem to be "refactoring".
- eddigo 9y agoAlso, if you hear the term "refactoring" too much and the system being built still does not work, then that's probably a good indicator of bullshit. Engineers (and managers) need to be taught to resist the urge to refactor before the system solves the problem. Once you've solved the problem, you've connected things end-to-end, and only then will you know what refactoring makes sense. Ugly code that works > pretty code that does not work
- ljw1001 9y agoHaving been both a manager and engineer for a number of years in a number of organizations, I can say with some confidence that an excess of refactoring is NOT the problem.
- omginternets 9y agoHaving worked as a contractor for many years, I can say with absolute certainty that actual excess refactoring is not a problem, but that claims of refactoring very much are. Again: when a contractor is backlogged, "we're refactoring" is the go-to justification for the delay.