The Problem with Perfect

Anyone with a creative role, whether it’s writing code or UX design, will tell you that there's one hump you have to learn to get over - starting even though the end result might not be perfect. This can be a bug fix, a new app, or building something in a new technology, but that first step is always the hardest. So often, we find ourselves staring at a blank page, lost, and frustrated. If we hold ourselves to the imaginary standard of perfect, the pressure quickly mounts.

Next time this happens to you, ask yourself what the perfect end goal is.

You may find that there is no “perfect.” Effective systems architecture is evaluating the tradeoffs and picking the best option - not the perfect one. You might find your idea of perfect is trying to predict other people’s reactions to your work - an un-winnable game. Trying to build something everyone will like usually turns out pretty bland. Building something people hate can be pretty funny.

Often, especially in side projects, I find that the problem with perfect is there's no room for fun. So next time you’re staring at the blank page, get a little mischievous. Prioritize the part of the project that will bring you the most joy. Make Bob Ross proud and let your mistakes become happy little accidents - you’ll learn more that way.

Hopefully you’ll find the blank page less intimidating when you’re more focused on fun than perfect.