3 ms·
> And of course, that dirty code will be refactored later on. In my experience, the same product development lifecycles and business priorities that led to the
by otterley 13y ago
> And of course, that dirty code will be refactored later on.
In my experience, the same product development lifecycles and business priorities that led to the dirty code in the first place will cause it to live forever. Code that works doesn't tend to get refactored unless it needs to be revisited for some other business purpose.
- Draiken 13y agoI partially agree... normally this is a symptom of someone selling it as being something super simple to do for the managers. Personally I make it clear to them that if they need something impossibly fast, I'll need to come back for it later or it will cost us in the long run. When you do that, it's their choice to leave crappy code there, and later on you can point that out, when you need double the time to change that crappy little piece of code. But I've seen managers (that should know better) that just take the fastest path always and just don't care, unfortunately it happens :(