Right, which basically means that judgment compounds. AI just makes the slope steeper in both directions.

Maybe I'm being defensive, but the problem with this chart is it assume a binary of good dev/bad dev; AI makes the bad dev worse and the good dev better.

However, I think I once was a pretty good dev, and AI use is slowly turning me into a slop cannon. The temptation to use AI in place of real understanding is too strong.

I'm sure you'll say I was always dead weight, but I just want you to consider the possibility that AI might erode the capacity for good devs to handle discomfort, turning them into bad devs.

I wonder how much of the turbo brain developers time is spent on reviewing the code of slop cannons and how frustrated they must feel.

Previously, everyone was limited in their blast radius but now AI has levelled the playing field where even a single slop cannon be the bottleneck of PR reviews or even the company itself if not right now, then later, as the codebase turns sloppified which will have its ramifications later on.

Everyone might suggest with the diagram to be the turbo brains but I believe that we also need to reduce the metrics that slop cannon is achieving (surprisingly LOC which is a pretty bad indicator) and to be more reasonable throughout in realizing such bottlenecks and to follow good security practices throughout.

What a smug, dickish way to try to make a point. (But he’s still on Twitter, so I guess that makes sense.)