Live data from Hacker News

Pros and cons of solo development

johnjeffers.com

21–30 of 84 posts

Re: Pros and cons of solo development

#21

The rule to remember about solo development: Alone I can go faster, together we can go further! Everything else boils down to this.

Perhaps. I think AI changes the equation here. Honestly, AI changes what "solo developer" even means.

> Perhaps. I think AI changes the equation here. Honestly, AI changes what "solo developer" even means.

I disagree; it's even more obvious with AI that, with AI, a solo dev can go even faster, but still, with AI, you need a team to go further.

Re: Pros and cons of solo development

#22
post #4

Any 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

#23
All the pros listed really resonate with me. I don't develop software as a career anymore, but do it as a hobby. I wouldn't take on a second developer partner for any of my projects. I guess it would feel like working on a beautiful, personal painting and recruiting a second artist to paint half of it. Maybe that works for others, but it's just not how I see myself creating a work. I'd accept small patches to fix bugs, but for the actual overall thrust of my projects, I'll probably always be lone-wolf.

Re: Pros and cons of solo development

#24

The rule to remember about solo development: Alone I can go faster, together we can go further! Everything else boils down to this.

Perhaps. I think AI changes the equation here. Honestly, AI changes what "solo developer" even means.

I agree. It sure does change what it means.

Re: Pros and cons of solo development

#25
The 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

#26
post #15

> But... I don't truly know what my users want. There is no telemetry of any kind in Luxury Yacht. I like being able to say that, but it means I have no idea how many people are using it, or how they're using it. I don't know what features are the most important to other people. So add telemetry and a request tracker like https://www.productboard.com/ . This is not a solo vs team thing.

Most projects don't need telemetry. They need better logs.

On the backend... Why wouldn't you log every request that hits your server, and why wouldn't you already know what those requests mean? Why would you let your frontend make direct requests to any other server when you can just proxy it yourself and maintain control?

On the frontend... What's so hard about wrapping all your event listeners and periodically sending those logs back to your server?

That's not even scratching the surface, but even something this simple and easy to implement is already miles ahead of most free-tier telemetry offerings, and you retain full control.

Re: Pros and cons of solo development

#27
post #4

Any 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.

[deleted]

Re: Pros and cons of solo development

#28
post #4

Any 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.

[flagged]

Re: Pros and cons of solo development

#29

All the pros listed really resonate with me. I don't develop software as a career anymore, but do it as a hobby. I wouldn't take on a second developer partner for any of my projects. I guess it would feel like working on a beautiful, personal painting and recruiting a second artist to paint half of it. Maybe that works for others, but it's just not how I see myself creating a work. I'd accept small patches to fix bug…

I feel the same way. I have hired a number of people over the years for various jobs who I’ve enjoyed working with. But it was out of a desire to capitalize on various situations, move faster. When it comes down to it, I am happier moving slower and alone, and the end result is always better.

Re: Pros and cons of solo development

#30

The rule to remember about solo development: Alone I can go faster, together we can go further! Everything else boils down to this.

Team just eats your runway, and adds shit ton of overhead.

Plus it is much healthier to have a social life outside of work. Talk about something else, no algos!

Post reply on HN