Before judging me, give me 5 mins. Exactly 5 mins. Start the timer!
Let me explain through a story –
Once upon a time, there was a developer who used to code everything on his own. He had strong coding knowledge, and whenever he got stuck, he would Google his doubts and spend hours debugging – but eventually, he always found the solution by himself.
But one day, he was greeted by a friend named GitHub Copilot. It helped him by suggesting quick and small code snippets.
Copilot – “Writing a for loop? Based on your code, this looks like something you wish to write?”
Developer – “Oh my God! Yes, thank you!”
Just like that, it became his coding buddy – always beside him while he coded, suggesting snippets, gradually reducing his need to Google for syntax help, and boosting his coding efficiency. Now, he no longer had to context-switch to search for simple things; he could stay fully focused on writing code!
And occasionally, it even helped him understand tricky code snippets in simple words – like a true buddy – when things were too complicated for his brain to grasp quickly.
That sounds so positive! Copilot is such a good buddy!
But wait! Here comes the plot twist. One day, the buddy left 💔! And suddenly, everything around him (his IDE 😛) felt so lonely.
He found himself thinking, “What the hell is the syntax for this simple thing?”, “I’m Googling this? Seriously?” Pretty sad, no?
Whose mistake was this? Copilot’s? The developer’s?
I’ll say no one’s!
Because it was just a small phase – one that passed very, very soon. Soon, everything got back on track. He started remembering the syntax again and got back to coding just like before.
So, no downside to this friendship. In fact, it sparked a realization in the developer about the usefulness of having a coding buddy – aka AI.
Soon, he started a new friendship with a new coding buddy named ChatGPT.
This was a different kind of friendship. Instead of just helping with small code snippets, this buddy started helping him generate entire complex code blocks. Something that would have taken him 30 minutes to write? He could just ask his buddy to generate it. Then he’d review it, refactor it – and done! All in much less time!
Of course, sometimes his friend hallucinates a little bit – but that’s fine. Because even when it does, it still gives him something useful to start with – something he can tweak and get his work done.
So you see how amazing this friendship is?
In the end, it’s never about the tool. It’s about the talk.
The better you speak, the better it listens.
A real friendship – human or AI – is built on communication.
Stop the timer!
So, that’s what I meant by vibe coding.
What’s stopping you from coding like this?
Do you think the developer will forget everything and become dumb?
If so, I want you to re-read his first heartbreak 💔
Do you think it’s risky? Security concerns?
That’s why the developer is still there.
When your friend suggests something, don’t you double-check it?
If you don’t, then that’s your mistake, not your friend’s.
And that doesn’t mean you shouldn’t take advice in a friendship.
Want a demo?
Recently, our fellow developer was working on a feature and needed a table with around 1k records.
Sure, he could’ve done it himself – by exploring, Googling SQL commands, and piecing it all together.
But that would’ve taken him, let’s say, 30 minutes?
So, instead, he just asked his buddy 3 questions.
And within 5 minutes – I repeat, 5 minutes – he had the table ready and could continue his work without distraction!
It just required proper communication and feeding the right data. That’s it! Here’s the chat if you wish to read.
Our dear developer isn’t that great at writing, but he’s pretty good at storytelling.
So he narrated this blog…
While his dear friend ChatGPT wrote it for him 😉
Any guesses who our dear developer is?
How was the blog?