on finishing things

i have a folder on my laptop called wip. it has forty-three projects in it. maybe three of them will ever see the outside of that folder.

every one of them started with the same clean feeling — a fresh repo, a working hello world, a head full of the version of it that didn't exist yet. that part is the easiest thing in the world. the hard part, the part i've been quietly bad at for years, is the 20% at the end where the idea stops being fun and starts being work.

#starting is a different skill from finishing

starting is cheap. starting is mostly permission you give yourself — a blank page, an hour, some enthusiasm. any half-decent idea can carry you through the first weekend.

finishing is what comes after the enthusiasm runs out.

it's the part where you still have to fix the deploy pipeline even though the interesting problem is already solved. the part where you have to write the readme, the onboarding, the empty-state screen. the part where the bug you'd been avoiding for a month is now the only thing standing between you and "done".

they're not the same skill. and nobody really tells you that until you're three years into treating them like they are.

#the quiet cost of unfinished things

i used to think unfinished projects were free. they lived on a hard drive, they didn't take up physical space, they weren't technically costing me anything.

that's wrong.

every unfinished thing i own is carrying a little bit of my attention, whether i look at it or not. when i open my laptop there's a faint background pressure — you said you'd ship that, remember? — and it drags on everything new i try to start. you can't fit a fresh project into a head already full of half-ideas.

an unused tab is cheap. forty unused tabs is a tax.

#"done" is a real state

the thing i've been forcing myself to accept lately is that "done" is a real, achievable state — not a myth, not a moving target.

it doesn't mean perfect. it doesn't mean you've covered every edge case. it doesn't mean you've built the thing your head was imagining on day one. it means you've drawn a box around it and said this version ships.

the projects i've actually shipped are never the ones that are finished in some grand sense. they're the ones where i got honest about what "good enough" looked like, cut everything else, and pushed.

the ones still rotting in wip are mostly there because i couldn't bring myself to make that cut.

#small finishes compound

i've been running a dumb experiment for the last couple of months — finish one small thing every week. not a masterpiece. not a side business. just one closed loop.

the thing i didn't expect is how much it changes how i feel about doing things.

starting the next project is different when you're not carrying around a quiet pile of broken promises. you approach it with the expectation that it's going to end, because most of the recent ones did. that's a completely different mental posture than the one you have when you've left yourself a trail of half-finished ruins.

finishing is, as much as anything, a habit of believing you finish things.

#the reframe

i used to think my problem was that i started too many things. i don't think that anymore. the problem isn't the starting — starting is where most of the curiosity and energy in my life actually lives.

the problem is that i never gave finishing the same respect i gave starting.

so i'm trying to fix that quietly, one closed loop at a time. not every project. not the grand ones. just the small, boring ones — the tool, the write-up, the bug fix, this post.

finish it. ship it. close the tab. move on.

the folder called wip will probably always exist. i just want it to get a little smaller each month, instead of a little heavier.