Been indie 10+ years (aged 23-34) and can definitely say that — once it works out — the autonomy and independence make it an absolute dream lifestyle.
Some pointers and observations I've learned along the way.
1. The hardest part of persisting is the emotional game. Improve your motivation by doing things in a way that even a failure of your primary business goal still leaves you in a better position career/skill-wise than when you started. Also: figure out how to separate your identity from your business, otherwise every tiny failure or criticism will sap your energy.
2. For many — maybe most — products within reach of a solo founder, marketing will take up at least as much time as development. Unlike programming, marketing is shrouded in something not unlike the fog of war in RTS games. It is highly exploratory and experimental in nature. But dealing with this uncertainty carries its own intellectual appeal, one that you can learn to embrace — or even enjoy.
3. Outsource as much as can. If some work can be done for less than your hourly rate as a freelancer, then, overall you're more efficient to code for $$$ then pay someone to handle that part of your business.
4. The technical skills that are most useful to a solo founder are more to do with system design than programming languages and frameworks. You should focus on things like data integrity, uptime, redundancy, error-tracking, rapid response to production issues, integration testing, etc. rather than which React.js state library is better.
5. Get to know other solo-founders. I formed a monthly meetup with about ten other people in a similar boat in my town and these sessions acted both as a support network and as a way to get feedback on my (sometimes harebrained) ideas.
I've a lot more to say on this topic and I go into way more depth in the screencasts I post over at https://www.semicolonandsons.com/
Some pointers and observations I've learned along the way.
1. The hardest part of persisting is the emotional game. Improve your motivation by doing things in a way that even a failure of your primary business goal still leaves you in a better position career/skill-wise than when you started. Also: figure out how to separate your identity from your business, otherwise every tiny failure or criticism will sap your energy.
2. For many — maybe most — products within reach of a solo founder, marketing will take up at least as much time as development. Unlike programming, marketing is shrouded in something not unlike the fog of war in RTS games. It is highly exploratory and experimental in nature. But dealing with this uncertainty carries its own intellectual appeal, one that you can learn to embrace — or even enjoy.
3. Outsource as much as can. If some work can be done for less than your hourly rate as a freelancer, then, overall you're more efficient to code for $$$ then pay someone to handle that part of your business.
4. The technical skills that are most useful to a solo founder are more to do with system design than programming languages and frameworks. You should focus on things like data integrity, uptime, redundancy, error-tracking, rapid response to production issues, integration testing, etc. rather than which React.js state library is better.
5. Get to know other solo-founders. I formed a monthly meetup with about ten other people in a similar boat in my town and these sessions acted both as a support network and as a way to get feedback on my (sometimes harebrained) ideas.
I've a lot more to say on this topic and I go into way more depth in the screencasts I post over at https://www.semicolonandsons.com/