I'm Ashish.
Full stack developer building SaaS and sharing what I learn.
Things you'll see here:
• React tips
• SaaS lessons
• AI tools for developers
• Building in public
Follow along if you're building online.
We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity.
This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.
@0xBebis_ Nobody talks about the cost of vibe coding.
Claude, cursor, vercel, supabase.
You’re paying $200/month in tools
to build a product making $0.
@hamzaalabou man, same here. those edge cases will sneak up on you, right? i usually just try to build a style guide for consistency. helps a bit, but not foolproof. what tools are you using?
@SimonHoiberg facts. it’s like we’re building a house with a door from one store, windows from another, and a roof from somewhere else. at some point, you're just asking for leaks.
I used to give “accurate” estimates.
And still missed them.
If something felt like 3 days, I said 3.
Clean. Confident. Wrong.
Because those 3 days were never just coding.
It was:
Unclear edge cases
Random bugs
Interruptions
Context switching
“Quick” discussions that weren’t quick
And suddenly 3 quietly became 5.
No one questioned my skill.
But predictability? Gone.
So I changed one small thing.
Now if it feels like 3 days, I say 3–4.
Not to pad.
To account for reality.
That shift did more than fix timelines.
I stopped rushing.
And that created something unexpected…
Thinking space.
Instead of closing the ticket ASAP, I started noticing things:
A component doing unnecessary re-renders
A slow interaction that felt slightly off
A messy abstraction I had ignored earlier
Small things.
Not in the requirement.
But very visible once fixed.
Over time, those “unplanned improvements” started stacking.
Not because I worked extra hours.
But because I finally had room to think while building.
The interesting part is this:
That extra 10–20% isn’t buffer.
It’s where better engineering actually happens.
But I still struggle with one thing…
When should I quietly improve something…
And when should I call it out and make it visible?
How do you approach this in your team?
#Frontend #React #DeveloperExperience #WebDev #LearningInPublic
Hi @shadcn,
I'm currently using shadcn/ui (with Radix UI primitives) in a production SaaS dashboard. I'm considering switching to Base UI with shadcn/ui, but I'm struggling to find clear reasons to make the switch.
Could you share your thoughts on this?
@thesayannayak it's all about the user data and patterns, right? like when everyone suddenly slows down, even if you can't see them. wild how that works.
@techdroider for real, that keynote was a whole vibe. felt like they were flexing on everyone. gotta admit, some of those features had me thinking, 'do I really need this?' lol
If you start an app now, please don't use:
1. Supabase = you will regret it.
→ use Convex, Neon, Better-Auth instead
2. Clerk = this is the worst choice ever
→ use Better-Auth instead
3. Supabase Storage or AWS S3
→ use Cloudflare R2, this is the cheapest you can have
4. Namecheap: laggy, buggy, boring
→ use Porkbun or Cloudflare
5. MongoDB = just don't