I’m a solo dev. At a high level, I find that just writing down what I’m trying to achieve and referring to it often is critical. The most important things to understand are what you’re building, who your users are, and when you want to launch. Use this as a razor to determine what features to add/remove. This should not be complex - one sentence each! Try to make all decisions through this lens. Revise the lens as you learn more.
In terms of managing the day to do, my project has 4 or 5 modules and each has its own TODO and README in markdown. The README is where I explore the design and the TODO is obvious.
You don’t need fancy tools, what you need is a vision that pulls you along.
In terms of managing the day to do, my project has 4 or 5 modules and each has its own TODO and README in markdown. The README is where I explore the design and the TODO is obvious.
You don’t need fancy tools, what you need is a vision that pulls you along.