About

Why does an Enterprise Architect build software?

In my consulting practice, I audit IT landscapes and rationalize technology portfolios for large organizations. The greatest threat to enterprise agility today is architectural gridlock — application and data landscapes that are too fragmented to be maintained, too complex to be modernized, and too disjointed to adapt to fast-changing business environments.

I build software as architectural theses. SwarmCoder is the current one: an agentic coding system for organizations that need proper traceability on their software development — proof that AI can be brought into a delivery lifecycle safely, with mechanical governance and human guardrails, rather than thrown over the wall to an agent that reinvents its process on every run.

It also addresses an economic risk that is architectural in nature: frontier tokens are currently sold below cost. Organizations are building their delivery pipelines on that pricing as if it were permanent. When it corrects, the cost of building software becomes a number someone else sets — and by then the dependency is load-bearing. The architectural answer is to treat token economics as a design constraint now: SwarmCoder confines frontier spend to a few capped judgment calls and runs the volume on hardware you own, so the correction, whenever it comes, is mitigated as much as possible.

It is built on ZeroZ4j, my zero-impedance Java stack — from ZeroZ4j's side, SwarmCoder is its demonstration project. Both make the same point: whether at the software architecture level or the enterprise application level, the path forward is unifying and simplifying your architecture.