I unironically agree with @bcherny’s take that “coding is solved, but bugs are not.” The deeper mea...
Guillermo Rauch(@rauchg) · 软件开发
I unironically agree with @bcherny ’s take that “coding is solved, but bugs are not.” The deeper meaning is that you can in theory code *anything* now. You can burn infinite tokens refining and optimizing. Including optimizations that no one will care about 💀 With Vercel you can build a different kind of recursive improvement loop. You capture traces from production, you then optimize and course-correct based on how your software is being used IRL. This is not a new idea. The best engineers I’ve ever worked with never jumped into coding (now prompting) right away. You instrument the system, collect data, understand distributions, user journeys, and then put fingers on keyboard. You can ask your agent today to look at your traces! Vercel Developers @vercel_dev Vercel Tracing is now GA on all plans. Starting with Next.js 16.5, new projects have it on by default. Search and inspect spans from the dashboard or the CLI. ▲ ~/ vercel traces search --status error vercel.com/changelog/verc… 🔗 View Quoted Tweet 💬 58 🔄 6 ❤️ 182 👀 13224 📊 61 ⚡ Powered by xgo.ing