I like open source software, but I am terrible at running open source projects. The way I work doesn’t match the open source model.

Here is my problem - sharing code is good, but managing a project forever is not.

Selfishly, my side projects are for me and nobody else.

Adding features other people want destroys my creative vision. I don’t want to build software that fits every user need.

When I open source my code, I feel guilty when other people try to contribute. What happens when I no longer care about the project?

Just because I made something two years ago doesn’t mean I want to keep updating it today. Most times, I make something and move on.

One and done.

A public project with multiple versions, constant updates, etc. doesn’t fit me. My heart isn’t in it.

With Obvious, I decided to shut the project down. It’s an archive now. Eventually it will just be a zip download.

Future projects won’t be open source. I will do a video and writeup instead. If someone wants the code, they can ask for it.

I don’t see a way to do open source without compromising my vision. I don’t want to be married to a project forever.

The way open source is now leaves me feeling guilty about abandoning projects.

When I see code that hasn’t updated in years, I am leery about using it. Why then would I publish code that will never be updated?

I would like an open source model that is like boxed software. You do one release, people can use it, and that’s it.

Maybe you do another release if the project is interesting in a few years. Maybe you never do a second release.

That approach fits me better as a creator. I don’t think it fits the expectations of the open source community.

As it stands today, doing open source software creates guilt. It is not worth it.

Sharing project videos and articles suits me better. I’ll do that instead.

-Brian

P.S. I unpack more ideas in Creative Genius