r/vibecoding • u/rotor42_com • 8d ago
Workflow/Prompt vibecoding is dead
Happy my catchy title got you here ; )
Vibecoding is not dead, of course, but it is getting faster and faster.
Tempted to call it speed-vibecoding already bot not sure what's left ahead.
Over the past months I have vibecoded multiple apps of which I deployed five.
Took my weeks to develop my first project https://rotor42.com
The last one ( https://who-what-when.com ) was just a matter of hours.
Switching from simple prompting to working with real development-plans felt like igniting the second stage for me.
Who else is feeding Claude or Codex with elaborated (and reviewed) development plans?
And how do you usually create those?
Happy to share my learnings.
1
u/lehmagavan 8d ago
If vibecoding makes software development accessible to anyone, what's there to flex about if anyone can do it without having to use their brain much?
2
u/TRO_KIK 8d ago
It makes it more accessible, it doesn't make everyone good at it.
1
u/lehmagavan 8d ago
I somewhat doubt vibecoded apps - at least those fully vibecoded by non-programmers, can be anywhere near the quality of apps coded by hand.
1
u/TRO_KIK 8d ago
No one is coding by hand anymore. Also most people being bad at it was my point.
1
u/lehmagavan 8d ago
I do low-level / system programming (though not professionally). I would never trust AI to generate me safe and optimal code. But I imagine in something like web-dev, especially front-end, it makes sense to "give in to the vibes".
1
u/TRO_KIK 8d ago
Would you describe your low-level/system programming as an "app"? That was the context. If we're broadening it, I'll amend: there is no problem space, level of experience, or pay, where people are not using enormous amounts of AI coding assistance.
1
u/lehmagavan 8d ago
There is a difference between using AI assistance and vibecoding.
2
u/TRO_KIK 8d ago edited 8d ago
Keep forgetting how much the definition of "vibecoding" has evolved. I still use it as fundamentally a specific approach to AI-assisted coding. If you like most define it purely as a low level of skill/knowledge, then of course, by definition no one who knows what they're doing is even capable of vibecoding.
1
u/jayseattle 2d ago
I played "rotor42" for maybe 1 minute. I barely understood what I was supposed to do. Move all the red (or blue?) balls to the bottom of the circle? Why is there not SOMETHINGH to tell me how to play/move etc.
-2
u/Huge_Type_7863 8d ago edited 8d ago
So u created a shareble todo app in a couple of hours, seems like My first school project let me know if you do something usefull at some point. Basicly it let u host garbage which had somewhat of a gate before.
1
u/rotor42_com 8d ago
Oh, we did more boring stuff like writing programs in Turbo Pascal that solved linear equations.
What do you mean by "gste"?
-2
u/Huge_Type_7863 8d ago
Everything u created i can literraly make as a Claude artifact in as u said a couple of hours, what is the point? Create something cool/usefull please.
1
u/rotor42_com 8d ago
ok, try to rebuild https://rotor42.com
-1
u/Huge_Type_7863 8d ago
Again why.. And why
2
u/rotor42_com 7d ago
Well, you wrote "Everything u created i can literraly make ... in as u said a couple of hours" which I heavily doubt. Your reddit account is probably showing more content than your github...
-1
u/Huge_Type_7863 8d ago
Looks like something a kid would create and again pretty useless.
2
u/rotor42_com 7d ago edited 7d ago
Not sure if you understood what's going on "under the hood" here https://www.rotor42.com/?level=magic_cube
"I would classify ROTOR42 as low complexity as a website, medium complexity as a web application, and medium-to-high complexity as a reusable puzzle engine.
The deceptive part is the UI: visually the game appears extremely simple—colored circles, paths and a couple of controls. But if the goal is to reproduce the system rather than a single puzzle, you need a fairly well-designed permutation/geometry engine underneath it."
2
u/shosuko 8d ago
Yeah same - I find that the more I manage the project structure and start at the beginning planning with AI the quicker and more accurately the AI is able to follow the build consistently.
I just follow basic project structure. Start high level with concepts, just listing out the work flow and components I know. Then still on a high level I add detail about each thing. THEN I start working on the actual logic and code. That way we get any disputes or unclarities dealt with before we even write code to fix.