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

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

Don’t just let the AI code - actively question its architectural choices, hold it accountable to existing designs, and challenge unnecessary complexity.

I just wrapped up a 3 hour coding session. I instructed the agent to break the work into planned steps and test drive each step. When it had completed a tested increment, we proceeded to the next. This resulted in 27 separate commits.

Even still, I made at least eight direct interventions where I stopped the agent as it generated code with questions like:

• “Why mock file operations in integration tests? Use temp directories instead”

• “We already built those convenience methods - what did we miss?”

• “Why mocks over dependency injection?”

• “Do your changes actually match the schema?”

The result was a cleaner architecture with dependency injection. Integration tests using actual file operations vs mocks. Schema compliance verified at each step. Code using existing design patterns instead of reinventing the wheel.

The most valuable interventions weren’t about syntax or bugs - they are architectural challenges that prevent technical debt and follow established patterns.

#SoftwareDevelopment #AI #CodeReview #CleanCode #TechnicalLeadership