Productivity for the solo developer

When you’re responsible for code, product, support and promotion, it’s easy to get lost between tasks. A few practices help keep focus and progress visible.

Define one priority at a time

Pick one important thing per day or per week (e.g. “this week is checkout” or “today is fixing bug X”). Everything else goes on the list for later. Fewer daily decisions mean more energy to execute.

Separate “modes” of work

• Build mode: 1–2 hour blocks for coding only, no email or social.
• Support/communication mode: fixed times to reply to users and messages.
• Planning mode: once a week, review backlog, metrics and next steps.

It doesn’t have to be rigid; what matters is not mixing everything all the time and ending up with nothing done.

Lightweight tools

• Task list: Notion, Linear, Todoist or even a markdown file in the repo. What matters is having a single place for “what to do”.
• Changelog: writing down what you did (features, bugs, improvements) helps you see progress and communicate updates later.
• Limits: setting a “cap” on hours per day or per week avoids burnout and forces prioritization.

Accept that not everything ships the same day

As a solo dev, you won’t do it all. Focus on what impacts the user most and on your health; the rest can wait or be cut. Sustainable productivity is worth more than sprints that don’t last.