If there is one thing I really hate it's deploying new code that has cruft/legacy shit already baked in. It just makes me feel awful. But sometimes, after so ma

If there is one thing I really hate it's deploying new code that has cruft/legacy shit already baked in. It just makes me feel awful. But sometimes, after so many months (or years, in at least one of my cases) on a project, I just say fuck it, and ship it (be it my code or a team member's). I definitely agree with your ethos though. I think there's a lot to be said for having some buffer between functionally complete code and a hard ship date so that you can leave things in a state that don't make you or someone else feel bad about things later.