Architecture is a Conversation, Not a Diagram
Five things our industry treats as truth about software architecture. None of them hold up. UML was a vendor interop play from 1994, not a communication tool. Architecture is not an artifact. It is an understanding that lives in conversation. Natural language is the only notation everyone in the room already compiles. I spent twenty-five years doing architecture. I was a student volunteer at OOPSLA 1998. I published a design pattern at EuroPLoP 1999. I believed the box-and-arrow gospel for two decades. Then I went back and read what Christopher Alexander, Peter Naur, Alan Kay, Martin Fowler, and Rich Hickey actually wrote. What I found was uncomfortable: we kept the notation and abandoned the meaning. This talk takes five beliefs most teams treat as architectural truth and pulls them apart. That architecture requires formal notation. That it is a visual discipline. That the architect's job is to produce artifacts. That decisions should be made upfront. That documentation solves the knowledge problem. I show what the giants actually said, what I built to test the idea (a small experiment called ConvArch), and what it taught me about feedback loops in architecture. I will also be honest about the limits of my own argument. Conversation without verification is just a nicer way to be wrong together. Five people confidently agreeing in a room is still a confident guess.
- Architecture
Foredragsholder
Marco Nissen
Senior Software Developer, Telenor · Author of "Code Different"
Marco Nissen is a senior software developer at Telenor in Trondheim, after 25 years of building software and architecture across Germany, Canada, the UK and Norway, most recently as an architect at Lyse. He was a student volunteer at OOPSLA in 1998, published a design pattern at EuroPLoP in 1999, and has been questioning the notation ever since. Founder of Stash2Go (100k+ users). Author of "Code Different" on LinkedIn. MSc Computer Science (Saarland / Max Planck Institute), MBA (Europa-Institut).