Live data from Hacker News

Pros and cons of solo development

johnjeffers.com

11–20 of 84 posts

Re: Pros and cons of solo development

#11

For me the Best Pros is "That one random-internet-comment is a good usability improvement, ask LLM to do the small change and commit immediately." Smaller ideas need not be approved , or held back by schedule pressure from bean counters. Just Do It. :). It's the small corrections which end up polishing the product as good as "professional usability studies".

Yeah, the small bits of sand in the gears is something that is hard to sell when you allocating engineering effort. But it adds up over time.

It makes the difference between a tool that is a pleasure to use and one that causes dread.

Re: Pros and cons of solo development

#12
I feel like your con about not making the right design choices isn't a con. Solo development doesn't mean throwing out the principles that help you learn. Prototyping and beta releases exist to validate design choices without needing a team to debate them. If your software has users they become the sounding board. You mentioned only asking your friends about your ideas. The best part about prototypes and betas is that you get to build something, use it, and see if you like it before committing. If the idea doesn't get traction, throw it away!

Re: Pros and cons of solo development

#13
I should probably create my own project at some point, but most of what I do is building mini shopping malls or integrating large machinery equipment. Someday, I'd like to make a project that other people actually use.

As an independent developer, the advantage is that I can do a lot of different things. It's hard to go deep into one area, but I can work across many different kinds of projects—building drones, inspection equipment, testing gear, shopping malls, red-team work for security companies, smart farm control systems, home trading systems, apartment wall pads, POS, WMS, data collection for academic papers, and more. I've worked on quite a variety of projects and stacks. That's the upside. The downside is that it's hard to develop the same depth of expertise as a team-based developer. In reality, most of the work is just reading manuals and implementing things according to them.

Right now I'm working on creating a programming language, but I'm a little worried because everyone seems to be building languages with LLMs these days. Ultimately, a language needs to offer enough value for users to actually want to try it, and I'm not sure I can create something compelling enough to attract interest.

The machinery equipment work I usually do depends on factories expanding nearby, but lately the area I live in has been declining, so there's not much of that work anymore. Someday I'd like to build a project that people remember. But unlike Western developers, I'm far from the mainstream of programming, and my skills aren't that great either, so I'm not sure what to do or what would even be a good direction.

If I joined a company, I'd have to leave my area, but then rent would be hard to afford, and my workflow would be so different from theirs that I'm not sure it would work out. I feel like I've designed my career poorly. And it's not like I'd be able to get hired in this job market anyway

Re: Pros and cons of solo development

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

Re: Pros and cons of solo development

#16
I'm a big believer in the philosophy "Make the thing you want, and chances are it's what others want also". I'm also a big believer in whole-hog vibe-coding. So none of these cons resonate with me. The code is slop, hell yeah it is! And it works GREAT. The users? It's me, and anyone who sees me using it and gets jealous.

Re: Pros and cons of solo development

#17
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.

I don't want to add telemetry. And I think this is where the solo vs team thing matters. I can just say "no telemetry" and I don't need to argue with anyone about it. I make the decision and live with the consequence.

I don't really need to know how many people use the app. It would be cool to know, but not necessary.

If someone wants a feature, or a fix, they can open an issue.

Re: Pros and cons of solo development

#20

I feel like your con about not making the right design choices isn't a con. Solo development doesn't mean throwing out the principles that help you learn. Prototyping and beta releases exist to validate design choices without needing a team to debate them. If your software has users they become the sounding board. You mentioned only asking your friends about your ideas. The best part about prototypes and betas is tha…

Yeah I understand what you're saying here. Some of that is just me dealing with imposter syndrome. I pretty much know what a good app looks like, and I have definitely been through a lot of iterations to get Luxury Yacht to where it is today. Thanks.
Post reply on HN