Founding a company, or just working on any project with a very small team (Less than 5 people) has all of the same issues the author wrote about here. At least they did for me. I resonated a lot with this. ---

Separately, I hope the author of this project is able recognize how this project might be able to grow sustainably. Its a hard thing to know that you won't be able to work on something forever, and either building a community who wants to maintain a core project or having some company pay to maintain it could be a good idea. Linus isn't going to be around forever, but I expect that linux will outlive him by a good margin.

maybe a little bit of telemetry that is meant to inform the developer is OK

i assume most people are just against the ad-driven telemetry

Any tips if you have been a solo dev for a very long term (20+ years) for getting hired as part of a team?

I've spent most of the last two or so years working solo (engineering wise) professionally. I'd say the biggest con is that it's lonely. I've gone weeks without talking to people at work. I think that would drive most people crazy :).

I'd say responsibility is the same for me as I've only worked at small companies as a generalist. But yeah I suspect if you come from big tech land, being the everything person might be super tough to get used to.

Lessons from my failure:

- do everything you can to keep burnout at bay

- you do, in fact, need a holiday

- hyperfocus is not your friend, ever; if you feel you can’t put it down, you must put it down

- never delete emails; the one thing you can guarantee is that you will need an email you deleted

- if you look back at your notes and they are not instantly obvious, rewrite them while you still remember what you meant, because one day you won’t

- you might be selling your abilities but you should never rely on them yourself; you do need systems

- you can fall out of love with the thing you are best at

- listen to your friends when they sell your talents; if they say you can do a thing, who are you to argue?

- three days of fully billable work per week is already too risky to gamble on, so:

- you are not charging enough

- YOU ARE NOT CHARGING ENOUGH

- FFS do you even listen? You’re not charging enough

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

A version of this I've been enjoying is mostly solo dev but with a biz-guy partner. I mostly just build software but have a partner who will go find out how people are using it, what they want, handle inbound, and be there to chat about ideas even if we're not getting into the technical weeds.

Part of the cons is offset, if the single maintainer dissapears, nothing a fork can't fix :)

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!

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

The rule to remember about solo development: Alone I can go faster, together we can go further!

Everything else boils down to this.

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

[delayed]