Three Decades of Building Software

Mike Merchant has spent his career building software. A self-taught programmer from age 12, he studied computer science at Cal Poly Pomona and worked on enterprise systems at Southern California Edison and Kaiser Permanente before founding Codazen in 2007. Over nearly two decades leading Codazen, he and his teams delivered enterprise applications and global-scale websites; working through every dominant model of software delivery along the way, from Waterfall to Agile to scaled Agile inside large enterprises.

When the Old Models Started to Break

For years these processes worked, but the established approaches were built around fixed primitives that govern scope without being opinionated about workflow or quality. There was never a clear, shared standard for what made an epic or a story good. As AI coding agents matured, the cracks widened: teams could suddenly move far faster, but tools and the planning primitives beneath them were never designed for durable scope or memory; the persistent context that lets both people and agents do their best work.

The Watershed Moment

By December 2025, Codazen faced a pivotal moment. AI agents had become capable of writing production code as well as the team who had spent decades doing it. This forced a hard question about how Codazen needed to continue working, and what value it would continue to provide. Under this kind of acceleration, established processes were already straining. The choice was stark: move faster, or be left behind.

In this watershed moment, Merchant decided to start over with a blank slate. He set out to design a new way of working without the constraints of inherited terminology, ceremony, or tooling. The premise was simple: AI agents can help enormously, but only if they know the target. Without a clear destination, agents guess; and guessing is what teams can't afford. So he began defining new primitives built for durable scope and shared context: Codas, Beats, Beat Versions, Revisions, and the structured Notes that inform the context they are built off of.

From a Tool to a Methodology

The ideas first took shape as a tool, later named Harmonica. As the Codazen team used it to build software, including the tool itself, a methodology surfaced from the practice. They extracted and named it Harmonic Composition, using the tool to refine the method and the method to improve the tool — a virtuous cycle in which the system helped build itself.

The Coda Connection

The musical naming runs through everything here. Harmonic Methods treats software delivery the way music treats sound, as many independent parts brought into a coherent whole, then performed reliably, again and again.

The name Codazen shares that root. A coda is the passage that brings a piece of music to its resolution, taking all that came before and carrying it to an intentional close. It is a fitting word at the heart of a methodology built to bring work to a clear and reliable point of completion.

Harmonic Methods Today

Harmonic Composition is one of three frameworks under Harmonic Methods. Alongside it sit Harmonic Orchestration — coordinating human and AI agents to execute against shared context — and Harmonic Portfolio Management, mapping and arranging capabilities across the wider landscape. Together they form a connected approach to building software where intent is explicit, context is preserved, and teams plus agents stay aligned.