I was really excited about this hackathon because it was an offline event and completely focused on prompting and building a web game using AI.
Bu...
For further actions, you may consider blocking this person and/or reporting abuse
This is a genuinely useful post because it documents exactly the gap between "AI generates code" and "AI generates correct code under pressure."
The hackathon setting makes it even more telling. When you're vibe coding for a demo, the stakes are low — if it breaks, you regenerate. But the habits you build there carry into real projects where the cost of a subtle bug is way higher.
What I keep coming back to: the bottleneck was never generation speed. It was always verification. You can get AI to write a game loop in 30 seconds, but figuring out whether that game loop actually handles edge cases correctly takes the same amount of human attention it always did. Maybe more, because the code looks plausible enough that you trust it.
The METR research on AI-assisted coding showed developers perceived they were 24% faster while actually being 19% slower. The gap comes from exactly what you described — the time spent debugging and re-prompting eats the generation speed advantage.
Not saying vibe coding is useless. But knowing when to switch from "generate fast" to "verify carefully" is the real skill. Sounds like the hackathon taught you that under pressure, which is the best way to learn it.
I'm really glad you found my article useful.
Yes, you are absolutely right about the verification and you have made a valid point of game loop actually handling the edge cases. This got me so much frustrated as I wanted to add different levels to the game and make it more difficult for the user to play but while doing so AI started doing things on it's own. The original game logic for loosing was kinda lost while building levels in the game. So, yeah I agree with you it doesn't make us faster it actually makes us slower cause the execution can divert into any possible way and I have to teach AI to do how I want it.
Yes, I learned a lot about AI Studio, Antigravity and Prompting while building the game. If you are willing to learn even a small ant can teach us amazing lessons.
What's was the bug you found most annoying while debugging?
This is such a real take! It’s easy to think AI tools make building a game simple, but the 'pressure test' of a hackathon always reveals the gap between prompting and actually debugging. What was the most unexpected bug the AI introduced for you?
I'm pleased that you liked it. Yeah, pressure test really shows the capabilities of AI in real life like how would a developer react to a 2am call for a production bug but for me the gap was larger.
The most unexpected bug the AI has introduced to is when I prompt it to do some changes in a long conversation it tends to redo the tasks I prompted it to remove. Like, I'm waiting for an output but all I get is new output and previous outputs. It really creates a mess in the code and also in AI studio it can add files but can't remove them, I prompted it many times as it was an unnecessary file but it couldn't delete the files.
What's an unexpected bug you faced while vibe-coding or any interesting story you wanna share?
That's such a relatable experience! 😅 The 2am production bug analogy is spot on — pressure testing really does expose the gaps.
And yes, that issue with AI redoing old tasks in long conversations is painfully familiar! It's like the model loses context of what 'remove' actually means and just keeps adding layers. Definitely creates chaos in the codebase.
The AI Studio file limitation is weird too — being able to add but not delete? That's such a basic need. Hope they fix that soon.
As for unexpected bugs I've faced — one time the AI kept importing the same library 5 times in one file no matter how many times I told it to stop 😂 Took me longer to clean up than to write it myself!
Would love to hear more about your hackathon experience — what were you building?"
Yes, it has happened to me as well. I told it to remove the library but with newer instructions it kept adding it.
It was a wonderful experience every hackathon comes with it's pros and cons and as for the building part I have provided the link in the submission attempts. Though, it is still in prototypal phase but I included it to share what I have built on. Here's the link for you.
Glitch Hunt
What's your hackathon experiences or have you taken part in a Dev Challenge how was it?
Although I'm not a vibe-coder, I'm a developer. It actually gives couple of interesting facts to bear in mind as I will attend a hackathon in April. Good to know, thanks for the article !
I'm really glad you liked the article. Thank you so much for your support. Give your best in the hackathon maybe we will get to see an amazing build by you and shared in form of an article. Looking forward for your experience.
Hopefully, that hackathon will be my official farewell with web-dev and smart-contracts and focusing only on cryptography and blockchain architecture (What I actually do currently). You can read my first article where I introduce my self also feel free to connect on signal or telegram.
For sure, I would read that. I am sure you will lead the way of cryptography and blockchain on Dev.to. I would love to connect and learn more about blockchain from you. It is the most fascinating thing I like in Web3.
The hallucination-under-pressure pattern is consistent — models get more confident-sounding exactly when context degrades, which is the worst time to trust them. The planning phase working well but execution breaking down is exactly the gap most vibe-coding workflows haven't solved yet.
Yes, exactly what I faced while working with vibe coding workflows. I think they lack in the execution of the context because if I say do Task A then it will do Task A + B resulting in a more chaotic output.
What's your favorite vibe coding tool you use?
It is so true
I'm really glad you liked it. You are also providing such amazing articles. Keep up the good work.
Ah, thank you!