Programming

28548 readers

355 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 4 days ago by luciole@beehaw.org to c/programming@programming.dev

157 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

[–] timochka@lemmy.zip 1 points 2 days ago

There are two things we measure inadequately with junior/senior. There are people who are highly skilled and have aptitude and passion for engineering - they are junior for lack of experience, but will be senior in good time.

Then there are people who are simply shit, who probably call themselves "coders", who are proud of being self-taught by hacking out Javascript or got a vocational qualification from a Poly. They will remain junior forever (unless they work in outsourcing, in which case they'll be billed as senior devs if they can bluff their way through for 6 months.)

The latter are fucked, the former will be fine; I suspect we're going back to a world as it was 30 or 40 years ago though, where the quality of your degree is far more important and the number of vacancies far lower. I rather hope the death of outsourcing will also finally mean an end to the ridiculous job-title/expertise inflation that sector has wrought upon the industry.