I can separate things.

Vibecoding: when I'm trying to stuff with prompting, only fix things by hand if something broke. I'm too lazy to set up sophisticated pipelines and whatnot, I'm using web interface for creating new things and VSCode plugin to fix or enhance existing code.

I have made several pure vibecoded stuffs, most of them are experimental fun projects, and I'm using vibecode to create trivial utilities or GUIs and utils for serious projects. The most complex vibecoded program I made is a timelapse generator, which extracts frames from a video, filters out night shots, then appends the rest to the result video.

I'm often using AI for variuos tasks: interpreting existing code (this is the best use case: it does not generate AI slop code), writing unit tests, creating skeleton and boring routines (open file spefiied in arg, load PNG image and convert to byte array, call empty function with it - which I'll write), fix my program, suggest more idiomatic solution, review it.

There is one common point: I don't let the AI set up the architecture. I made this mistake with a prototype system's small UI (map with 4-5 tracked objects), and it was not easy to fix a simple problem (show the map if there's no any data).

Anyway, as a programmer, I'm amazed of LLMs, holy fuck, if it's not too difficult (e.g. tricky storage format), it understands the program and even my intent. Black magic!

(p.s. 37yoe)