
AI Agent Upgraded My Codebase to Nuxt 4
From Nuxt 3 to Nuxt 4 in two hours. 45 passing tests. Zero manual edits. Here's what agentic coding actually looks like in the wild.

In 2021, I took part in the Toptal JavaScript Speed Coding Challenge. The goal? Solve 30 coding challenges in under three minutes. That's right - 180 seconds to:
Sounds wild, right? It was.
But what followed was a story of experimentation, automation, reverse engineering, and ultimately, a little help from the cloud.
My strategy was simple:
It worked. I submitted within 180 seconds.
Result: Decent score, but far from the top. I thought speed = copy-paste accuracy.
Time to automate the grunt work.
Result: Better score, still not #1. There's a ceiling even with automation.
Here's where things got interesting.
While inspecting the app, I noticed:
The browser wasn't sending my code to the server - only the results.
That changed everything.
I built a new approach:
POST.Result: Submissions in under 7 seconds. Top 10 in India. But I wasn't done yet.
One bottleneck remained: network latency.
Solution: I spun up an EC2 instance in AWS's US East (N. Virginia) region.
Final Result: Submission in under 4 seconds. Ranked #1 in the Indian Region.
Thanks for reading.
Namaskaram 🙏

From Nuxt 3 to Nuxt 4 in two hours. 45 passing tests. Zero manual edits. Here's what agentic coding actually looks like in the wild.

After six months of production RSC usage, one reframe made everything click: stop thinking about components and start thinking about render boundaries.

True stories from working around the world, where meetings meet adventures.