Table of Contents
Introduction
AI Is Awesome
Failing Code and a Cold Bus
And Here Comes the "However"
The Name Itself
The A...
For further actions, you may consider blocking this person and/or reporting abuse
π Thank you! I couldn't agree more about the whole vibe-coding thing (and I'm just as much a fan of the name). You're right though - it DOES have it's usefulness and there's a time and a place to let AI run wild (production isn't one of them).
This is my version of, let's call it "vibe-adjacent" coding (because it IS really fun):
So why do it in the first place?
Had my goal been to build a prod-ready, enterprise scalable, fully secure app, then I would have just written one. What I wanted was to understand how to utilize AI, learn which prompts return the desired results, and have something shareable at the end. No - I didn't write the code. I spent weeks instead writing prompts and instructions, testing different AI models, slowly over time giving it more and more freedom just to see what happens when you push it to it's limits in that kind of environment.
That's about as much "vibe" that goes into any one of my projects!
The use cases in your examples are perfect. I think as long as you're learning along the way and helping others when you can, then have at it. The whole "I'm not a developer, but I built <insert thing of the week> with AI" thing? Drives me insane, too! (bonus if they throw in a "their job isn't THAT hard" or "I don't understand why they make xyz" somewhere)
I'm glad I'm not the only one π€
Thanks for sharing such thoughtful insight. Your comment alone (with a few additions) could easily make an article on its own.
I completely agree that vibe coding can end up being more time-consuming than just development, especially when you consider long-term maintenance.
Iβm really glad to hear the post was relatable to you! π
Wow such an explanation, loved each phrase and the way you described our old way of solving problems. Also agree, that it's easy to prompt and build a project with AI but maintaining is a skill which comes to developers through experience and constant learning.
Appreciate that! Thanks! π
Love how you capture the importance of the 'journey' in coding - it really is where most of the growth happens for me, too.
I'm finding that when AI tools are built to keep context and let you gradually shape things (vs just spitting out code), they can actually deepen that journey instead of replacing itβcurious if you think we'll get more of those tools soon?
Thank you! The AI tools are definitely here to stay and I think more of them will be added in the future β they definitely help us in many ways. I use them almost every day.
I can even state that AI tools made me a better developer in some ways, however we need to watch out not to overuse them, just like anything else in the world.
lol she created this post with an AI
Iβve just learned 2 new things about me that I didnβt know before:
Thank you!π
this is extremely impressive, the amount of stories and detail here lines up so much with my own early coding days
you think thereβll ever be a real way to blend deep learning and hands-on work so you donβt lose the vibe
Thank you! Iβve been outlining and refining this article for over a month β I didnβt want it to feel shallow. I wanted it to be relatable. Iβm glad I was able to get my point across.
I truly believe there has to be some ways for balancing between deep learning and hands-on work. Weβre at our most effective when we get the most out of both. And software engineering is all about effectiveness.
Excellent work
Appreciate that! π
George, you nailed it! I'm not "All In on AI" at all. I'm still quite skeptical about the current LLM-based AI assistant hype. Still, I'm using it, sometimes struggling, sometimes taking important steps forward to better code and new content creation ideas.
I had already collected some ideas for a new blog post about recent AI coding experiments, "real vibe coding" === "getting into the zone", and what has happened to Music Monday, but I had turned away a bit from DEV after its announcement to collaborate with Google AI. Posts like yours keep me coming back to DEV and inspire me to finish and publish my post drafts!
Where is the Vibe in Vibe Coding and what happened to Music Monday?
Ingo Steinke, web developer γ» Jun 25
Thanks for sharing! Iβll definitely check out your article.π
Growth like this is always nice to see. Kinda makes me wonder - what keeps stuff going long-term? Like, beyond just the early hype?
Thatβs a great question. I think the quick answer would be results. Time is the best tester.
deep researched done by AI. Isn't it??
The section about average energy consumption is actually from ChatGPT, since it was specifically about ChatGPT itself β I didnβt really know the exact numbers.
The rest is mostly based on my own research and thoughts. It took quite a while to gather everything and shape it into something representative but it was definitely worth the effort.