WordPress

732 readers

1 users here now

A place to talk about WordPress the open source content management system. Also a place to ask for help with WordPress. Don't be rude, don't spam.

I check this once a week, so if you don't hear from me hit me up on Mastodon (phillycodehound@indieweb.social)

founded 2 years ago

MODERATORS

phillycodehound@lemmy.world

Boss is "vibe coding" (lemmy.world)

submitted 2 weeks ago by rayquetzalcoatl@lemmy.world to c/wordpress@lemmy.world

24 comments fedilink hide all child comments

My boss thinks it's very cute to talk about AI as much as possible, and today asked if I'd heard of "vibe coding". I said yeah, and explained to my coworker that it's where you get a chatbot to write all your code.

My boss has just announced that he's vibe coding. I know the project he's working on. It took us months to put that codebase together, and there are a lot of very complex functions and plugins in that site that we've written to integrate with all the systems our client needs the site to use.

What am I supposed to do here? He's just letting a chatbot go rogue on the codebase. Do I just leave him to it with the full knowledge that it'll fall on me and my colleague to repair all this damage, presumably while being accused of breaking the site in the first place? I need the money from this job so unfortunately leaving isn't an option at this stage.

you are viewing a single comment's thread
view the rest of the comments

[–] makeshiftreaper@lemmy.world 16 points 2 weeks ago

If possible create local backups from before he let AI go loose. Likewise, save local copies of all of your commits and document all of your commits thoroughly. This way when things start breaking in the future you have documentation that shows that you didn't submit faulty code, and if the AI changes your work you have proof of what you did. Additionally if it manages to truly break something you get to be the hero and save the project

If you want to go the extra mile I'd pay attention to what your boss submits and either clean it up behind him, or log all of the issues and errors. Option 1 keeps them happy without breaking anything, option 2 lets you make a presentation and argument that vibe coding is bad practice

Generally just add some more work into your general "cover your ass" activities. Alternatively you could gather evidence of the dangers of vibe coding, present your case to your boss, and hope he realizes it's a bad idea. But this is lemmy and I know we're not a confrontational bunch