In theory, a code change is the same whether it was written by a human or generated by AI. The diff may even be identical.

What is different is what the team learned while producing it.

When developers wrote each line themselves, they accumulated familiarity with the system. They made small architectural decisions, discussed alternatives, noticed inconsistencies, and gradually built a shared understanding of how the codebase worked.

AI can generate the same change without transferring that understanding to anyone.

This creates two risks. First, coding agents make small but consequential decisions that developers may never notice. Second, thousands of individually reasonable changes can gradually shift the architecture, conventions, and structure of the system.

In this session, I’ll demonstrate a system we built to surface hidden decisions during development and expose longer-term architectural drift. The goal is not to slow AI-assisted development down. It is to ensure that the team’s understanding can keep up with the code.

Target audience: Software engineers, architects, tech leads, platform teams, and engineering leaders adopting AI coding tools.
Level: Intermediate–advanced.
Preferred duration: 30–45 minutes.
Format: Experience report with system examples and a prototype demonstration.
Prerequisites: Familiarity with pull requests, software architecture, and AI-assisted coding.
Source: Lessons from AI-assisted development and building tooling to expose hidden decisions and codebase drift.