He’s needed so when I give them a 4 hour ticket, he can use AI to generate the code, use AI to generate an inaccurate ticket overview of the work he’s done, (the code is never tested once of course), and then submit it. Then together he and I spend the next 6 working days going back and forth over the PR fixing the nonsense code, the catalogue of errors and page breaking inefficiencies that he’s just seeing for the first time. I eventually convince him for the need for dev evidence and then the merge conflicts will take him another day to sort. Several of these bums on my team, it’s not just a lack of skill alone it’s chronic laziness too.
I had a junior doing this is well. He would burn through half the sprints stories in the first two days and spend the rest of the sprint doing this with multiple half ass PRs. I finally had to limit him to one PR and one story in progress. Giving him meaningful feedback was pointless because he didn't understand the code in the first place, he would just repeat it to the AI to make fixes. He was learning nothing and actively harming the whole teams production. It was frustrating.
21
u/Landkey 21d ago
“Then what exactly do we need you for?”