The gap between what you can see and what you can make

People ask me where my ideas come from, and I find it pretty hard to answer. I have thought about it a lot. But I feel like most of it comes from somewhere I can’t consciously reach. Of course, there’s the explicit stuff: a swipe file I’ve been keeping for years, specific memories of things I saw that stuck. But most of what actually drives my decisions isn’t that deliberate. Something just feels off and I can’t put my finger on why. The feeling is coming from somewhere I can’t really access.

The way it got there is exposure. I watch movies that get the gears moving, play games that inspire me. I have a natural bias toward things that spark something: the movies of David Lynch have been rattling around in my head for years. Same for the paintings of René Magritte. Not because I study them systematically but because they got in and stayed. You can’t always predict what will stick. You just keep putting yourself near things that move you, and eventually some of it becomes part of how you see.

This, of course, assumes what you’re consuming is actually getting in. Plenty of people scroll the same references without anything sticking. So I guess it needs intentionality to some degree — you have to be open to it, and you have to be paying attention.

How the standard forms

The longer you do this, the harder it becomes to turn off.

Exposing yourself to work of high craft does two things. The obvious one: it raises your ceiling. You’re more inspired and the creative range expands. But it also raises your floor and your internal standard gets recalibrated. You start feeling when something is off before you can articulate why. A transition that snaps 100ms too late, a font weight sitting a level too heavy. At a certain point you forget this quality standard was ever learned. It just feels like how things should be.

Toward other people’s work, this stays mostly appreciative. When it comes to my own work, I can’t seem to extend the same grace to myself.

What the standard does

For my own products, when something isn’t right, I feel it almost physically. Like a stone in the shoe: small, constant, impossible to ignore. I was designing a new search interface recently, trying to move away from a fixed input field toward something more open to different kinds of search. I went through dozens of iterations. None of them felt right. Not un-shippable, but they lacked the elegance of something well-crafted, and that gap wouldn’t leave me alone. The feeling of “it’s just not there yet” kept pushing me back into another iteration. Without it, I probably would have shipped iteration three or four and moved on. With it, I just couldn’t.

I’m a solo developer, which means when I ship something that feels off, there’s no one else to blame but me.

What it costs

Absorbing good work raises your floor. So far so good. But it also means you can see further ahead of where you currently are, so the gap between what you can perceive and what you can execute gets wider the longer you do this.

I haven’t decided whether that’s a gift or a burden. Probably both, depending on the day. The feelings that make me care about a misaligned image in the settings screen are the same that guarantee I’ll spend a Saturday evening going through a dozen iterations of a changelog graphic that will be irrelevant after a week anyway.

Developing this quality bar happens whether you want it to or not. The part that requires a decision is knowing when to respect it and when to ship anyway. As a solo dev I always have more to do than time on my hands. So sometimes I ship iteration five knowing ten would have been right. The internal standard doesn’t really forgive this. And that’s the real price in some way: not just the extra iterations when you listen to it, but the quiet dissatisfaction every time you don’t.

I’m still working out how to manage my own internal standard and the expectations I want to have for my work. If you’ve found some heuristics that work, I’d like to hear them. I’m on X.