The big ball of mud
There’s a beautiful software development concept named the Big Ball of Mud.
If you’re not a developer (I’m not either but am a friend to a few), you may imagine software development as an elegant exercise in architecture, but that’s rarely the case. A big ball of mud is what most software looks like under the hood because budget, priorities, deadlines, skills, resources …
The beauty of the Big Ball of Mud though, is that however messy, it works! It is unthinkable to just throw it away and start from scratch. There’s so much you just don’t understand about the system; you can never know what you’re getting yourself into.
Draw your own parallels here; I’m sure you’ll find that you have your own mudballs to deal with, and although it’s fun to play the architect, you can provide the most value only if you’re also willing to get your hands dirty.

Oh this is nice. I haven't heard that term despite being hitched to a software builder. But I love this concept because things are never perfect and it's always messy and I think this is more and more true. Being able to live in the mess while still being able to build towards your vision is a critical skill. I used to think that starting over was an opportunity to build perfection. I no longer feel that way, nor is perfection what I care to aim for. I now cultivate my capacity for grit.