Why SW Architecture is Mostly Communication • David Whitney, Ian Cooper & Hannes Lowette • GOTO 2025

Why SW Architecture is Mostly Communication • David Whitney, Ian Cooper & Hannes Lowette • GOTO 2025

by GOTO Conferences

Applied Sciences & Engineering Computing & Cybersecurity UMComputer programmingUMZSoftware Engineering
🎙 GOTO Conferences 👥 1.1M 📅 September 29, 2025 ⏱ 55 min 👁 3K 📄 expert opinion 🧭 2026-08-03
Available in: English (current) Français

Keywords

architecturecommunicationemergent designsustainable architectureorganizational scaling

Summary

In this GOTO Unscripted interview, David Whitney, Ian Cooper, and Hannes Lowette discuss the evolving role of software architecture and architects. They begin by defining software architecture, referencing Grady Booch’s definition that all software engineers do design, and that architecturally significant decisions are those with high cost of change or impact on reasoning about the system. They contrast emergent architecture with deliberate design, using metaphors like London vs. New York to illustrate organic vs. planned growth. The conversation introduces the concept of sustainable vs. slash-and-burn architecture, where sustainable architecture requires continuous reinvestment in design to adapt to business changes, while slash-and-burn leads to eventual rewrites. The role of the modern architect is described as an executive producer, focusing on coaching, communication, and helping teams avoid design dead ends. They discuss the importance of language and communication in architecture, emphasizing that architecture is mostly about communication. The discussion covers scaling architecture with organizational growth, decision-making processes like advice forums, and balancing standards with team autonomy. They critique pattern cargo-culting and advocate for design wisdom over rote application of patterns. The conversation concludes with the transition to leadership and coaching, reiterating that communication is key in architecture.

195 words

Critical Evaluation

The discussion provides valuable insights into the practical realities of software architecture, drawing on the extensive experience of the three participants. The strength of the content lies in its nuanced exploration of the tension between emergent and deliberate design, and the emphasis on communication and coaching as core architectural activities. The speakers articulate complex ideas clearly, using relatable metaphors (farming, cities, archaeology) that make the content accessible without oversimplifying. The argumentation is generally solid, grounded in real-world examples and references to established concepts like Grady Booch’s definition and ATAM. However, the discussion is largely opinion-based, lacking empirical evidence or formal citations, which limits its scientific rigor. The references provided are mostly personal profiles and links to related talks, not primary research. The adéquation between title and content is strong, as the conversation consistently returns to the theme of communication. The speakers also touch on important topics such as sustainable architecture and the dangers of pattern cargo-culting, offering practical advice for architects. While the discussion is insightful, it would benefit from more concrete examples and data to support its claims. Overall, the content is valuable for practitioners seeking to understand the human and organizational aspects of architecture, but it should be complemented with more rigorous sources for academic or research purposes.

210 words

Title / Content Match

The title accurately reflects the central theme: the importance of communication in software architecture, as emphasized throughout the discussion.

Quality & Reliability

8/10

The discussion features three experienced software architects with substantial industry credibility. They reference established concepts (Grady Booch's definition, ATAM, Barry O'Reilly's work) and practical experience, but the conversation is largely opinion-based without empirical data or formal citations. The sources provided are mostly personal profiles and links to related talks, not peer-reviewed research.

Chapters

Cited Sources

  • David Whitney's Blog — David's personal blog, likely containing further writings on architecture and software engineering.
  • Ian Cooper's Blog — Ian's personal blog, where he shares his thoughts on software architecture and engineering.
  • GOTO Unscripted Article — The article associated with this interview, possibly providing additional context or a written summary.
  • The Architect's Paradox — A book referenced in the description, likely discussing the challenges of software architecture.
  • Residuality — A book referenced in the description, possibly related to Barry O'Reilly's work on stress-based design.

Concurring Sources

  • GOTO Unscripted Article — The article associated with this interview, likely providing additional context or a written summary.

External References

Contribution & Novelties

The interview offers a fresh perspective on software architecture by emphasizing the human and communicative aspects over purely technical ones. It introduces the concept of sustainable vs. slash-and-burn architecture, providing a useful framework for thinking about long-term system evolution. The discussion also highlights the importance of coaching and communication in the architect’s role, which is often underrepresented in technical literature.

Pour aller plus loin :

132 words

Radar Profile

The radar profile shows high scores in quantity and quality of information, with moderate technical depth and reliability. This indicates a content-rich discussion that is well-articulated but relies on expert opinion rather than empirical evidence.

Reliability 7/10