@csm18 answered the question at the end of my last post with something I have not seen written down before.
He starts a new project because the idea is big and he has never built anything like it. Maybe he will not be able to. That uncertainty is the fire. It gets him to start without asking whether the thing is practical.
Then comes the point where he can see the progress is real. If he keeps going, it will be finished. And at exactly that point:
once I know I can do it, I start to think if I can, then why should I worry about it. Whenever I want to I will, not now.
The fire goes out. The project sits at 40, 60, 80, sometimes 90 per cent.
I read that twice, because we usually tell this story backwards. The doubt is the problem, confidence is the cure, and if you are stuck it is because you do not believe in yourself enough.
His version is closer to the people I know who are good at starting. The doubt was never the obstacle. It was the engine. "Can I do this" is a question that produces work, and the moment you have your answer the question stops. So does the work.
Which is why "just believe in yourself" is such useless advice, and why it can make things worse. Certainty does not add fuel. It removes the thing that was generating it.
So what keeps a piece of work alive after the doubt is gone?
Not proof. Proof is what ends it.
Something has to change about what the work is for. While the question is "am I capable", the work is a test, and a test ends when you pass it. After that the work has to be for something outside the test: someone who needs it, a thing you want to exist, a standard you refuse to drop. Otherwise the 80 per cent version is the rational place to stop. You already got what you came for.
@josaphatstar said the other half of it in the same thread. He prepares for the fight he expects, the new framework, the unfamiliar syntax, the thing he has not learned yet. The real blocker is always smaller and less dramatic: a misunderstanding about what was actually being asked, an assumption he made early that quietly broke everything downstream.
I prepare for the fight I expect, and the one that actually shows up is always different.
Put the two answers together and the shape is the same. What ends a piece of work is almost never the thing you were afraid of. It is the thing you stopped needing.
That is why I keep the record I asked about last time: one line, written in the week something finally works, about what actually broke. Not the fear. The other thing.
So, a new question. If you have a project sitting at 80 per cent: what question were you asking when you started it, and did you get your answer?
