“vibe coding” is cool, but not the future
For the last couple of weeks I got back to my code editor. But instead of VS Code I installed Cursor. Added Claude 3.7 to it. And started “vibe coding”. The challenge was simple. I wanted to build a…
Apr 11, 2025 · 3 MIN READ
For the last couple of weeks I got back to my code editor.
But instead of VS Code I installed Cursor.
Added Claude 3.7 to it.
And started “vibe coding”.
The challenge was simple.
I wanted to build a simple browser based game to surprise my girlfriend.
She loves pandas.
So I said let me make a game about a little panda who has to eat bamboo in order to pass to the next level.
For the tech stack, ofc I went with React and TypeScript.
One reason AI coding tools became so popular is because of how easy they are to get started with.
The only thing I had to do was to talk to Claude via the chat and approve the code changes it suggested.
It took me a few seconds to get the basic game built…
And it took me hours to debug it, extend it and deploy it!
(it might not look like much, but I am proud of what Claude and I built)
This is how my workflow looked like:
Talk to Claude via text or voice
Claude writes the code
Accept changes in Cursor
Test
Report bugs
Repeat (hoping Claude will fix it)
Question my career choices cause this is boring as hell
What’s the problem with this workflow?
It is not FUN!
Is passive.
It is chatting. Waiting. Debugging. Hoping.
I am not a software engineer any more! I am a Senior Tester working together with a Junior dev that gets easily confused.
If this was how coding looked like back in 2025 when I started….
Then I would have probably chosen another profession!
All in all, here are a few lessons I learned:
The same skills that make you a good developer, will make you a good AI-developer
To avoid creating a big pile of garbage code, you have to put in place the same good old engineering best practices (clean code, SOLID, separation of concerns)
You need to create a Read me for Claude to understand your project, and your architecture decisions
Context is a lot more limited than most AI companies want you to believe
Cost is really cheap at the beginning, but escalates quickly
And regardless of whether you use AI or not…
You can’t build what you don’t understand!
If “vibe coders” will want to become professional software developers and build bigger things than half-assed demos….
Then they will have to learn the same stuff a traditional software dev had to!
Nope, AI will not take your coding job.
Yes, I do see myself and other developers using these technologies... But I don’t see them replacing our jobs anytime soon.
Actually the opposite.
The copy-paste nature of programming will mostly be done by some AI helper in your editor, allowing you to do cooler stuff… Like high level design, performance optimisation, or coming up with better features for your app.
Talking about cool stuff…
Bogdan and I are taking next week off for Easter break. We limited our April spots to only 5. Half of them are already reserved.
If you are interested, book a call here and let’s chat!
Have a lovely weekend!
Dragos
P.S. My girlfriend loved the game, she is still playing it as I am writing this! Yet, after checking out my Claude bill, I think flowers would have been cheaper!
I know... Is the gesture that matters :)
