Mastodon Feed
dysfun@treehouse.systems ("gaytabase") wrote:
no i'm not vibe codding today, but i have been having thoughts.
most importantly, they make fewer clangers when doing less work at a time. how do you structure everything to make it do less work at a time without having to supervise it constantly? not sure. lots of files?
they are absolutely terrible at iterating. they like to give up and their solution is often to attempt a rewrite rather than fix the errors with what might have been borderline acceptable if they'd just fixed it.
oddly enough this is not an error i have with programming languages - they manage loops just fine. i could for example with the right tools rather easily knock up a loop that builds, runs the tests and otherwise instructs it to continue solving the problem. well the loop bit is easy, at least, but getting the cod to do the thing might be harder.
maybe i can drip feed it errors? it definitely gets confused when receiving a lot of them at a time and what i said earlier about less at a time might work.
so it's not a complete fix, but i think i could probably do a better job if i wrote my own vibe codding apparatus - one that appreciated that there are algorithms other than machine learning available to solve problems. unfortunately this is sounding like a lot of effort to make the silly thing less silly. like an actual engineering problem, in fact.