Comment Consistent with my observations.. (Score 2) 33
Management has been pretty adamant that we are at the point where a developer should *never* look at source code, and work purely on prose. So some dutiful people have taken it to that extreme.
So they tell me they spend hours in planning, reviewing the resultant generated plan to give themselves confidence that the resultant code should make sense, then let it chew on making test cases, making code, running the tests, deciding whether the test cases were bad or the code was bad when failures happen, repeating until it has satisfied itself and then it lands in the builds that the still-human QA get a pass at. Then the human QA person often basically says "WTF, this is broken as hell" and the developer starts over incorporating the feedback from the tester into the flow.
Now the folks that discard that mandate and use CodeGen for code completion, more curated prompting, they get respectable speedups, but no hope for management to just toss those long term if they still need to curate the CodeGen. So management *really* wants the narative to work for the case above. They have raised the question if the real problem is the human QA, it passes all the CodeGen test cases and it's own code review, so maybe the human QA is just raising a stink to look relevant... Doesn't help that management understands neither the customer, software, or how to develop code, so they base things largely on wishful thinking on what the cheapest and most convenient answer would be that supports them getting big bonuses.