i had no idea how to ship.

march 21, 2026 · 2 min read


when you're self-taught, you learn by building.

you watch something break, you google why, you fix it, you move on. that loop is how you get good. it's uncomfortable and slow and then one day you look back and realise you can actually build things.

nobody handed me a syllabus. no degree, no bootcamp. just curiosity, google, and a lot of late nights staring at error messages.

i was proud of that.

and then i launched csskro and heard nothing back, and i realised the loop had a massive blind spot.


the silence after launch didn't hit me right away.

the first day i told myself it was too early. the second day i told myself the same thing. a week in, i started refreshing the analytics less. a few weeks later, the silence had just become the background noise of my day.

nobody was coming.

not because the product was bad. not because the problem wasn't real. students genuinely struggle with the english essay, and the tool i built genuinely helped with that. nobody was coming because nobody knew it existed.

i had spent 3 months learning to build. i had spent zero hours learning to reach people.


when you're self-taught, every resource points you at the craft. tutorials, courses, youtube channels. none of them teach you what happens after you push to production.

distribution is a skill. reaching people is a skill. writing something that makes someone stop scrolling is a skill. understanding where your users actually hang out, what words they use, what would make them click.

and none of it comes automatically just because you learned to code.


so i have started learning the thing i skipped.

same way i learned everything else. googled it, read about it, studied what actually worked for other people. it's slower than building. more uncomfortable. you can't run it and see if it compiles.

the new project i'm working on, i'm doing it differently this time. distribution first, then build. i want to know who i'm reaching before i write a single line of code.

and csskro, i'm not done with it. the tool still works. someday i'll come back to it, armed with everything i didn't know the first time, and i'll make it count. the product deserves that. and honestly, so do the six months i put into it.


if you enjoyed this post, consider sharing it on twitter.

share on twitter →

want to be the first to know when i post?
drop your email below and i'll let you know when the next one goes live.

← back to blog
+k