My Worst Setback Was Also My Mildest

I have had setbacks that cost more than this one. A channel with six hundred videos deleted overnight. A codebase lost to a file path, with two hundred borrowed euros inside it. Measured in destroyed things, the last six weeks cost nothing at all.

I would still call them the worst setback I have had. That is not a paradox and it is not modesty about the earlier ones. It is a straightforward consequence of what a setback actually is, and it took me until this week to state it plainly enough to be useful.

What happened, measured

Late June into the first week of August, roughly six weeks. My phone reported an average of thirteen hours a day of screen time. Tasks slipped to tomorrow, then stopped being written down, which is the part that matters: an untracked task is not a delayed task, it is a deleted one. There were days I did not open the repository.

There was no decision anywhere in that. Nobody chooses a six-week drift. It assembles itself out of individually reasonable days, and by the time the shape is visible from the outside it has already been the shape for a month.

Why “worst” is the right word for the mildest one

Every setback before this was something that happened to the work. The channel was hacked. The project broke because I restructured files without knowing what version control was. Both were expensive. Both were also, in a specific sense, easy: there was a technical thing I did not know, I learned it, and the same failure could not happen twice.

This one had no technical fix, because nothing was technically wrong. The code was exactly where I left it. The users kept using it. The Discord kept growing while I was not there, which I found genuinely disorienting, and which is worth saying because it is the clearest evidence that the project was not the problem.

The only input that failed was the one I fully control. That is what makes it the worst category, independent of the size of the loss.

The three causes

I can name three, and I do not think any of them is an excuse. They are variables, and variables are more useful than excuses.

Burnout. The obvious one, and the one I had been ignoring for months on the grounds that I was young enough for it not to apply.

A relationship ended in that window. I am not going to write about it beyond saying that it happened and that it was a real input, not a footnote.

I stopped believing the goal was reachable. Not dramatically; there was no moment of despair. I would open the roadmap and the honest, flat thought was this does not work. Once that thought is available, every hour of work has to be justified against it, and most hours lose that argument.

The three compound. Burnout lowers the quality of your reasoning, bad reasoning makes the goal look unreachable, an unreachable goal removes the reason to recover from burnout. None of them individually would have cost six weeks.

The two weeks in the middle

Ten days into July I went to Dublin for two weeks. Two things are true about it and neither cancels the other.

It was the first time I had been in an English-speaking country, and English stopped being a subject and became the medium everything happened in. I found a calisthenics community training outdoors and trained with them. I would take the trip again without hesitating.

It was also two weeks I could not move, inside six weeks I should have. The trip was not the cause of the drift (the drift had a two-week head start on it), but it was two weeks of runway spent, and the launch date did not shift to make room. Both of those are just facts about the same fourteen days.

Why the timing made it expensive

Two constraints were sitting under all of this the whole time.

The first is a launch date I cannot genuinely move. Not “would prefer not to move”: the kind that has other people’s expectations attached to it.

The second is that my parents put real money into this. Every previous euro in this project was mine, or borrowed from a cousin, or lost. This is the first time I have been spending money that belongs to people who will not ask for it back and will not say anything if it goes badly. That is a different weight than debt. Debt is a number. This is not.

A mild setback with those two things underneath it costs more than a severe setback without them. The severity of a setback is not a property of the setback. It is a property of when it lands.

The recovery was slow, and that was new

Every previous recovery had a day. Something happened, or I decided something, and the next morning was measurably different. I had that experience often enough to start treating it as the mechanism, as if recovery were an event you wait for.

This one had no day. It had a slope, and a shallow one. The first week back was mostly opening the project and closing it. The second was real work at maybe half rate. Nothing about it felt like a turnaround while it was happening, and I want to be precise about that because the version of this story with a snap-back day in it would be a lie about a fairly important detail.

What actually moved it was not motivation. It was three constraints tightening at once: a date that would not move, money that was not mine, and pressure that kept accumulating until working was simply the only remaining option. I did not decide to come back. I ran out of alternatives to coming back.

That distinction (constraints move you, motivation does not) is the one thing here I would defend as generally true.

Where this actually stands

Back on track is accurate. Recovered is not.

March is my reference point. In March I was going full throttle, and I know what that feels like from the inside well enough to measure against it. I am not there. I am maybe two thirds of it, and I would rather write that down than round it up, because the rounded-up version is how a six-week drift starts.

What I would extract from it

1. Measure the input, not the mood. Thirteen hours a day of screen time was observable weeks before I drew any conclusion from it.
2. An untracked task is a deleted task. The list going quiet was the first real signal, ahead of anything I noticed about myself.
3. Severity is about timing, not size. The same six weeks in March would have been an annoyance.
4. Constraints recover you; motivation does not. If a recovery needs to be reliable, build the constraint before you need it.
5. A slope counts. Waiting for the day you snap back is a way of not starting on a Tuesday at half rate, which is how it actually goes.
6. “Nothing broke” is not “nothing happened.” This one left no wreckage to point at, which is precisely why it ran for six weeks unchallenged.

Launch is next, and it is close. I will write about that one once it has actually happened.