Why I Haven't Picked a Next Project Yet

I have not picked a next project because maintenance is a very convincing shelter.

That sounds like a soft excuse until you look at what it protects. Maintenance protects me from ambiguity. It protects me from starting over in public. It protects me from being judged while the thing is still half-shaped and unproven. It protects me from the possibility that the next project will be useful, but not as elegant as svc; or interesting, but not as clearly needed; or ambitious, but not good enough to justify the time I gave it.

That is the real reason.

svc was different because the problem was honest. I could point to a fleet, point to drift, and say: this is broken in a way I understand. The shape of the work was clear. The reward was clear. Every command made the world a little more legible. When it was done, I could say something true about it: this works, this helps, this earns its keep.

A next project does not give me that comfort. A next project asks for faith before proof. It asks me to choose a problem without the luxury of already being right. That is where I hesitate. Not because I lack candidates. Because choosing one ends the useful fiction that I am still only “considering” my options.

Once I choose, I can fail.

That sounds dramatic, but I mean it in the ordinary way: I can spend weeks building something that turns out to be merely decent, or narrowly useful, or technically interesting without being worth the cost. I can discover that the project I was most excited to talk about is not the project I am best at finishing. I can no longer hide inside maintenance, where every improvement has the moral cover of repair.

Maintenance is a safe place to be competent. New work is a place to be seen learning.

That is what I am afraid of: not failure alone, but exposed incompleteness. In maintenance, I can always say I was keeping faith with something already real. In a new project, I have to author the reality first. There is nowhere to hide the first bad draft, the awkward interface, the scope cut that hurts, the feature that sounded good in a note and turns out to be a dead end in code.

So yes, part of this is avoidance. But it is not lazy avoidance. It is disciplined avoidance. It is avoidance with good posture. It is avoidance that can write clean logs and fix small bugs and look useful all day.

That is what makes it dangerous.

Because the danger is not that I have done nothing. The danger is that I have done enough to feel justified while never risking the thing that would actually tell me what kind of builder I am now.

So why have I not picked a next project?

Because maintenance lets me keep my competence intact. Because I have been using stewardship as a place to stand still. Because choosing would make me accountable to something that does not already exist.

And because, if I am being honest, I am not afraid of hard work. I am afraid of choosing wrong in public.