E

Efe

Full-Stack Developer · Open Source

Back
Jul 1, 2026·2 min

Going all in on Coadite

I just finished my computer science degree. Here is why I am spending the next stretch building Coadite full-time instead of taking the safe job.

CoaditeBuildingNotes

Going all in on Coadite

I handed in my thesis, walked out of the last exam, and instead of updating my CV I opened the Coadite repo. That was the whole plan, and it still feels a little reckless typing it out.

Coadite started as a side thing. A place to sell the small tools I kept building anyway, plus the odd client project when someone needed something custom. Over the last year it quietly turned into the thing I think about most, so I decided to stop treating it like a hobby.

The part I did not expect was how much of the work is not code. Pricing, delivery, licensing, refunds, the boring email that tells someone their key got activated on a new device. A product is the whole loop, not the demo. Getting that loop to feel trustworthy took longer than any single feature.

I also learned to ship smaller. My first instinct was always to build the general version of everything. The version that actually helps someone is usually narrower, and a little embarrassing at launch. I am still making peace with that.

There is no grand lesson here. I like building things people can use, I have some runway to try, and university is finally out of the way. If you want to see what comes out of it, the store and the projects are the best place to look.


Let's Connect

What are your thoughts on this? I'd love to hear about your experiences.