The InfoQ Podcast · 2026-06-01 · 42 min
In this podcast Michael Stiefel spoke to Sonya Natanzon about the intersection of technical and social aspects of software architecture. Understanding the business and how a company operates is more important than the specific technologies used. Effective requirements analysis requires focusing on problems to be solved that describe good and bad outcomes, rather than statements of need or solution statements. Embracing constraints enable architects to narrow down the available options, which makes designing the system architecture much easier. It is often better to use techniques from approaches like Domain-Driven Design or Event Storming without formally introducing the methodology to the team. This will increase their effectiveness by reducing people's natural resistance to formal methods. The future of training new engineers will come from their ability to explain and review code, and learning how to fix broken systems. Read a transcript of this interview: Newsletter:
Architectural Patterns: Moving Beyond Cloud-Native to Local-First - Insights from Adam Wiggins72 / 100
How eBPF Empowers Developers to Observe Inside the Linux Kernel in a Safe and Unintrusive Way
Increasing Users’ Data Agency: From BlueSky's AT Protocol to the Local-First Software Movement
From MCP and Vibe Coding to Harness Engineering: How Did AI Native Engineering Evolve in One Year
Chasing Efficient Java Development: From 1BRC to Developing Hardwood AI Natively