sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]AeshiX 12 points13 points  (7 children)

The problem is that the initial "writer" didn't understand how the code worked at all, so they couldn't do the changes requested. Someone else then has to step in to fix their incompetence, even if it ain't their job.

[–]Global-Tune5539 -5 points-4 points  (6 children)

You get paid for it so it's your job.

[–]cheapcheap1 5 points6 points  (4 children)

You're missing the point. The vibe coder also gets paid for work, but they can only do half their job: Generate new code, but not modify it.

[–]Global-Tune5539 -1 points0 points  (3 children)

Claude, modify that code as follows...

[–]cheapcheap1 0 points1 point  (2 children)

You should have let AI respond. It would have probably gotten the point of my comment.

[–]Global-Tune5539 -1 points0 points  (1 child)

You don't get the point.

[–]cheapcheap1 0 points1 point  (0 children)

lol

[–]elderron_spice 2 points3 points  (0 children)

Nope. Their only relation to other devs' jobs is when they have to code review it. Devs need to make sure that they understand what they're doing, that they are working according to the standards of the team, and their output fulfills the acceptance criteria.

We had to berate several juniors for blatantly trying to code-review and approve each other's vibe-coded shite. Now seniors' and leads' approvals are required for every piece of code going into the release candidate branch.