Quote · The MongoDB Podcast
Modern AIOps: What It Takes to Build Reliable AI Products
Where this was said
Vibe Coding and the Evolving Role of the Developer
At 51:23 · chapter starts 49:40
Jesse raises the polarizing topic of vibe coding — building products by prompting AI agents rather than writing code directly — and whether platforms like v0, Lovable, and Bolt are a liability or a force multiplier. Karthik's answer is nuanced. Vibe coding is real and increasingly how products get built, even by experienced engineers using tools like Cursor Agent or Devin. But it amplifies what you already know rather than replacing what you don't. His personal war story makes the point vividly: he asked Claude Sonnet to fix a bug, and it returned 50-100 lines of code. [1] — Karthik Kalyanamaran "AI coding agents like Cursor or Claude Sonnet can write 50-100 lines for a bug that needs one. If you can't read the code, you'll ship a me…" 49:40 The correct fix was a single line. A developer without strong fundamentals would have accepted the bloated solution, resulting in a codebase that accretes complexity with every AI-generated change. Jesse draws the synthesis: AI coding tools are like upgrading from a hammer to a drill — you move faster, but you still need to know how to build. Karthik suggests Langtrace-style observability baked into vibe coding platforms could help close this gap, a product idea he admits he'll be thinking about.
AI coding agents like Cursor or Claude Sonnet can write 50-100 lines for a bug that needs one. If you can't read the code, you'll ship a mess. Vibe coding doesn't eliminate the need for programming knowledge — it changes the job from writing code to critically reviewing what AI produces.
