Pros and Cons of Solo Development – John Jeffers

Pros and Cons of Solo Development

05 Jul, 2026

I created and maintain Luxury Yacht, a desktop app for managing Kubernetes clusters. Think Headlamp, Lens, and k9s. It's that kind of app. Luxury Yacht is a solo project, and it's been quite a challenge to get it to where it is today. I want to talk about some things I've learned over the past six months of doing this.

But First, Why?<br>Why do this, when apps like Headlamp, Lens, and k9s exist? I just never found the app that clicked with me. The closest thing I found to what I wanted was Infra, which I really liked, but it's been abandonware for years. So, I decided to write my own. Along the way it got good enough that I thought other people might also like using it, so I released it.

Maintaining Luxury Yacht is practically a full-time job that I do for free, in my spare time. It eats up a sizeable chunk of my evenings and weekends. I'm not complaining! Nobody's forcing me to do this. I enjoy it. I'm creating something genuinely useful for myself that I get to share with other people. As I write this, I've got well over 350 stars on the GitHub repo, and that feels pretty good.

Pros<br>There's a lot of freedom that comes with being the sole maintainer of an app. This is the big draw for me.

I get the exact app I want, that works exactly the way I want it to. This is extremely satisfying, and you should try it if you haven't yet. AI has opened this door for a lot of people. More on that later.

I can ship a bunch of changes at once. I can create ridiculously huge PRs that I would never willingly inflict on another person.

Being accountable to no one but yourself is liberating. I make all of the product decisions. If I want a feature, I build it. I don't have to cut or delay features to meet a release deadline, or negotiate with a product team about taking the app in directions I don't agree with.

I release on my own schedule. Sometimes I might release a few times in one day, other times it might be a few weeks between releases, if I'm working on a particularly large or complex task.

I don't do standups, sprints, points, or burndown. All of the ceremony that can get in the way of actually doing the work is gone when you're a one-person shop.

I can choose to license and release my app however I want. In my case, I've decided to give it all away for free. There are a few reasons for that:

I like the philosophy of FOSS, and I like the idea of giving something back to the community that has given me so much.

I make extensive use of LLMs to write Luxury Yacht. It doesn't seem right to charge someone to use code that was trained on other people's hard work. Perhaps this is a naive way to think about this.

I really, really don't want to be in the business of software. I like creating the app. I don't want to run a business. It's important to understand these kinds of things about yourself, so you can enjoy what you do and not burn out. I might be leaving money on the table, but I don't care. I'd rather be happy.

The other category of things in the Pros column are learning opportunities. What you'll learn from your project depends on what you're building, how you build it, and where you're starting from. I'm not going to go into detail about the specific things I've learned from working on Luxury Yacht, because that's unique to me. Suffice it to say that you'll learn a lot, because it will force you to deal with things that you probably don't have to deal with in your day job's niche.

Cons<br>The flip side to all of that freedom is responsibility. You're on the hook for everything. It takes a lot of self-discipline to do this solo. I wouldn't recommend it if you don't have that discipline.

Thanks to AI, writing software is easy, but writing good software is still hard. Even if you let LLMs write most of the code, it's a lot of work to prevent it from becoming slop. Current LLMs cannot hold the complexity of large apps in their context windows, and you have to constantly monitor and direct them to keep them from going off on strange tangents and producing garbage code.

I have no one to bounce ideas off of, aside from friends who use the app. I don't know if my design choices are right. I don't know if my implementation makes sense. I don't know if I'm making rookie mistakes in the code. What I do have is a lot of experience as a platform/infra engineer, and I've been using Kubernetes for almost as long as it's been around. I have a pretty good sense of what I want out of an app like this, and I'm hoping that what I want from this app are the same things other people want.

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.

It can be a massive time sink. As I mentioned earlier, I spend...