Now that Railway has released buckets, and since I am using drizzle and trpc with supabase, I am seriously considering using Railway's Postgre DB. I would use Betterauth or similar to replace supabase's auth.

Over the past eight to ten weeks, we've been building and testing a structured system for AI-assisted development. Our focus has been straightforward: good architecture, solid security, and code we can maintain long-term. I want to give a shout-out to Zubair here. Technically he's from a competitor agency, but we had a conversation six or seven months ago where we both realised something: AI development, when done right, is genuinely better than traditional low-code work. We've been on parallel tracks since then, and those early discussions really shaped how we've approached this. The key insight we landed on is treating AI as a controlled tool within a clear system, not just letting it run wild. This gives us consistent results, enforced structure, and keeps us in control of the decisions that matter. What's been surprising is how straightforward this actually is in practice. When you nail the basics, clean data models, proper permissions, audit trails, disciplined deployment. AI development stops being scary. It's actually more transparent and secure than the heavily abstracted no-code platforms many of us started with. You can see what's happening, control the boundaries, and own your logic. The main thing I've learned: AI-driven development doesn't mean abandoning good engineering. If anything, it demands it. And when you approach it with that mindset, it actually makes you a better developer. See example from our PM System (Traditional Dev + AI assisted development) of what we have developed in past few months for our internal use.

"But I don't use React." If you built your app with Lovable, Bolt, Replit, or v0 - you do. These tools generate React/Next.js apps under the hood. An attacker can just send a request to your server and they're in. Severity score 10/10 https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components Here's a video I recorded a video to help you understand the issue and fix your app.

Check them out here https://github.com/ZubairLK/security-agents Video on this dropping next week but thought I'd share with the community ahead of time. How are you guys securing your apps? Thanks

Hi all, Just thought I'd start some general discussion on what people are up to these days. I'll go first. - I have recorded a bunch of videos. A marketplace build series for bubble devs switching to AI code. Supabase 101 for Bubble devs etc. But need to prepare a whole bunch more marketing materials around it. - I've been really sick the whole of last week (bad case of food poisoning). Recovering from that & catching up with various projects at the agency What are you all up to & what are you planning on getting done this week? Thanks Zubair