Skip to main content

Posts

Showing posts with the label Startup Journey
Debugging Hell: One Bug That Nearly Crashed Our Launch ๐Ÿ’ฃ Debugging Hell: One Bug That Nearly Crashed Our Launch Published: 20/06/2025 – Behind the Scenes Series #3 ๐Ÿšจ The Crash That Didn’t Make TechCrunch (But Almost Made Us Quit) Three days before launch, everything was on track… until we realized that new users weren’t being saved to the database . The app was showing a “Signup successful” message — but behind the scenes, nothing was saved. Users tried logging in again and were met with… silence. It was like they never existed. ๐Ÿงต How It Unfolded (A Real Timeline) T–72 hours: Suspicion One teammate said, “Weird, I just signed up but I’m not showing in the users table.” We checked. They were right. The auth record existed, but no user profile row. T–60 hours: Panic Our signup logic used a chained `.then()` call after a Supabase signup: signup(email, password).then(() => { createUserProfile(email); }); But `...

The behind-the-scenes story of how we chose our tech stack, what went wrong, and why we changed course

The Tech Stack We Chose (And Why We Switched Midway) The Tech Stack We Chose (And Why We Switched Midway) By Rexman Published: 13/06/2025 – Behind the Scenes Series #2 ๐Ÿง  The Master Plan Choosing a tech stack was easy. Or so we thought. We had a Notion page comparing Postgres vs Mongo, Firebase vs Supabase, React vs Vue vs SvelteKit. We were acting like we were choosing our life partner — when really, we just needed a stack that wouldn’t break in 3 weeks. We picked: Frontend: React Native with Expo Backend: Supabase (Postgres + Auth) Storage: Supabase Storage AI integration: Claude (Anthropic) Deployment: Vercel ๐Ÿ’ฅ Reality Bites Week 1 was smooth. By Week 2, cracks appeared. Supabase’s Postgres was fine… until our expensive queries choked it. React Native was okay, but we hit prop-passing hell fast. Claude integration was awesome… until we realized we needed more dynamic prompt chaining a...

How we built our MVP in just 30 days: lessons, tools, and real talk from a startup founder

How We Built Our MVP in 30 Days How We Built Our MVP in 30 Days By Rex, Founder at Pinegrass Published: 06/06/2025 – Behind the Scenes Series #1 ๐Ÿš€ “Let’s ship in 30 days… or shut up about it.” That was the line I scribbled on a sticky note on Day 0. Not because I’m a productivity junkie — but because for 6 months, the idea had been sitting idle in our Notion. And Notion isn’t where startups are born — execution is . This is a raw look at how we built and shipped our MVP in exactly 30 days — no excuses, no fluff, no overplanning. ๐Ÿงญ Why We Set a 30-Day Deadline (And Meant It) Week 1: The Ruthless Cut We started by saying no — to features, personas, and overthinking. From 24 wishlist features, we cut 18. From 3 user personas, we chose 1. Our only goal was to solve one job well . Signup → Get value Log back in Share it with someone else No dashboards. No settings. No custom flows. Just the job. Week 2: Setup ...