Atharv Ketkar

Vibe code to pro

Well you might have noticed that vibe coding is frustrating

I strongly believe things get frustrating when we are not winning, when things are not in our control, when we are not understanding what is going around us

If your purely vibe coding then that’s going to happen sooner or later

And that’s why I would advise you to start acting more like actual developer

Instead of saying hey fix this Upload error

it would be a lot more helpful for you and the AI to first go:

  • Hey what part of our code base is responsible for upload
  • Hey what might cause our our code to give this exact error
  • Hey what can we do to bulletproof this whole process so that we are operationally sound from things like loss of connection, user mischief or server timeout etc.

These actually shows you which part of your code are responsible for what

And in that process they load up the context window of your AI model

And you might also actually learn what kind of errors arise from what type of setup

You will be able to identify errors and describe them better

You’ll be able create solutions and design systems that are way more robust

And if you keep doing this for months you will be no longer a vibe coder

You will be actually learned person

A pro at work

Example from claude:

❌ Vibe Coding:

You: "Upload is broken, fix it"
AI: *changes random stuff*
You: "Still broken"
AI: *changes different random stuff*
(repeat until frustration)

✅ Developer Approach:

You: "What's the upload flow in our codebase?"
AI: *shows client-side handler → API endpoint → storage*

You: "The error is '413 Request Entity Too Large'. 
     Where are size limits defined?"
AI: *shows nginx config + API validation*

You: "How should we handle this gracefully?"
AI: *suggests client-side validation + chunked upload + 
     proper error messages*

You: "Show me where to add client-side file size check 
     before upload starts"
AI: *precise change to validate before API call*

Result:

  • Problem solved correctly
  • You understand your upload system now
  • You can handle similar issues independently
  • The fix is robust, not a band-aid