Why this one in particular gets avoided
Side projects stall in planning because planning is genuinely enjoyable and produces the feeling of progress without any of the risk. Choosing the stack, the name, the domain, the perfect first feature — none of it can fail, which is precisely why it can continue forever.
The moment a real version exists it can be judged, including by you, and that is the actual threshold being avoided. It is worth knowing that: the resistance is not about time. People with no free evenings still ship things; people with free evenings still plan.
Then, in order
- Make it do exactly one thing, badly, end to end.
- Show it to one person, or just use it yourself once.
- Write down the single most annoying thing about it.
- Fix that one thing next session. Repeat.
What one 25-minute session gets you
One session is enough to make a bad version exist. A bad version that exists beats a perfect one that is still being planned, and it is the only thing that reliably makes the second session happen.
That is the whole method DuckDoro is built on: pick the thing you are avoiding, make it small enough to begin, and give it one calm session before the day fills up. If you want it as a daily habit rather than a one-off rescue, that is eating the frog — and DuckDoro keeps exactly one frog slot open every day.