Very interesting observation. This resonates well with me and puts into words something I've been contemplating for years. I used to describe myself as a perfec

Very interesting observation. This resonates well with me and puts into words something I've been contemplating for years. I used to describe myself as a perfectionist, but today I'd rather be described as a pragmatist. You can't ignore critical details, but neither can you be so focused on getting every detail perfect that the big picture ends up worse. This is typical when designing software: There's limited time and resources available, and you often need to make a difficult tradeoff between the time taken to create something that's (perfectly?) maintainable long-term, and saying "enough is enough, we're losing money every day that we don't release". I get the impression that people are rarely able to keep both of these concerns in mind. Many skilled developers ignore the long-term opportunity cost of taking a long time to write "perfect" code, whereas many managerial types ignore the long-term technical cost of shipping poor-quality, difficult-to-maintain code.