Programming

28720 readers

332 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

109

Is Vibe Coding the Norm Now? [rant/vent/advice welcome] (beehaw.org)

submitted 2 weeks ago by luciole@beehaw.org to c/programming@programming.dev

161 comments fedilink hide all child comments

Hello programmers! I’ve been making a living for a couple of decades figuring out stuff for people and coding whatever will make them happy. It’s fun. I’ve grown to prefer the people to the coding but I still get a kick out of the whole thing.

The problem is: at the job we’re being asked to pivot to vibe coding. At this point the order is to use it for all code, read the slop carefully, argue with the machine for way too long and only then open that PR. Massive productivity gains are expected. I’m appalled from an ethical, philosophical and professional standpoint. We’re a non-profit ngo ffs. My colleagues are fine with it. If I get even slightly critical the group goes awkwardly silent and I get comments on how all the programmers they know from other places don’t code anymore.

If this is how it goes from now on, I’m out. Is it really though? Are all businesses switching to vibe coding? Have some of you started switching career? I think I want to go to meatspace. Hand-made coding could make a cute hobby.

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

[–] eyesaremosaics@lemmy.zip 3 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

What are your thoughts for using AI to colour in & do the tedious bits? So you plan out the structure of what you're trying to do, work out the individual pieces and get the AI to do a bunch of the (well specified) leg work. I've found it fairly reliable like this, especially for things that involve looking up function parameters in unfamiliar APIs. But this does depend on a thorough look over what comes out as well. No doubt there's still issues that can pop up but generally have found it to be useful overall

[–] Feyd@programming.dev 11 points 2 weeks ago (1 children)

If the API is unfamiliar how do you know what it puts out is the best way to use the API without going and reading the docs anyway?

[–] eyesaremosaics@lemmy.zip 2 points 2 weeks ago* (last edited 2 weeks ago)

Sure if you need it to work with that level of detail/efficiency then you'll need to understand the code thoroughly as well. If you need it to draw a dashed line and you get a dashed line then that is fine by me. Looking up the argument differences between matplotlib plt.plot and plt.scatter for example can take quite a bit of time for fairly trivial things

[–] rozodru@piefed.world 3 points 2 weeks ago

Personally I don't allow the AI to write any code. I do use AI but I mainly use it for debugging and as a sort of glorified rubber duck that I can bounce problems off. check my code, see what's wrong with it, see what it recommends, and based on my own knowledge know the right direction to proceed. It still gets things wrong most of the time but at least it can point me down a path that I know will be the correct one.

I used to use it to craft boilerplates/bootstraps and at first it did it well enough but lately it even fucks that up. so I don't bother. I honestly don't even trust it to do the tedious writing. It's a useful idiot at this point.