Reassessing AI's Impact on Development

Reassessing AI's Impact on Development
Ken Judy
Ken Judy
Originally: Aug 26, 2025 | Enhanced: Oct 28, 2025
1 min read
Technology AIcodingTechnicalDebtSoftwareDevelopmentAgileAllianceProductivity

Reassessing AI's Impact on Development

1 Technology Post AIcoding, TechnicalDebt, SoftwareDevelopment, AgileAlliance, Productivity Aug 26, 2025 1756252800000

We’re letting hype and economic pressures compromise our professional integrity

Current research reveals that while developers feel more productive with AI tools, the data doesn’t back that up.

  • 10x increase in duplicated code blocks in 2024
  • Copy/pasted lines now exceed moved/refactored lines for the first time ever
  • Every 25% increase in AI adoption = 7.2% decrease in delivery stability

We’re not just accumulating technical debt, we’re doing it at unprecedented scale while burning through massive computational resources at temporarily subsidized prices.

The solution isn’t sharing the industries blind faith that AI will do our jobs for us or letting our bosses tell us to just shut up and use the tools. We need to wrangle our AI practices using the disciplined approaches we already know work.

I’m proposing a human-supervised PDCA framework that might help us take more control of the technical debt generator.

Can we turn this crisis into an opportunity?

#AgileAlliance #AIcoding #TechnicalDebt #SoftwareDevelopment

Originally published on LinkedIn on Aug 26, 2025. Enhanced for this site with expanded insights and additional resources.

← Back to Articles and Posts

Related Content

Illusions of AI Code Generation Productivity
analytics emblem

Illusions of AI Code Generation Productivity

Your team’s AI code generation productivity gains may be an illusion.

Industry studies show perceived gains with code generation can result in a net slowdown in delivery. I’ve built GitHub Actions that measure five key metrics:

🔍 Large Commit Percentage (Target: <20%, Found: 46%)   🔍 Sprawling Commit Percentage (Target: <10%, Found: 20%)   🔍 Test-First Discipline Rate (Found: 58% - Good given refactoring)   🔍 Average Files Changed per Commit (Target: <5, Found: 6.4)   🔍 Average Lines Changed per Commit (Target: <100, Found: 9,053!!)

The article explains the metrics, shows results from my project, and links to GitHub action code.

#AI #SoftwareDevelopment #TechnicalDebt #EngineeringLeadership #CodeQuality

Technology AISoftwareDevelopment
1 min read Read Full Post →
innovation emblem

Insights on Using Anthropic Claude Models

Using Anthropic Claude models for coding:

Opus is strong on analysis. Industry benchmarks show it’s strong at coding, but I find it ambitious and rangy. It drifts beyond its mission when struggling, and will charge down supposition paths without grounding.

Sonnet is good at tasking out work and quite good at following through on well-defined tasks, but can be short-sighted in terms of pattern and method reuse.

The current version of Haiku falls short. It shows its age with anti-patterns like aggressively duplicating code and hardcoding values, particularly when spins on a task.

So, for now, I live in Sonnet. I use Opus mostly for analysis on big problems. I’ve stopped trying to use Haiku for now. Would love to hear from someone who is getting decent results in complex code with one of the smaller models.

Technology AICoding
1 min read
analytics emblem

Analyzing My AI Development Patterns

Most teams have zero visibility into their actual AI development patterns.

My AI development patterns over 30 days:

📊 50 commits analyzed across 4 feature branches 🚨 46% were over 100 lines changed or added 📁 20% of commits were across 5+ files 🧪 58% contained changes to both test and code files

Even with a disciplined practice, I need to reduce the batch sizes of my code changes.

How to measure yours: https://lnkd.in/d9FnkqhU

#AI #SoftwareDevelopment #CodeQuality

Technology AISoftwareDevelopment
1 min read