I love vibe coding and whenever I get bored, I vibe-code some websites for myself or for Dev Challenges.
I’m a little late sharing these because I...
For further actions, you may consider blocking this person and/or reporting abuse
“Do this only” looks like a good idea so AI does only what you want. It is fun to swipe and choose on BitMatch. 🍔 Thank you for sharing!
Thank you so much. I feel you have finally found your perfect bite 😆.
vibe coding is the only way i ship anything anymore. it gets you to the finish line fast — though that last 10% usually requires waking up your actual brain. vibe first, polish later is how i keep moving. since you're building focused tools, you might like stackapps.app — i built it to solve the traffic problem my 11 live apps have. full disclosure — when i'm promoting something commercially i say so, and i only write about tools i actually use.
That's should be everyone's moto to vibe code and finish fast. That sounds nice vibe first, polish later. I'll try someday as well.
Ok cool. Stackapps seems cool. I would to try it. Thank you for sharing it and keep up the good work.
I started using Antigravity for my vibe coding projects, mostly trying to build useful, problem-solving websites that actually add some value. I’m still pretty new to it, but I can already relate to a lot of what people say about vibe coding.
The most frustrating part is usually when you get stuck and the tool (Antigravity, Cursor, or anything else) just doesn’t do what you’re imagining. That’s kind of the “grey area” between what you want as a human and what the machine actually understands.
What I’ve found helps is actually pretty simple — just take a break. Step away from the project, completely forget about it for a bit, and then come back after a few hours with a fresh mind. Most of the time, things suddenly make a lot more sense and you solve it way faster.
Might be a bit off-topic, but I just wanted to share this thought. Happy to share one of my vibe coding projects with you soon as well.
Perfect. The idea of taking a break and let your mind relax is better approach rather than getting frustrated and keeping prompting. Loved the idea, thanks for sharing.
Sure, I'm excited for your project. All the best for it.
The lesson nobody talks about isn't about the model - it's about the half-formed mental state vibe coding rewards. The reason it feels productive is the model fills your gaps before they hurt. The cost is you stop noticing where your understanding ends. The cure isn't 'don't vibe code', it's a forced pause before merge: rewrite one method without help, and if you can't, you didn't actually finish the feature, the model did. Saved me from shipping a few class hierarchies I didn't actually understand.
You are right, Andrii. Half-formed mental state vibe coding is the real issue sometimes. Exactly, the gap is filled by the model.
That's a pretty good suggestion, to rewrite one method without help. Seems, pretty helpful to you. I'll use it as well next time I vibecode. Thanks for your wonderful advice.
Glad the 'rewrite one method without help' check landed. The reason I trust it more than write-from-scratch tests: it forces you to face the parts of the codebase you'd been outsourcing semantically. If the method takes 3 attempts unaided, that's the area where the model is doing your thinking. That's the part that quietly stops scaling. Curious which method you try it on first.
Nice write up, but this really annoyed me:
Really? This advise directly leads to bad code quality and security holes. If it's a bug, fix it! Maybe give it a lower priority if it appears to be minor, but keep it on the list. Of course that is not so important for one-shot code for a competition or so, but don´t give it as general advise, because this is bad advise! Whoever those "they" are, don´t listen to them as they have no clue about proper software development. I say that as a professional software developer, but luckily working at a place where quality is still a factor.
Sure, Stefan. I got your point. I wrote it wrong. I'll keep your advice and update the article. Thanks for pointing my mistake.
Vibe coding is not about replacing skills, it’s about speeding up imagination— that line perfectly explains the whole journey.
Perfect. Have an awesome time transforming ideas into reality.
vibe first, polish later is basically my religion at this point. glad stackapps caught your eye—shipping fast is the only way i beat the overthinking trap. definitely give it a spin.
Great work! I am not a fan of vibe coding too much. I need to try it with openclaw. Thought!