There's a specific shade of hope that shows up right before a status page loads. You already know the feeling if you've ever refreshed a dashboard waiting for a build to pass, an application to clear review, a request to get accepted. For half a second before the page renders, you're neither approved nor rejected. You're just waiting, and in that half second, anything is still possible.
I've spent an embarrassing amount of my life chasing that half second. Not the approval itself, exactly — the moment right before it, when the outcome hasn't been decided yet and you get to hold both futures in your hands at once.
I noticed this most clearly a few weeks ago, staring at a percentage on a screen. Eighty percent ready. Not done. Not rejected. Just close, with a list underneath telling me exactly which boxes were still unchecked. And I felt something I recognized immediately, because I've felt it my whole adult life in different costumes: the itch to fix the last twenty percent right now, tonight, so the number would move.
That itch is familiar to anyone who's ever waited on a code review, a college acceptance, a callback after a first date that went well. The percentage changes shape but the feeling underneath it doesn't. We treat approval like it's a finish line, when really it functions more like a drug — the relief is real but it's short, and the moment it fades you're already looking for the next thing that needs approving.
I think this is what nobody tells you about building anything, whether it's a piece of software, a body of creative work, or a version of yourself you're proud of: the approval was never the actual goal. It just felt like the goal because it's measurable, and measurable things are easier to chase than the vague, formless thing underneath them, which is usually something closer to I want proof that this was worth doing.
That's a much harder thing to sit with, because proof doesn't always arrive on a schedule. Sometimes it doesn't arrive at all in the form you were expecting. You can do everything right — write the honest thing, build the useful thing, show up consistently for months — and still get told "not yet," or worse, hear nothing at all. Silence is its own kind of rejection, maybe the cruelest kind, because it doesn't even give you a list of boxes to fix.
I used to think the fix for this was patience. Just wait it out, I told myself, as if patience were a neutral, passive state you could simply switch on. But real patience isn't passive at all — it's an active refusal to let your sense of worth get outsourced to something that hasn't answered you yet. That's a much harder skill than waiting quietly. It means doing the work today with the same care you'd give it if you already knew, with total certainty, that no one was ever going to check a box for it.
I don't think I've mastered that. I don't think most people do, not fully, not permanently. But I've gotten better at noticing the exact moment I start writing, coding, or making something for the approval instead of toward the thing I actually believe in. There's a subtle shift that happens — the work gets a little more cautious, a little more calibrated to what I imagine a reviewer wants to see, and a little less honest. You can feel it happening in real time if you pay attention. The sentence gets safer. The melody resolves the way melodies are "supposed to." The commit message gets vaguer because you're suddenly worried about how it reads to someone judging it, instead of whether it's true.
That's the real cost of chasing approval too hard — not that you might not get it, but that you start optimizing for the appearance of worthiness instead of the substance of it. And the two are not the same thing, even though from a distance they can look identical for a while.
What's helped me isn't some elegant reframe. It's smaller and stranger than that. I've started asking myself, before I ship anything, whether I'd still be glad I made it if no checkmark ever came. Not glad in a performative "I don't care about outcomes" way — I do care, deeply, that's not the point — but glad the way you're glad you kept a promise to yourself even when nobody was watching to confirm you kept it. If the answer is yes, I ship it and let the approval be whatever it's going to be, on its own timeline, out of my hands. If the answer is no — if the only reason I'm proud of it is the number it might produce — that's usually a sign I've drifted from building the thing to performing the appearance of the thing.
I still refresh the dashboard. I still feel that half-second of held-breath hope before the page loads. I don't think that instinct ever fully goes away, and honestly, I'm not sure I'd want it to — it means I still care about the outcome, which is better than the alternative. But I've stopped needing the checkmark to tell me whether the work was worth doing. That answer, it turns out, was always mine to give myself first.
The approval, when it comes, is just someone else finally catching up to something I already decided was true.