How do the colleagues of people "vibe-coding" feel about that?

Does it end up like having colleagues who are aren't doing or understanding or learning from their own work, and are working like they offshored their job to an overnight team of juniors, and then just try to patch up the poor quality, before doing a pull request and calling their sprint done?

Or is it more like competent mechanical grunt work (e.g., "make a customer contact app with a Web form with these fields, which adds a row to the database"), that was always grunt work, and it's pretty hard to mess up, and nothing that normally the person you assigned it to would understand further anyway by doing it themself?

random example, may or may not come from a real situation that just happened:

    - other team opens jira ticket requesting a new type of encabulator
    - random guy who doesn't know anything of how the current encabulator system works picks up the ticket for whatever reason
    - 10 minutes later opens a 2000 line vibe coded pr with the new encabulator type and plenty of unit tests
    - assigns ticket to the person who designed the current encabulator system for review
    - encabulator system designer finds out about this ticket for the first time this way
    - "wait wtf what is this?  why are we doing any of this?  the current system is completely generic and it takes arbitrary parameters?"
    - waste an hour talking to the guy and to the team that requested this
    - explain they could just use the parameters, close pr and ticket

> working like they offshored their job to an overnight team of juniors

Reviewing a co-worker of 13 years now gives me the exact same unpleasant feeling as opening an MR from a junior where I know it's going to be garbage and I'm tired of struggling to let them down easy.

Patch up?

Had our junior dev working on a case actually ran the code in the merge request and looked at the result, it would have been obviously broken and unusable. Like not even wrong value, it would have spewed a bunch of HTML into the page.

> Does it end up like having colleagues who are aren't doing or understanding or learning from their own work, and are working like they offshored their job to an overnight team of juniors, and then just try to patch up the poor quality, before doing a pull request and calling their sprint done?

yes