Something I keep having to remind myself, and other engineers in teams I work on is "Good enough is good enough". There are plenty of projects they're working

Something I keep having to remind myself, and other engineers in teams I work on is "Good enough is good enough". There are plenty of projects they're working on that could be better if they could spend another week or two working on it. But is it sufficient to actually justify that time vs working on other projects? Can we quantify how much difference that extra polish will make several months down the line? I find it hard to fight myself, because no small part of me sees my work in the same way Durnik does: > "Always do the very best job you can," he said on another occasion as he put a last few finishing touches with a file on the metal parts of a wagon tongue he was repairing. > "But that piece goes underneath," Garion said. "No-one will ever see it." > "But I know it's there," Durnik said, still smoothing the metal. "If it isn't done as well as I can do it, I'll be ashamed every time I see this wagon go by - and I'll see the wagon every day!" I landed a huge improvement on a product at work about 9 months ago, after months of work on it. Cut execution times down by a huge amount and made the customer experience more consistent. Managers look at it and see what I achieved. I look at it and see all the things I don't like about it, all the ugly hacks and things that make it work.