That's what is meant by human negligence. There will always be a hype about something and that is not an excuse to have a devil may care attitude on any work being done
Negligence depends on what you believe to be true. If you're being told "this is possible and the AI will do it properly you don't have to worry" then it's not negligence really - on the part of the person who believes what they are told.
For the rest of us it is about being put under pressure by managers who don't understand whether to believe what you say or what they read about vibe coding on some linked-in post. As far as they are concerned you're not the authority and some hype-ster is.
> "this is possible and the AI will do it properly you don't have to worry" then it's not negligence really
Then that's lack of due diligence and and any manager is forcing you to ignore that, you should report them to compliance team. You cannot blame everyone else and bear no responsibility for your actions. If you decide to vibe code blindly and ignore all the laws and standards, then that was your decision and you decided to turn a blind eye.
They watch your AI usage and pressure you to use more. They tell you that "of course you must check the code" but of course if you do then they can start telling you your performance isn't good enough. "Fred is much faster than you" and of course Fred says he checks everything but does he really? To do code reviews he just uses an AI anyhow so nobody catches what the AI doesn't catch. If you check his code carefully in a review and bring up a lot of questions (which he cannot answer because he doesn't know) then you're being "difficult" and dragging the team down.
Is this what I'm experiencing now? perhaps about 70% of it but I can see how it goes. There are lots of companies out there with poor development practices who think that AI will save them. They don't want to prioritise "quality" although they shout about this a lot. They think that somehow they don't deserve to have quality issues if they prioritise speed and features and don't bother to fix any problem until it causes downtime.
Please forgive my cynical view. I have simply had some bad experiences. It's not always easy to do what is right even when it's fully in the company's own best interest.
You do realize that bad management would still be bad management regardless of AI right? "Fred is much faster than you" has been used by management way before AI was there will aways be scenarios like that regardless of AI or any other tool or technology. Blaming bad management on advances on AI is quite naive and it actually doesn't achieve anything. If the management is the problem then you have to address that and fix that and AI has nothing to do it. Today the management would use AI as an excuse and tomorrow they would use the next hype word.
Oh definitely! :-) I just think it's like an amplification of the same old thing. It makes it easier to play that game and harder to counter it.
Fred now generates 5,000 lines of horse-dung that appears to work and management are gob-smacked. It is extremely fragile, has no security and the tests are all autogenerated so nobody knows if they're even testing what is actually important but...
Above the team-lead level, management, product manager etc have no idea what's inside a piece of work that makes it maintainable or secure or anything else and all they see is their idea realised and the person who did it has a golden halo so you cannot say a single negative thing about the work without a tonne of shit pouring on you.
This has happened to me. It was in the days when ChatGPT was much worse than it is now and the code was almost one big hallucination - indescribable how bad it was. The only advantage I had was that the whole team, other than Fred of course, rejected the PR. It caused a world of horrible problems though and incredible behavior from "Fred" and yet he was able to get away with it until he finally stepped so far over the line that nobody could support him. It caused other team members to leave though so it was a disaster.
Your case sounds pretty extreme, like a combination of multiple toxic factors and I still don't think it is due to AI. Fred still could have pushed bad code without the help of AI and the situation would be the same. In this case the problem is Fred, not AI. It's the human negligence of Fred that caused the issue. Even if you ban using AI in your company, still Fred would behave the same and find a different way to be toxic.
For the rest of us it is about being put under pressure by managers who don't understand whether to believe what you say or what they read about vibe coding on some linked-in post. As far as they are concerned you're not the authority and some hype-ster is.