AI Coding

Cognitive offloading is delegating to the AI and still owning the answer. Cognitive surrender is when the AI’s output quietly becomes your output and there is nothing you feel is left to check. For software engineers the line between the two moves under your feet most days, and most of us are crossing it without noticing.

There’s a specific code smell that shows up in AI-generated code, and once you see it you can’t un-see it: primitive obsession all the way down to the domain core. string for emails. string for IDs. Map<string, any> whenever the situation gets hairy. Working code, passing tests, ships fine. And yet a developer who’d actually thought about the domain would not have written a single one of those types that way.

An analogy came to my mind this winter: vibecoding is fast food. You can cook at home (write the code yourself), you can go to a good restaurant (hire a programmer), or you can buy yourself a hamburger (use AI tools).

Over the past 16 months, DX has been running a longitudinal study on AI’s impact on engineering velocity across a sample of more than 400 engineering organizations. We found that as AI tool usage increased by an average of 65%, median PR throughput increased by just under 8%. Most organizations are landing in the 5–15% range—a meaningful gain, but far below the 3x or 10x expectations many leaders are being held to.

cross-posted from: https://lemmy.bestiver.se/post/1070522

Comments

cross-posted from: https://lemmy.bestiver.se/post/1068766

Comments