• 1 Post
  • 102 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle













  • 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





  • Real answer: podcasts. Doughboys, Doughboys Double, Get Played, Get Played Season Pass (can you tell I like Nick Weiger?), Film Reroll, and Wait, Wait, Don’t Tell me

    Helpful answer: I like singing along to stuff so that ends up being a lot of 80s/90s pop and alt-rock stuff. CAKE, They Might be Giants, Garbage, Jamiroquai, Vengaboys, a bunch of one-hit wonders. Lately I’ve been on a bit of a trance kick so The Prodigy, Fatboy Slim, Chemical Brothers, and Daft Punk are in there too