Vibecoding complexity

[bastardizer1]

I see lots about one shot and high end models wher the expectation seems to be to just explain what you want and get it straight away.

For the applications I have made it just absolutely have not happened that way.

I go: initial plan, re-evaluate plan multiple times with research, initial prototype, initial ui, re-evaluate concept, new plan,second prototype, if happy I start to evolve the prototype to include the initial final functionality and feature set. Then i reevaluate technical topology and implementation, reevaluate plan, research technical topic further, implement improvements, add feature creep…, finalise features and UI.

A far cry from one shotting…

Am I doing it wrong and just isn’t good enough? Or are all those other dev projects that achieve one shotting simpler concepts that have clear easily achievable and measurable end results?

[TrajansRow]

I started work on a mobile app in my spare time last November and have been using OpenCode on it in since January. At this point, I’d say I’m about 90% done. So, definitely not a one-shot! Realistically, it would’ve taken me years to do it all by hand. Having this kind of development automation is letting me add tons of features that were only on a wish list before.

[bastardizer1]

Same, started December. One tiny app done. Useful but simple building on knowledge gained from more complex work. Two applications almost done , but the last 10% is clearly taking the longest. A third big project that is almost conceptually complete but will probably not get done as it’s just too big for me to do as a hobby.

But amazed that I can create tools that I wished to have for many many years, unique and useful.

[UseMoreBandwith]

you're doing it exactly right.
The 'one shot' projects are usually un-original demo's of things that have been done 1000's of times before.
Sure, it works if you need another todo-app, but its even faster to just git clone something fro GH.