Earlier quoted context omitted.
I already understand how to use them as a professional engineer myself, so I don't see the benefit especially for the amount of money a salary and benefits cost.
Then maybe you don't need them. Only you can answer that for yourself. That's kind of the point of my post. It seems like you're looking for an argument here, and I don't want to argue. I have no idea whether or not you need a team. Maybe you'd be better off spending money on tokens. I don't know.
Pros and cons of solo development
71–80 of 84 posts
Re: Pros and cons of solo development
#72Re: Pros and cons of solo development
#73Earlier quoted context omitted.
"prompting" is a skill, you pay for that.
Is it worth paying 200k a year for that, especially if I'm already good enough at prompting? That amount gets me a lot of Claude Code licenses instead.
Re: Pros and cons of solo development
#74The sharpest con for me is blind spots: solo you're the author, the reviewer and the QA, and all three share the same wrong assumptions. Same goes for weaknesses: on a team someone covers what you're bad at, solo nobody does. LLMs patch this surprisingly well on the technical side - it's a reviewer that didn't write the code, but much less on marketing, positioning, all the stuff outside the editor.
Re: Pros and cons of solo development
#75The rule to remember about solo development: Alone I can go faster, together we can go further! Everything else boils down to this.
I'm finding that yes, it takes longer on my own, I can have AI do much of the stuff for me that I don't want to do.
Re: Pros and cons of solo development
#76Earlier quoted context omitted.
Is it worth paying 200k a year for that, especially if I'm already good enough at prompting? That amount gets me a lot of Claude Code licenses instead.
it may not worth to pay you 200k if someone can also do that prompting..
Re: Pros and cons of solo development
#77Any tips if you have been a solo dev for a very long term (20+ years) for getting hired as part of a team?
Honestly, just applying to positions you're interested in and trying to get interviews. Worst case, you can treat the job interview as practice / learning, best case you pass the interview and get a job offer. Actually getting job interviews can be difficult. It helps to find the email associated with the person hiring, that way you can email them directly to make sure your application actually gets seen.
Re: Pros and cons of solo development
#78Earlier quoted context omitted.
In the time it takes me to make a single-node webservice with a CLI POC client I can now have a fully scalable SAAS with clients for iOS, Android, mac, linux, windows and web-based, user documentation in several languages and a suite of unit tests. Surely that's both faster and further? IMO AI agents are like a team of remote consultants that only talk shop and have no sense of humor.
> I can now have a fully scalable SAAS with clients for iOS, Android, mac, linux, windows and web-based, user documentation in several languages and a suite of unit tests. Which you won’t be brave enough to put on the internet.
Re: Pros and cons of solo development
#79Earlier quoted context omitted.
it may not worth to pay you 200k if someone can also do that prompting..
Indeed, that's why I'm a solo founder.
Re: Pros and cons of solo development
#80The sharpest con for me is blind spots: solo you're the author, the reviewer and the QA, and all three share the same wrong assumptions. Same goes for weaknesses: on a team someone covers what you're bad at, solo nobody does. LLMs patch this surprisingly well on the technical side - it's a reviewer that didn't write the code, but much less on marketing, positioning, all the stuff outside the editor.
this issue resonates for me very much, as a one person startup experimenter in 2026 like a whole bunch of other people. I have a day job with lots of human interaction, but I've been trying to find the edges of what's possible as a single person on my fun side project, and I still haven't found them. I built a product in 3 months, and then wondered if I could commercialise it in another three, which I've now done. Th…