23 • Dev

Joined January 2026
C retweeted
So you just finished building your web app. Here's how you get people to actually see it. (Thread)
2
1
3
331
C retweeted
Rate limiting when developing with LLMs isn't optional. Redis handles this at scale. But you don't need it yet. Instead, add a rate limit table to Supabase. Track user ID, timestamp, request count. Fixed window is simplest, query on each request, increment if under the limit, block if over. There is one issue with this - concurrent requests. If two requests come in simultaneously for the same user, both can read the count before either increments it, and both pass through. At low traffic this rarely matters, but it's a real tradeoff worth knowing. A fix to this is to increment atomically. Instead of read → check → increment as separate steps, you do it in a single database operation. In Postgres you can use UPDATE ... RETURNING. So when do you actually migrate to Redis? When your atomic Postgres updates become the bottleneck under concurrent load. Or when you're seeing latency on the rate limit check itself. Or when you need distributed rate limiting across multiple servers. Until then, the Supabase table is enough. Build simple. Migrate when the problem is real, not imagined.
1
2
128
C retweeted
New feature: Pinned Posts. - Save drafts - Edit them over time - Shows the prompt used for each generation - Preview how they'll look on X - Mark them as posted - Favourite posts to feed back into the AI. Don't lose tweet ideas you could use later.
1
2
144
C retweeted
What’s the best way to validate an idea before building? - Landing page + waitlist - Build an MVP in a weekend - Post about the problem obsessively - Pre-sell before writing a line of code Something else?
7
1
10
264
C retweeted
What’s a guaranteed way to get your first user? - Cold dm / email - Posting on X - Ads - SEO Or something else entirely?
26
1
25
919
C retweeted
My stats for March are in. My goal was to reach 100 followers & 350K impressions. Started March with: → 57 followers → 188K impressions → 2.5% engagement Ended March with: → 124 followers (+67 ) → 445K impressions (+257K ) → 2.8% engagement The grind is working.
1
2
8
204
C retweeted
Stop overthinking your stack. Here’s the best tech for fast-to-ship MVPs: Frontend → Next.js ( hybrid rendering + API routes ) → Typescript everywhere ( static typing ) → Tailwind ( styling ) Database + Backend → Supabase ( PostgreSQL + Auth ) → Supabase Storage ( image + video ) Deployment → Vercel ( great for Next.js ) Integrations → Stripe ( payment ) → Anthropic/OpenAI ( AI integration ) → Resend ( email handling ) → Posthog ( Analytics ) This stack isn’t about being perfect. It’s about removing decisions and reducing friction. Build fast. Focus on great features, not the stack.
2
3
196
C retweeted
The best way to humanize AI outputs? Give the AI a better identity to work from. Here's what I found actually matters for making AI sound like you. (thread)
1
1
2
190
C retweeted
Personalisation separates usable AI outputs from slop. I'm focusing on this with The Daily Ship. - Quick fire questions - Text box for personal do's and don'ts - Pasted voice samples (real tweets the AI studies) This gets compiled into a voice profile that feeds into every prompt. Here's how it's looking so far👇
1
2
105
C retweeted
3 months of posting on X. I’ve found the hardest part is posting valuable content every single day. So I started working on something to fix that for myself: An app that turns your git commits, trending topics and your personalised profile into daily content ideas. Built specifically for build-in-public devs. Anyone else struggling with consistency? How are you handling it?
1
1
1
173
C retweeted
“Just post consistently” is terrible advice if you don’t know what to post. I’m building The Daily Ship. It turns your profile, commits, and trends into actual content ideas. Here’s the current landing page.
1
1
146
C retweeted
Here's a look at my progress on The Daily Ship so far. Personalisation page that auto compiles a voice summary based on your inputs. Single post generation that creates ideas based on your profile and customization. Also working on a quick idea generator. 5 ideas you can expand into full tweets with one tap. I'll have a basic MVP out soon for anyone that wants to give it a try.
1
123
C retweeted
The 6 steps I use with AI to go from idea to actual plan. (Thread)
3
1
3
287
C retweeted
AI apps are one of the most interesting things to build right now. I've built: • a support ticket summariser/translator • a coding challenge generator • an X reply assistant extension Here are 4 prompt engineering lessons I've learned. (Thread)
3
1
4
230
C retweeted
As a dev, I ship code almost every day. But posting about it everyday is tough. The blank compose box stares back. The energy to turn a commit or idea into something worth sharing isn't there. So most days my work stays private. No growth, no feedback, no connections with other devs building the same stuff. I've tried tools that automate posts, but the output sounds generic and not like me. What I realized is I don't need automated posts. I need automated ideas. A tool that works with what I'm already doing. So I decided to build it myself. The Daily Ship A tool for devs who ship daily but struggle to share daily. It generates ideas for single posts, threads, git commits, and trending topics. But the real focus is personalisation. Every idea can be customized end to end to sound like you. No generic output. Your voice. Your work. Your posts. If this sounds like a tool that could help you too. The waitlist is open👇
1
1
1
163
C retweeted
I built a newsletter into my portfolio site. Every week I document what I'm building, what I learned, and cool videos I found. Runs on markdown files. Supabase for subs, Resend for emails. No CMS, no Substack. First post is already live. New ones every week. Link👇
1
1
1
167
C retweeted
I used to skip straight to building. No validation. No plan. Just vibes and a code editor. The result? Products nobody cared about. Here’s the step I was missing: (Thread)
1
1
1
139
C retweeted
I’ve seen a lot of established creators say:“Your first product won’t be the one.” Most of the time, they’re probably right. But as a dev starting this journey, that line can feel pretty discouraging. My Take: Treat every product you build as the one that can change everything for you. The real trick isn’t accepting what you create might fail. It’s refusing to let that stop you. Relentless discipline + unshakable belief keeps you shipping everyday. You got this. What’s the project you’re treating as “the one” right now?
2
1
3
174
C retweeted
Program-Pit is launching this week. What started as a FastAPI & Clerk tutorial. Is now a fully gamified coding practice platform. And completely free to use, if you use up your requests just add your own API key. Do your daily challenges, level up, unlock badges, get to #1🏆
1
1
221
C retweeted
My Plan for March Being honest about where I'm at and what I'm building towards🧵
1
1
1
1
590