Day 3 of trying to make any money on the internet:
Hit 1000 followers 🥳
Shipped absolutely nothing
Progress is all over the place
Still figuring it out, but we're getting there 🫡
x.com/CodeWizard/status/201440...
3 months into building in public and I still haven't made my first dollar 😆
But here's what I have done:
- shipped an invoicing app that actually works
- hit 1000 followers somehow
- learned more than my last 3 years at the 9-5
Not quitting my day job yet, but I'm closer than I was yesterday 🫡
Day 2 of trying to make any money on the internet:
Nearly hit 1000 followers 🥳
Finally fixed the landing page (it was haunting me)
More locale features dropping soon
Marketing? Yeah... need to do more of that 😆
Baby steps, but we're moving 🫡
https://x.com/CodeWizard/status/2014052048220668069
Shoutout to everyone still building with $0 MRR - either we're super brave or just a little too stubborn for our own good 😉🫡
Day 1 of building my app to make any money on the internet 🫡
Cannot thank you all enough for such an incredible response on the first video. You guys are truly incredible 😭
New features inbound, new update soon?
https://x.com/CodeWizard/status/2013691061772730530
The technical skills you have? Not the problem.
Sharing what you're building publicly? That's the unlock 🫡
Thank you all so much for the incredible support on my first video.
You guys are awesome 🫶
https://x.com/CodeWizard/status/2013691061772730530
Day 0 of documenting my invoicing app build and I'm already wondering what I've gotten myself into 🫡
Please be gentle when I eventually break something that was totally fine five minutes ago.
Why am I like this? 😆
Post image
Post image
Confession: I'm about to do that thing where you rip out working auth because the new shiny docs look too good 😆
Clerk's been solid but slow on features.
Anyone actually made this jump?
Or am I about to learn why 'if it ain't broke' exists? 🫡
Building in public isn't a marketing tactic 😆
It's how you go from "random person launching thing" to "the obvious choice"
People don't follow perfect launch announcements
They follow real builders sharing the messy journey
Authentic connection > polished facade every time
Developers hate marketing because it feels like creative work.
But what if you treated distribution like debugging?
- Content = repeatable system
- Traffic = automated pipeline
- Growth = solved technical problem
Build a factory, not art 🫡
Why do breakthroughs always show up at 2am when you should be asleep? 🤔
Spend all day stuck on a bug, then suddenly fix it right before bed.
Now I'm way too hyped to sleep and way too tired to code more 😅
Building in public isn’t just marketing, it’s basically a cheat code for indie hackers.
If you’re still hiding in stealth mode, you’re missing out on free accountability, instant feedback, and a network that actually wants you to win.
Time to hit that tweet button. 😉
5. What actually works
- Daily progress updates (even tiny wins)
- Behind-the-scenes fails
- Revenue or user number breakdowns
- Asking for help in public
The more human you sound, the faster you grow. 🫡
4. The compound growth pattern
Week 1: 5 likes, comments from your mum
Week 4: Other builders notice
Week 8: Customers start following
Week 12: Random opportunities in your DMs
Showing up beats being perfect.
Every single time.
3. Network effects are wild
Share your problems out loud and solutions just show up.
One builder tweeted about payment headaches.
Got recommendations with Stripe alternatives, 3 partnership DMs, and even found a co-founder.
2. The accountability hack
When you say 'Shipping v2 this week' and 500+ people see it, suddenly you actually have to do it.
No more 'I’ll finish it next weekend' lies.
Public pressure is real and honestly, kind of helpful.
1. The transparency advantage
Builders who share the messy, real stuff get 3x more engagement than those polished launch posts.
People want to see the chaos, not just the shiny end result.
Sharing your struggles humanises you.
Who knew? 😅
Spent way too much time analysing how indie hackers actually grow on X.
Plot twist: the ones building in public absolutely destroy the stealth mode crowd.
Here's what I've learned about growing from zero
👇
Hate marketing? Just build cool stuff people actually search for 😉
Free tools that rank > forced LinkedIn posts any day 🫡
Here's something you might like. I'll update it at some point.
https://github.com/v0sudo/brutal-shadcn
Hate marketing? Just build cool stuff people actually search for 😉
Free tools that rank > forced LinkedIn posts any day 🫡
5. The shipping advantage
Workflow fixes ship fast.
No fancy UI, no endless research, no feature flags.
Just remove friction and deploy.
Tiny workflow fixes aren't glamorous.
But users notice.
Retention goes up.
Word spreads.
Sometimes the smallest changes actually matter most.
4. How I find these fixes
Watch people use your app (awkward but so worth it).
Look for:
- Repeated clicks
- Long pauses
- Frustrated sighs
- 'Why doesn't this just...'
Those moments are your next sprint.
3. The compound effect
Tiny fixes add up fast.
One user saves 2 minutes a day.
With 100 users, that's 200 minutes saved.
That's over 3 hours of human time back in the world.
Honestly, feels better than any vanity metric.
2. Real examples from my apps
Instead of building:
- Advanced dashboard → Fixed the 'export takes forever' button
- AI recommendations → Made search actually find things
- Social features → Auto-save drafts every 10 seconds
Guess which ones people loved? 😉
1. The mindset shift
Features sound impressive in meetings.
Workflow fixes actually get used.
I stopped asking 'what's cool?' and started asking 'what's annoying?'
Turns out users care way more about saving 30 seconds than seeing fancy animations.
Stop building 'features'.
Start building tiny workflow fixes.
The difference changed how I ship everything.
Here's why
🧵
Post image
While everyone's hacking their morning routine, I've turned lunch into my secret weapon 😆
Most slept-on hour for remote folks 🫡
20 min to eat, 40 min to think without Slack destroying my focus.
Best debugging happens with a sandwich in hand.
Lunch break > morning grind.
No-code tools be like:
"We make coding easy!"
Call me old but they actually:
- Just hide the complexity
- Make debugging is a guessing game
- Documentation? Good luck lol
Meanwhile actual code would've taken 10 mins
Sometimes the "simple" way is just... harder 😆
Post image
Post image
I'm tired of seeing this.
Border radii aren't that difficult to get right.
Builders, for the love of God, fix your nested corners.
It takes 5 minutes to fix.
Ship like you actually know what you're doing. 🫡
Don't be like me 😬
Set a goal of 600 followers by today. We didn't just hit it, we blew past it.
App #1 status: Still not broken, which is really confusing.
x.com/CodeWizard/status/200741...