Study: Generative AI Is Eroding the Development Pathway for Software Developers

cross-posted from: https://piefed.world/c/tech/p/1394707/study-reveals-how-generative-ai-is-eroding-the-development-pathway-for-software-develope

In-depth interviews with 14 junior and senior developers in Korea reveal four structural changes

eng.snu.ac.kr/en/communication/promotion/news?md=v&bbsidx=8355

After a lengthy argument with my boss, I was allowed to “only” force the AI-first model onto half of my small dev team of 8 engineers and 4 QAs. After about a year, the results are obvious: the engineers who went AI-first are now AI-fluent: they know how to prompt the model, develop agents, AI-automate workflows, and push a TON of code. Like almost an order of magnitude more code into prod. However, to say their skills have stagnated would be generous. In some cases an engineer I could count on to debug a tricky issue is completely not able to anymore. Meanwhile, the non-AI team is now essentially my code quality and bugfix team. Their PRs are small and concise, their changes are understandable, and most importantly, their skills have remained the same (and in the case of the 2 juniors, have improved).

If we hadn’t kept a few people in reserve, we’d be fucked, because there have been multiple times where an AI-first engineer has tried debugging an issue (and with big models - Astra, Fable, Opus) that either totally failed and gave up, or made things worse by introducing “fixes” that made problems elsewhere.

So this is a small sample, and YMMV, but for junior engineers in particular (who usually have the least amount of say in pushing back against bad ideas) this is – not “is going to be” – a major problem.