When building something, you want to do the best possible work everywhere. But optimizing every piece takes time and time is finite.

If you care about what you do, it's natural to want to do your best all the time. But "best" and "good enough" are not the same thing. You have to learn when and where to aim for each.

"Best" assumes unlimited time and perfect conditions.
"Good enough" understands context: deadlines, user needs and opportunity cost.

Knowing the difference isn't lowering your standards. It's applying them wisely.