Different context makes same advice useless

The incentive flipped. Building is slow, teaching is fast. So people optimize for audience before outcomes and call it expertise.

If it worked reliably they would scale it not sell it

remote teams ship better than hybrid.

not bc remote is magic it forces you to write things down.

written decisions > verbal ones written specs > whiteboard scribbles

the writing isn't overhead. the writing IS the thinking.

hybrid = interruptions + isolation + zero docs.

#buildinpublic

the startup advice industry is just MLM for people with MacBooks. successful founders selling playbooks reverse-engineered from survivorship bias to aspiring founders who will never use them.

#buildinpublic

"product-market fit" is just a fancy way of saying "people use my thing." the fact that an entire industry exists around helping founders "find" it is the greatest consulting scam of the decade.

#buildinpublic

Agile is just waterfall with better marketing and more meetings about how agile you are.

#marketing #productmanagement #buildinpublic

i think control works best when it's surgical stream the output so it feels alive, let users highlight and edit a single sentence instead of restarting everything, and add undo (obvious, yet almost nobody does it). Find the 2-3 moments users feel most helpless and fix those. The rest is noise.

3 AI UX anti-patterns killing your product:

Pulsing "thinking" dot for 15 seconds → feels broken
Wall of text for a simple question → feels overwhelming
No way to edit AI output inline → feels final

The fix isn't smarter AI.
It's making the human feel in control.

#buildinpublic

most meetings exist because the person who called them wasn't confident enough to make the decision alone and needed 6 other people to share the blame.

#buildinpublic

it was a sarcasm

if you're a solo founder choosing your stack:

pick tools that let you forget they exist.

the best infrastructure is invisible.

what payment + backend combo are you using? curious 👇

the real benefit of both:

I spend zero time on infrastructure.

no database migrations gone wrong at midnight.
no payment webhook debugging.
no auth edge cases breaking my login flow.

I just build the product. that's it.

What surprised me about Dodo:

the checkout flow conversion rate was higher than I expected.

when the payment experience feels native and fast, people don't drop off.

no redirect to a third-party page. no friction. just pay.

Dodo Payments: the pitch

→ global payment processing (not just US/EU)
→ checkout sessions, subscriptions, license keys
→ simple API — I integrated it in an afternoon
→ handles tax compliance so I don't have to think about it

for a solo founder selling globally? this was the move.

What surprised me about Supabase:

the edge functions are legitimately fast. I was skeptical — "serverless is slow" etc.

but for my use case (AI processing voice entries), the cold start was negligible.

and writing them in TypeScript/Deno felt natural coming from a Node background.

Supabase: the pitch

→ postgres database (not some proprietary thing)
→ auth that just works
→ edge functions (serverless, globally distributed)
→ real-time subscriptions
→ storage

one dashboard. one bill. one less thing to worry about at 2am.

I chose @Supabase for my backend and @dodopayments for billing.

here's why — and what surprised me about both.

#buildinpublic

sureee

Sunday builders thread:

drop your project with:
→ what it does (1 sentence)
→ biggest challenge right now
→ one thing you're proud of

I'll RT the ones that catch my eye

#buildinpublic

Raising venture capital to validate your idea is like buying a treadmill to find out if you like running. you already know the answer, you just wanted permission to spend money.

#buildinpublic

SaaS is dead

We replaced all our subs with "custom AI software".
Monthly spend dropped from $750 in SaaS to just $4570 in LLM tokens.

Big win

As a bonus, the team now spends half their time fixing vibe-coded bugs instead of using working tools

But at least we own the stack

hot take: the best developers I know don't have strong opinions about frameworks.

they have strong opinions about problems

the "React vs Vue vs Svelte" debate is just developers arguing about hammers instead of building houses

pick one ship something nobody cares what you used

#buildinpublic

Even though I’m Indian, I can say that there are many more Indians who speak out and point out what is wrong.

what are you building right now?

drop a one-liner about your project.

I'll reply to every single one.

#buildinpublic

that's what nobody tells you about building solo.

it's not a flex. it's a trade-off.

but if you can push through the ugly middle? the other side is worth it.

what's YOUR hardest lesson building solo? 👇

Lesson 5: you will want to quit at month 3.

the excitement of the idea wore off. the first users are lukewarm. growth is flat.

this is where 90% of solo projects die.

the ones that survive aren't better. they're just more stubborn.

Lesson 4: loneliness is a real problem.

no co-founder to bounce ideas off. no team standup. no one to celebrate small wins with.

building in public on twitter is how I replaced that. it's not the same, but it helps.

Lesson 3: marketing is harder than building.

I can ship a feature in a weekend.

getting 100 people to care about it takes a month.

the code is the easy part. distribution is the actual product.

Lesson 2: your biggest competitor isn't another product.

it's the user's default behavior.

they've been doing things the old way for years. your app needs to be 10x better at ONE thing, not 2x better at everything.