Building Software That Survives • Michael Nygard & Charles Humble • GOTO 2025
Keywords
Summary
132 words
Critical Evaluation
The interview provides valuable insights into software architecture and organizational dynamics from a seasoned practitioner. Michael Nygard’s experience at Sabre and Nubank offers concrete examples of how legacy systems and technical debt accumulate, and the practical challenges of modernization. His discussion of centralization versus autonomy is particularly nuanced, correctly pointing out that these are not opposite ends of a single spectrum but rather dimensions that vary by activity. This perspective is a useful corrective to simplistic debates on the topic. The explanation of Conway’s Law is accurate and well-illustrated, showing how communication structures shape system design. The conversation is grounded in real-world experience, lending credibility to the claims. However, the content is largely anecdotal and lacks empirical evidence or formal citations. While Nygard is an authoritative figure, the interview does not provide a systematic review of literature or data. The discussion is accessible but assumes some familiarity with software engineering concepts. The title accurately reflects the content, and the interview stays on topic. Overall, it is a high-quality expert opinion piece that offers practical wisdom, though it is not a rigorous scientific analysis.
183 words
Title / Content Match
The title accurately reflects the core theme of building resilient software and the discussion on architecture, autonomy, and alignment.
Quality & Reliability
8/10
The interview features Michael Nygard, a recognized expert in software architecture and resilience, sharing insights from his extensive experience at Sabre and Nubank. The discussion is grounded in practical examples and references to established concepts like Conway's Law and technical debt. While the content is largely anecdotal and based on personal experience, the speaker's authority and the coherence of the arguments lend credibility. The lack of formal citations or empirical data slightly reduces the score.
Chapters
Cited Sources
- Michael Nygard's website — Author's personal site with resources and articles.
- Charles Humble on Bluesky — Co-host's social media profile.
- GOTO Conferences on Bluesky — Conference organizer's social media profile.
- Conissaunce — Charles Humble's consulting and content site.
- GOTO Unscripted article — Full transcription of this interview.
- GOTO Newsletter — Newsletter for GOTO content.
- Charles Humble on LinkedIn — Co-host's professional profile.
- Charles Humble on Mastodon — Co-host's social media profile.
- Professional Skills Shortcut — Resource mentioned by Charles Humble.
- GOTO on LinkedIn — Conference organizer's LinkedIn page.
- Michael Nygard on LinkedIn — Guest's professional profile.
- GOTO Conferences YouTube — Channel subscription link.
Concurring Sources
- Conway's Law — The interview discusses Conway's Law, which is a well-known concept in software engineering.
- Technical Debt — The interview frequently mentions technical debt and its impact on legacy systems.
External References
Contribution & Novelties
The interview offers a nuanced perspective on centralization vs. autonomy, emphasizing that these are not binary but activity-specific. It also provides practical insights into modernizing legacy systems and applying Conway’s Law to reduce organizational friction.
Pour aller plus loin :
- Conway’s Law — The principle that organizations design systems that mirror their communication structures.
- Technical debt — The concept of accumulated cost from shortcuts in software development.
- Release It! — Michael Nygard’s book on building resilient software.
77 words
Radar Profile
The radar chart shows a balanced profile with high scores in quality and reliability, reflecting the expert's credibility and practical insights. The quantity of information is moderate, and the technical level is appropriate for a professional audience.