Christian Nwamba

3 months ago I started building a coding agent that runs in the cloud. It's since written every line of code I've shipped, including itself. Today, I'm open sourcing it. Introducing Open Agents.

Time for a big systems advice thread! In distributed systems there's no magic "push everything to prod at once" button. Every service gets pushed independently and nodes within a service get updated incrementally. If you mess up forwards/backwards compatibility you can fail irrecoverably. So how to avoid this? 1/5: Decouple data and code changes. Never push out a release that changes how data is stored at the same time as the code that uses this new data. If there's a bug and you need to roll back to the old version of your code it won't be able to handle the new data in the new format. Instead push out a release that first changes the data in a way that’s compatible with both the old and new code (e.g., optional fields etc), when that’s stable push out the new code that uses it, then when that’s stable you can change the data to remove backwards compatibility. This is known as a “migration” in the database world and yes it’s annoying, but yes you need to do it.

@tannerlinsley Where can I buy tickets?

Instead of doing a TanStack Conf, I'm seriously considering inviting everyone to just meet up on a Caribbean-bound cruise ship. It'd be cheaper in every way, you could bring as many family/friends as you want, and instead of wasting time on talks/booths, we can just chat endlessly about JS/TS/Web over unlimited freestyle soda machines, soft-serve ice-cream and mini golf. TanStack Cruise 2028

The World is Changing. AI is changing everything. A lot of my homies and followers ask me what they should do… This video is my answer ↓

@Rasmic Oh musicians 😂

@wesbos Works on my machine!

Only cool people can reply to this

@theo You forgot one: we’re are COOKED

Oh no I forgot to do the buzzword clickbait. This AGENT ORCHESTRATION CODING APP CHANGED MY LIFE. Claude Code? dead. Cursor? 2024 was 2 years ago. Codex? If you hate having RAM. T3 Code is the FASTEST way to escape the permanent underclass.

T3 Code is now available for everyone to use. Fully open source. Built on top of the Codex CLI, so you can bring your existing Codex subscription.

@jamwt @convex While I appreciate the simplification of these, I like this delivery and format @jamwt Hope we see more.

I made a video demystifying database consistency, isolation levels, record contention, and pessimistic vs. optimistic concurrency control tradeoffs. (I also said "dollars" instead of "pounds" 40 times.) Check it out if you want a basic working knowledge of this stuff.

@royanger @theo Finally got the chance to catch up on some @theo’s video and found myself here

Me: 'Why I am suddenly getting a big influx of followers?" Thanks for the very kind words @theo!

🚨 You can now author @convex components I built the Stripe component (thanks @theo for pushing for this) With just a few minutes setup, you have payments integrated into your convex projects I'll link the doc down below 👇

Cool planning agent pattern with @aisdk Agent creates a plan. Then, while there are outstanding tasks, forces a tool call (executeTask) that spawns a subagent to complete the current task

We just raised a bunch of money to reinvent backend engineering for developers. We have huge plans for Convex, and we need your help to realize them. news.convex.dev/convex-raises-…

Person A: "Let's index the entire internet!" Person B: "😂 Sure, just casually rebuild Google. What's next, solving world hunger?" Ilya Sutskever: "Hold my beer."

The hardest part of being a technical founder isn’t shipping fast, it’s learning when not to. At @rivva_app, we were building a mission-critical feature: AI that can look through your emails, understand them, and turn them into actionable insights. It was tempting to build it myself. I knew exactly how to do it: parsing emails, orchestrating agents, turning them into structured data. I could’ve shipped it in two days. But I had a choice: 👉 Do it myself and move fast 👉 Let one of our engineers take ownership, learn deeply, and move a little slower He took four days. But here’s the surprising part — now he doesn’t just understand the code. He understands the why. He joins product meetings with strong opinions, connects engineering decisions to user impact, and even challenges product direction with insights I wouldn’t have thought of. If I had built it myself, we would’ve saved two days. But we would’ve lost a leader in the making. As a CTO, my job isn’t to build every feature. It’s to build the people who’ll build them — even if that means watching someone take the long road that I could’ve sprinted. Speed gets features out the door. Patience builds a team that can ship without you.

Me: “Don’t use any.” Claude Code: “You’re absolutely right.” Claude Code: Thinking deeply…. Claude Code: Searching node modules…. Claude Code: user as any

Agile: move fast Assigned to me:

Tutorial: 5 minutes. Real life: 5 hours of debugging why it doesn’t work like the tutorial.

@GitKraken haha

@codebeast Let us soothe your soul :)

git still scares the crap out my soul

@_JitendraM exactly

@codebeast One wrong command and you reach in alternative timeline 😅