2026-09-03 –, Auditorium
We like to treat software architecture as a technical discipline, so when an architecture rots we go looking for technical causes. But every decayed system I've ever seen had a perfectly good plan behind it. The mess didn't come from the code. It came from how the people building it talked to each other, or stopped talking to each other. That's Conway's Law, and it just got a plot twist: a growing share of those conversations now happen with AI assistants instead of with teammates.
This talk follows one fictional organization across three eras of its life, on a single network graph of people, teams, services, and code that evolves on screen, to find out what all those private conversations are doing to your software.
The story follows one fictional organization, stitched together from things I lived through, across three eras of its life: the early monolith, the reorg into "autonomous teams" that nobody thought all the way through, and the arrival of LLM assistants. The whole arc plays out on a single network graph of people, teams, services, and code that evolves on screen as the company changes, so you can watch the architecture respond to the conversations, and stop responding when the conversations stop.
Along the way: how well-intentioned autonomy can manufacture a distributed monolith; what actually happens to a codebase when every developer's closest collaborator becomes a model; what the industry's own data says about feeling faster versus being faster; and why AI makes Conway's Law bite harder, not softer. And because this isn't a doom talk, the way out is here too, grounded in Diana Montalion's Learning Systems Thinking.
You'll leave with a new lens to view your own codebase, a sharper question to ask about every system your team ships, two gut checks for your team's AI adoption, and a handful of practices you can pilot without waiting for anyone to approve a reorg.
Software Architecture, Conway's Law, Systems Thinking, Socio-Technical Systems, AI-Assisted Development, Team Communication, Engineering Culture
I'm Juan Caraballo, an Infrastructure and Reliability Engineer from the Dominican Republic, currently based in Lisbon, Portugal.
I started my career as a Django developer at the Utah Water Research Laboratory, where I spent nearly a decade, before moving into data engineering and eventually infrastructure and site reliability.
Outside of work, I'm drawn to the connective tissue between fields like physics, biology, ecology, and computer science, and I try to bring that cross-disciplinary lens to the way I think about engineering problems.
