I couldn't agree with you more. I think wanting to aim for perfect code and a perfect project is okay, but we need to know when it is time to move on and focus on the next most important thing.

I've worked with devs that focused so much on having perfect code that they missed deadlines or burnt out working overtime to "improve" something that provided barely any benefits.

I think the worst case I've seen is a dev working overtime to refactor and change a lot of code that we weren't even working in. The changes ended up going unused because QA and the stakeholders didn't have the time to test and didn't think the improvements were worth it compared to other priorities.