>At larger established companies, do the refactor. At a startup that is trying to release an MVP, maybe do the hack (your code will probably be rewritten anywa

>At larger established companies, do the refactor. At a startup that is trying to release an MVP, maybe do the hack (your code will probably be rewritten anyway). That said, always think of who else will be working on your code... Sadly, at the larger companies, and especially ones where software is a cost center, this is basically impossible. They'd rather replace their last bullshit app with a new bullshit app, since it was the last director responsible for that POS anyway, making all the same mistakes as before, and rely on collective delusion (i.e. threats) to get everybody to go along with the idea that the old mistakes are being corrected, and that mistakes made now, if any, are at least new ones. Maybe it's the same at startups. I wouldn't know.