[leros]

I don't project manage and code at the same time. I find that leads to bouncing around and not making effective progress. I treat myself like a small team of individuals.

I'll dedicate time to just project management. I'll become a project manager and lay out the requirements, break that down into tasks, and prioritize. Then I'll take one task and focus on that. For example, an early task might be designing the overall system architecture, so I'll become a software architect and work on that. A next task might be coding a feature. So I'll become a developer and code up that feature.

If I ever find myself mixing roles into a single work session, it's usually time to take a step back and organize myself a bit more.

[muzani]

This was how I leveled up at solo work. At least 20% of the time goes into planning everything out. Aim before firing. You can easily spend hundreds of hours coding a thing nobody wants. That's how everyone gets burned out. Most of the docs for these are written on the train, in queues, in bed, so I can just jump into coding when I'm at an actual keyboard.