Skip to Content

AI

AI coding tools and large language models (LLMs) can write code, explain it, and refactor it faster than any person. But writing code was never the hard part of maintenance. Someone still has to understand the system, decide what should change, and live with the result. AI changes how that work gets done. It does not remove the need for it.

Key Statistics

Why This Matters

AI makes new code cheap. That shifts the cost of software toward everything that comes after: reviewing it, testing it, understanding it six months later, and deciding whether it should exist at all. Teams that only measure how fast code gets written will miss where the real costs land.

Used well, AI is a strong maintenance tool. It can map an unfamiliar codebase, draft tests for code nobody wants to touch, and carry out large refactors one careful step at a time. Used carelessly, it produces more code than anyone can review and turns a legacy system into a bigger legacy system.

On the Maintainable Software Podcast, language creators, framework authors, and practitioners share how AI is changing their day-to-day work, and which old habits matter more now than ever.

Episodes on AI

Frequently Asked Questions

Does AI-generated code make software harder to maintain?

It can. AI makes it easy to add code faster than a team can review or understand it, and every line added is a line someone has to maintain. The risk is not the tool itself but skipping the review, tests, and design thinking that keep a codebase healthy. Teams that hold AI-written code to the same standards as human-written code avoid most of the problem.

How can AI help with legacy code?

AI is useful for reading code as much as writing it. It can summarize unfamiliar modules, trace how data moves through a system, draft characterization tests before a change, and carry out repetitive refactors across many files. The best results come from small, verifiable steps rather than asking a model to rewrite a system in one pass.

How do you test software that uses an LLM?

LLM-powered features can change behavior without a code change, so traditional pass/fail tests are not enough. Teams use evals: curated sets of inputs with expected qualities, scored automatically and tracked over time. Pair evals with production monitoring, and prefer the simplest model that does the job so there is less to go wrong.

Do frameworks and abstractions still matter if AI writes the code?

Several guests argue they matter more. Frameworks give both people and AI agents a shared set of conventions, which makes generated code more predictable and easier to review. Good documentation and clear error messages, long valued by developers, turn out to be just as valuable to coding agents.

Will AI replace software developers?

Our guests do not expect it to. AI handles more of the typing, but someone still has to understand what the software should do, judge whether a change is correct, and own the system over time. Those skills, especially understanding how software should behave, are becoming more valuable, not less.

Related Topics

Between the episodes

235 Episodes published since 2019

Stay sharp. Skip the noise.

One email when a new episode drops. That's it.

Joined by engineering leaders at companies you've heard of.