You don't have the code in git or something? Let him vibe code on his own local branch
this post was submitted on 21 May 2025
38 points (100.0% liked)
WordPress
746 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
We do have it on git, after long insistence on my part, but it's just a pain in the arse having to undo all of what he'll merge into main.
Get really excited about vibe coding and tell your boss it works better if you make an AI specific branch. Toss main branch protections in and you’ve basically given your little brother an unplugged controller to play with.
Genius 😂
This guy 🫡
Just don't let him mess with main at all...
Time to change to rebase only workflow. Easy reverts.
Ask about security concerns of feeding your proprietary code to an AI where it will be used for training data.
They likely don't care.
Better way to phrase it is 'Had legal signed off on allowing our IP and confidential data to be sent to AiProvider?'
You're dead right that they don't care! Unfortunately we don't have a legal dept but not a bad shout on the confidential parts...
Do you have source control? Constraint it to testing branches, read, test, and check before letting stuff go into production.
So just the regular workflow.
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
I would save a local version of the code from before his AI bullshit, and get paid handsomely later to just copy and paste old unshitty code in to fix problems.
Assuming he's just a middle manager, just express your polite disagreement everytime it makes sense by writing in a way that will cover your butt when shit eventually hits the fan and higher ups step in. If he's the head of the company, maybe you should spend teaching time with him to avoid losing your job when the company fails.
Unfortunately it's a small agency, so him and the big boss work in tandem. They've both hauled me into meeting already about how I need to be more positive about AI 😂
“I am positive that AI will break shit.”
Hopefully you backed it up.
You have git, let him break it all and then just revert. Pain is a great teacher, it's why I don't touch fire as often as I'd like.
Do you have backups?
We've got it all on git
Good