AI is making us write more code. That's the problem.

I analyzed research papers on AI-generated code quality. The findings:

→ 1.7x more issues than human-written code
→ 30-41% increase in technical debt
→ 39% increase in cognitive complexity
→ Initial speed gains disappear within a few months

We're building the wrong thing faster and calling it productivity.

The bottleneck was never writing code. It's understanding what to build.

If you're using AI coding tools, focus on:
• Smaller features (if it's 1000 lines, it's too big to review)
• Clear acceptance criteria before you prompt
• Tests first, AI-generated code second
• Security audits (AI can't do this)

More code isn't the goal. Solving real problems is.

@Mark Levison Right. it's getting hilarious, when you get AI to write code for audio coding applications. The machinery never understands, where you want to go, regardless of the detail you provide in your prompting. It's an endless back and forth, the code is often incorrect, and even more often not human readable or visible in applications, that have a procedural GUI. A complete time-waster actually.
Mark Levison (@[email protected])

7.26K Posts, 904 Following, 530 Followers · Certified Scrum Trainer | I help organizations and teams become more effective. I use #Scrum, #Kanban #Agile #BehaviouralPsychology. | I’ve helped over 8000 people build better teams I dabble with #PKM aka Personal Knowledgement Management so the ideas that fall out of my head get written down somewhere #Obsidian. #fedi22

Agile Alliance Mastodon
@jrp Interesting. I've never done Auido related development. I think i would fail harder than the GenAI tools.
@jrp @mlevison I had a student submit a vibe coded plugin that sounded correct, but wow, did it use a lot of system resources.

@celesteh

But those resources wanted to be consumed.

Debugging vibe code is entertaining.