Christian Nwamba @codebeast

Jack of a few trades. JavaScript. Teacher. Musician. Co-founder & CTO @rivva_app. Prev @AWS @Microsoft, @cloudinary, @auth0 London, England Joined September 2012

Tweets

15K
Followers

39K
Following

2K
Likes

16K

Evil Rabbit @evilrabbit_

a day ago

It’s incredible to think we launched Geist just 3 years ago. Today, it’s served 181 million times per week on Google Fonts.

Evil Rabbit @evilrabbit_

3 years ago

↳ Vercel Sans Coming this Spring

96 238 3K 493K 457

22 4 214 20K 20

View Details

Things that make your codebase legible to agents (learned the hard way): 1. One source of truth. No content hiding in a CMS the agent can't see 2. Names that say what they do 3. Tests that double as docs 4. Delete dead code. Agents trust it like it's load-bearing

1 1 5 406 0

View Details

AI SDK @aisdk

2 days ago

Use Claude Fable 5 with the AI SDK.

Claude @claudeai

2 days ago

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use. Its capabilities exceed those of any model we’ve ever made generally available.

5K 14K 102K 50.4M 21K

2 6 49 5K 3

View Details

Guillermo Rauch @rauchg

4 days ago

Vercel AI Gateway recovers on average over 1T tokens a month 🤯 Much like Stripe recovers revenue with smart retries on failed payments or credit card updates. And we do it with 0️⃣ zero markup over the labs; adding redundancy, zero-data retention enforcement, observability, usage APIs, caps, … vercel.com/ai-gateway

45 32 352 55K 72

View Details

R 'Nearest' Nabors @rachelnabors

3 weeks ago

x.com/i/article/2057…

8 18 155 51K 404

View Details

v0 @v0

3 weeks ago

v0 Foundations is live. A 7-lesson course, under 20 minutes, to take you from your first prompt to a real app in production, walking through database, email, custom domain, and GitHub. Taught by @eveporcello vercel.com/academy/v0-fou…

11 21 219 15K 128

View Details

AI SDK @aisdk

4 weeks ago

AI SDK 7 canary has a new telemetry system. Register telemetry once, then all AI SDK calls emit telemetry by default.

4 8 151 31K 28

View Details

Chris Tate @ctatedev

4 weeks ago

I built Zero in 3 days. I didn't expect it to compile. I didn't expect it to mostly self-host. I definitely didn't expect it to work at all. Inspired partly by Bun's rewrite to Rust, Zero started as an experiment. Honestly, the project says more about where AI is today than it does about the language itself. It took more than 3,000 agent tasks to get here, and it's still nowhere near ready for serious comparisons, benchmarks or evals. But the goal is bigger than the current result. The hope is to either create a new language with tooling designed for agents from the ground up, or take learnings and apply it back to existing languages and ecosystems. The ideas are simple: 1. Make languages (and new versions) easy for agents to learn, adapt to and fix on the fly, even when not in the training data. 2. Build a standard library comprehensive enough that most projects don't need external dependencies. 3. Create a tight, fast development loop that even small models can reliably work with. I've never wanted to create a programming language. But after repeatedly running into the same problems, safe but slow builds, fast but unsafe builds, agents struggling with new languages and version changes, wanting faster builds, smaller bundles and better DX, I started wondering: Could accelerated, agent-driven iteration produce a language and tooling stack designed around these constraints from the start? So Zero was born.

Chris Tate @ctatedev

4 weeks ago

Introducing Zero The programming language for agents. I wanted a systems language that was faster, smaller, and easier for agents to use and repair. Explicit capabilities. JSON diagnostics. Typed safe fixes. Made for agents on day zero.

394 210 3K 1.7M 2K

99 38 738 143K 322

View Details

Chris Tate @ctatedev

a month ago

New proposal: mdxg.org Markdown Experience Guidelines A spec for how interfaces should present Markdown Virtual pages, navigation, search, theming Any .md file, zero changes Reference implementation below Would love your input

23 27 501 37K 447

View Details

Chris Tate @ctatedev

a month ago

Introducing zero-native Build native desktop + mobile apps with web UI and Zig → Tiny binaries, low memory usage → Selectable web engines (WKWebView, WebKitGTK, WebView2, Chromium/CEF) → Next.js, Vue, Svelte, Vite, React → macOS, Linux, Windows, iOS, Android

162 290 4K 548K 4K

View Details

Nico Albanese @nicoalbanese10

2 months ago

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.

140 203 2K 402K 3K

View Details

James Cowling @jamesacowling

2 months ago

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.