You do have to consider that this is an opensource developer creating something free in his free time. The app is also not life or death. Meaning, his quality standards are UNDERSTANDABLY not as high as if he was working for money on a banks money system.
In the end, all of the complainers are welcome to do the work themselves. That way, he won’t have to use AI at all.
No, vibe coding explicitly requires NEVER looking at the actual code. I can give claude a ticket, it creates a plan. I review that plan, maybe change some things. Then claude does the thing. I review the code, then tell claude to fix X. Then I test, then I tell claude to create a commit.
There we have claude creating a commit without any of it being vibe coded
From his perspective, he’s investing his free time and likely money into a project for people that are 99% of the time just leechers, as in they never contribute back and only complain.
Now he has a tool that he feels helps him deal with all that FREE labor is doing for everyone, and the very same people now want to tell him how to do his FREE labor he does for them.
I completely understand being pissed off by that.
This really depends on the project. For example, if you’re creating a CRUD web app for managing some kind of data, the main tough decisions involve system and data architecture. After that, most other work is straight forward menial work. It doesn’t take a genius to validate a gajillion text fields for a specific min and max length, map them to the correct field in the API, validate on the server again, and write them to the correct database field.
I agree that AI might screw companies over in the long run, when there’s no more juniors that can become seniors. That doesn’t apply to this case at all.