Thomas

My new workflow for shipping apps fast: 1. Design in Google @stitchbygoogle (vibe design first, code later) 2. Export the DESIGN.md blueprint 3. Feed it to Claude Code and let it build Why this works: → Stitch lets you visualize every screen before writing a single line of code → The DESIGN.md file gives Claude Code the full context : colors, typography, spacing, components → No more "that's not what I meant" back-and-forth Stop vibe coding blind. Vibe design first. Then build.

Most tech companies break out product management and product marketing into two separate roles: Product management defines the product and gets it built. Product marketing wires the messaging- the facts you want to communicate to customers- and gets the product sold. But from my experience that's a grievous mistake. Those are, and should aways be, one job. There should be no separation between what the product will be and how it will be explained- the story has to be utterly cohesive from the beginning. Your messaging is your product. The story you're telling shapes the thing you're making. I learned story telling from Steve Jobs. I learned product management from Greg Joswiak. Joz, a fellow Wolverine, Michigander, and overall great person, has been at Apple since he left Ann Arbor in 1986 and has run product marketing for decades. And his superpower- the superpower of every truly great product manager- is empathy. He doesn't just understand the customer. He becomes the customer. So when Joz stepped into the world with his next-gen iPod to test it out, he fiddled with it like a beginner. He set aside all the tech specs- except one: battery life. The numbers were empty without customers, the facts meaningless without context. And, that's why product management has to own the messaging. The spec shows the features, the details of how a product will work, but the messaging predicts people's concerns and finds way to mitigate them. - #BUILD Chapter 5.5 The Point of PMs

Building a React Native mobile app? Stop overthinking your setup. Here's the only stack you need 👇 ⚙️ Core ┗ Expo + TypeScript + Expo Router 🗄️ Data & State ┣ 💽 Expo SQLite + Drizzle ┣ ⚡ MMKV (30x faster than AsyncStorage) ┣ 🐻 Zustand ┗ 🔄 TanStack Query 📦 Must-Haves ┣ 📜 FlashList ┣ 📝 React Hook Form + Zod ┣ 🎞️ Reanimated ┗ 👆 Gesture Handler 🎨 Styling (pick your level) ┣ 1️⃣ StyleSheet ┣ 2️⃣ Uni Styles ┣ 3️⃣ Uniwind ┗ 4️⃣ Expo UI ☁️ Backend ┣ 🟢 Supabase ┣ ⚡ InstantDB ┗ 🛣️ Expo API Routes 🛠️ Services ┣ 🚀 EAS (build + deploy) ┣ 🔐 Clerk (auth) ┣ 🐛 Sentry (monitoring) ┣ 💰 RevenueCat (payments) ┣ 📊 PostHog (analytics) ┗ 🤖 CodeRabbit (AI code reviews)

@levelsio @iFood I know a little trick to get your CPF by email within 2 days, you just need to send your passport and the Receita Federal form - DM if you want more info

P.S. we fixed @iFood, Brazil's delivery app, which on sign up also required both a CPF and BR phone before Now it doesn't! You can just tweet things and it's fixed

The main gotcha: speed ≠ skip the review. Both commands move fast. That makes the review step more important, not less. Run your tests. Check the diffs. These tools handle the mechanical work : engineering judgment is still on you!

The real power move is using them together: 1. /batch to scan your codebase and flag complex files 2. /simplify on those files to get cleaner versions 3. /batch again to propagate the improved patterns at scale Systematic codebase improvement without the slog.

Two @Claude code commands every developer should know: /simplify and /batch One cleans up overengineered code. The other runs refactors across your entire codebase in parallel. Here's how they work

People who moved abroad alone in their 20s, handled all docs, bank account, visa, tax, jobs, accomadation, and culture difference These people fear nothing anymore

Claude code down. Coffee time. {"type":"error","error":{"type":"overloaded_error","message":"Overloaded"},"request_id":"req_*******************"}

Solo dev math: (1,400 lines of auth code x future maintenance hours) vs a managed service that handles it all. Lesson : If auth isn't your product, don't build auth.

The hardest part wasn't the migration. It was pressing delete on code that worked. But every line of custom auth is a line you maintain forever : token refresh bugs, deep link edge cases, secure storage encryption quirks.

Today I deleted 15 files and ~1,400 lines of custom auth code from my React native Expo app. My entire auth screen is now 5 lines. Here's what happened.

🔴 Keep your API keys and other CI/CD credentials away from Agents! In Claude Code, the bare minimum is to type /permissions in the console and set up the following : Add deny rule Read(./.env) Add deny rule Read(./.env.*) Add deny rule Read(./secrets/**) Add deny rule Bash(printenv) Add deny rule Bash(export)