Most people who can't feel proud are chasing the next target out of ambition or anxiety. That isn't your problem. Your problem is stranger and more specific: the moment a thing is solved, it goes dead to you. While it was broken, the engine wouldn't fire, the bug was live, the system was a puzzle, it held your full attention. The second it works, it stops being interesting. It becomes the most boring object in the room. So you wipe your hands, glance around for whatever is still broken, and walk toward it. You didn't move the line out of greed. The win just lost its grip on you the instant it stopped being a problem.
From the inside, this doesn't even feel like skipping a win. It feels like nothing happened. There was a thing that didn't work, you got it working, and now there's a different thing that doesn't work. Where, exactly, is the moment you were supposed to feel proud? You were never standing in it. You were already three steps into the next fix. And because you don't trust soft, backward-looking feelings anyway, 'let yourself feel proud' sounds like an invitation to stand around admiring yourself, which is the last thing a hands-on, present-tense person wants to be caught doing. So you never do it, and the work stacks up behind you, finished and instantly forgotten, paying you nothing.
The fix goes dead because the problem was the point
Understand the mechanism before you try to fix it, because this isn't a willpower issue. Your attention is hooked by problems, not products. A live problem is a thing you can take apart, probe, and beat. A finished product is inert — there's nothing left to do to it, so there's nothing left for your mind to grab. The completed work doesn't fade because you're modest or restless. It fades because the exact quality that made it absorbing — its unsolvedness — is the quality you just destroyed by solving it.
So when you go looking for pride and feel only a flat 'meh,' you're not broken and you're not ungrateful. You're trying to feel something about an object your attention has already filed as dead. That's why the standard advice — 'just take a moment to appreciate it' — slides right off you. You can't appreciate the thing as a thing; it bores you now. What you can still respect is the work: the diagnosis, the steady hands, the call you made when it wasn't obvious. The pride isn't in the finished engine. It's in the fact that you were the one who could make it run.
Pride isn't sentiment — it's an accurate read of your own competence
The word 'proud' probably makes you wince a little, because it sounds like a feeling you'd have to perform — chest out, soft music, telling yourself you're great. That's not it, and if it were, you'd be right to refuse it. Strip the sentiment off and pride is just an honest entry in your own logbook: this was hard, I was the one who could do it, and it now works because of decisions I made. That's not a mood. That's data about your capability, and you of all people should want it accurate.
Refusing to log it isn't humility — it's a measurement error. You're meticulous about your tools and your diagnoses, but you keep a running ledger of your own competence that's blank on the credit side and detailed on the debit side. Every fix that didn't hold, you remember. Every fix that worked, you forgot the moment it worked. Of course you feel like you're treading water. You've been keeping the books in a way that's mathematically guaranteed to never show a gain, and for a person who values getting things right, that's a sloppy way to track the most important system you run.
Why the empty tank eventually catches up with you
You can run a long time on pure interest in the next problem — longer than most types could. But interest is fuel that only flows while the problem is live, and there are stretches where nothing in front of you is interesting: tedious work, a dry patch, a long grind with no satisfying click at the end. In those stretches the people who banked their wins have something to draw on. You have nothing, because you spent every win the instant you earned it by not noticing it. The tank reads empty not because you've done little, but because you never let any of it register as deposited.
This is where the detachment quietly costs you. Withdrawing from a finished win feels clean and efficient in the moment — no fuss, on to the next. But over years it means you've built a great deal and carry the felt sense of having built nothing. That's not freedom; it's a leak. Letting yourself actually clock a win isn't getting sentimental or going soft. It's plugging the leak, so that when you hit a stretch with no live puzzle to ride, you're not running on fumes with a full warehouse of work behind you that you've trained yourself not to see.
Clock it before it goes cold — the ninety-second move
You won't do anything that requires standing around feeling things, so don't. Make it a fast, mechanical step, the kind you'd build into any process. The instant something works — before you reach for the next broken thing — stop for ninety seconds and do one concrete act: note in a line what the problem was and the specific call that cracked it, or just look at the working thing once and say plainly, 'that was a hard one and I got it.' The window is short because the fix goes dead fast, so you have to catch it while it's still warm, not at the end of the week when it's already inert.
Keep a running list of solved problems if a felt moment won't take — a literal log of things that were broken and now aren't because of you. It plays to your strengths: it's concrete, it's true, and it requires zero sentiment. On the dry days, you read it, and it does the job the missing pride was supposed to do. This isn't about becoming someone who basks. It's about closing the loop on a win the same way you'd close any job properly — confirm it holds, log the result, then go find the next thing that's broken. You were always going to walk toward the next problem. Just don't leave the last one unlogged on your way there.
The problem went dead the moment you solved it — that's how your attention works, and it's not going to change. But the competence that solved it is real, and it's yours, and you keep forgetting to write it down. Clock the win in ninety seconds while it's still warm, log it, and then go find the next broken thing. You were never going to stand around admiring it. You were just leaking proof of your own skill out the back door, one finished job at a time.