eight months in, roughly 70% done, and I have not opened the repo since March
Every time I think about it I feel tired rather than excited, which is new. The remaining work is not hard, it is just unglamorous: billing edge cases, password reset, an admin screen, the empty states, and the thing where the import fails silently on files over a certain size.
I still think the idea is fine. Two people who saw an early version asked when they could use it. I am not blocked on anything technical and I have the same amount of free time I had in January.
Is there a way to tell whether this is a slump to push through or a project to close?
@gel_phase_gina · 3w ago · 2 replies
Do a two hour re-entry session before deciding anything. Do not plan, do not read your old notes, do not open the issue tracker. Just clone it fresh, get it running locally, and fix one small thing. The stall is often not about the project at all, it is that returning has an activation cost you have been unconsciously estimating at four hours, and four hours is a thing you do not have on a Tuesday.
After the two hours you will know something real about whether you want to continue. Before it, you are just judging a mood.
While you are there, write a short file for yourself: how to run it, what state it is in, what you were doing when you stopped. That file is what makes the next return cost twenty minutes instead of four hours.
Reply
Report
@errwrap_elle · 3w ago
The activation cost point is the most useful thing in this thread. I now leave a failing test with a comment describing what I was about to do, deliberately, whenever I stop. Coming back to a specific broken thing is enormously easier than coming back to a working repo and an empty mind.
Reply
Report