Threading the Needle On GenAI and Developer Experience

Let’s face it: A lot of what developers do is routine. I’m pretty sure I’ve never heard a developer declare, “Hooray, I get to set up a SQL database!” (Well … maybe I’ve heard that once or twice — I know a lot of developers who are connoisseurs of sarcasm.)

However, when it comes to the trivia, the scaffolding, the mandatory “setting of values that should be defaults, but this library was written by idiots,” … developers hate that. They’d much rather solve interesting problems than bash their heads against a framework that’s broken but “the only one approved by legal.”

TuringBots to the rescue

The promise of TuringBots (generative AI [GenAI] that improves the software development lifecycle) is that they will take developers away from the trivia, letting them focus on the knotty problems that require creative solutions. So far, we’ve seen that with code completion and code explanation. We’re about to see GenAI solutions provide help with much more: determining what to work on next, identifying problems in the design, and even helping project managers understand when features will ship.

Most enterprises are still figuring things out

Organizations aren’t sure they’re seeing ROI yet. Many didn’t measure their developer productivity beforehand, so they can’t tell if it has changed. Most academic studies have measured productivity with toy problems (“build an http server”) or perceived productivity.

Many developers like having a GenAI assist, but there’s not a ton of proof that it makes things go faster. Confounding that, developers quickly see life with GenAI as the new normal. Story points get adjusted, and new deadlines are set with the expectation of GenAI help.

Introducing GenAI into a development organization can be a challenge. Moving from deterministic development to probabilistic development needs training — more than the half-hour course your company’s already done that says, “don’t put corporate data into public large language models.” Senior developers struggle to change long-established methods of working. Junior developers need more guidance: They’re taking on the code reviewer/debugger role without having written much.

Some organizations are overconfident — and will pay the price

Apart from the companies thinking about developer experience, some businesses hope they’ll soon be able to replace their costly developers with developer robots. I’m certain that some will. When you see that, run. They’re heading for cost overruns, maintenance nightmares, governance breakdowns, and vulnerabilities galore. GenAI makes it easy to create a lot of code that works most of the time. However, you still need experts to weed out the hallucinations.

The original article is here and was written with Caroline Bonde.

The views and opinions expressed in this article are those of the author and do not necessarily reflect those of CDOTrends. Image credit: iStockphoto/peterschreiber.media