As an industry, we keep treating software development as a technical problem. When systems become complex, we add frameworks. When code becomes hard to understand, we add documentation. When delivery slows down, we add tooling, automation, and now AI. And yet, we face the reality that many of our systems remain fragile, hard to change, and badly understood.

As AI increasingly takes over the act of writing code, a deeper question emerges: what is the value that humans still bring to building software systems? Our biggest challenges in software have never been purely technical. They are human. They live in the gap between what a system does and what it means. In the unspoken assumptions, shared context, domain knowledge, and lived experience that cannot be captured in code, diagrams, or documentation.

Already in the 1980s, researchers warned us: the theory of a system cannot be transferred through artifacts alone. Understanding emerges through collaboration. And yet, this industry keeps trying to externalize knowledge: more docs, more diagrams, more explicit models, and now AI assistants trained on past decisions. What we are really losing is tacit knowledge.

Explore how the loss of tacit knowledge, the stuff that lives in our heads, quietly shapes our architectures, our teams, and our organizations. Why adding more technology often increases complexity instead of reducing it. AI is not a threat, nor a silver bullet. It is a mirror: one that forces us to confront what only humans can do. Make meaning. Building shared understanding. Navigating ambiguity. Creating narratives that connect systems to the real world they serve.

This is a call to rebalance our industry, not away from technology, but toward the human skills that make technology sustainable. Because in the age of AI, the future of software is not about writing more code. It is about understanding more deeply.