Menu

1 / 4

Measuring AI’s Unintended Consequences

Radar·James Shore·4 days ago
#OK16H7Bd
Reading 0:00
15s threshold

The following article was originally published on James Shore’s Successful Software blog and is being republished here with the author’s permission.

AI is great for making teams faster. But is it sustainable? What about maintainability, burnout, and lock-in?

This is part 3 of my series on assessing AI’s impact on software development. In part 1 , we looked at why assessing impact is important, and what not to do. In part 2 , we looked at how to measure AI’s impact on delivery speed. In this part, we’re looking at how to measure and model the unintended consequences of using AI. Then we’ll wrap up in part 4 with an examination of business outcomes. Finally, an epilogue puts it all together with notes you can share with your CFO.

Does maintainability even matter?

I can hear it now: “Who cares about namby-pamby issues like maintainability and burnout? It’s a job.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.