InfoQ Homepage Design Content on InfoQ
-
Balancing Coupling in Software Design with Vlad Khononov
In this episode, Thomas Betts speaks with Vlad Khononov about balancing coupling in software design, the subject of his recent book. They discuss how coupling is necessary for a system to function, but has to be balanced to allow the system to evolve. Vlad identifies three factors that can be used to measure coupling: knowledge sharing, distance, and volatility.
-
Understanding What Really Matters for Developer Productivity: a Conversation with Lizzie Matusov
In this podcast Michael Stiefel spoke with Lizzie Matusov about the dependency of effective, productive, and satisfied teams on good software architecture. Understanding this relationship requires understanding exactly what software productivity really is, how modern software engineering research has become more rigorous and practical, and how to apply that research to software development.
-
Object-Oriented UX (OOUX) with Sophia Prater
In this episode, Thomas Betts talks with Sophia Prater about Object-Oriented UX (OOUX). OOUX focuses on identifying the objects and relationships within a system, allowing for better communication and collaboration among designers, product owners, engineers, and architects. Prater explains the process of OOUX, which involves multiple rounds of discovery, requirements, prioritization, and revision.
-
Architecture Does Not Emerge - a Conversation with Tracy Bannon
In this podcast Michael Stiefel spoke to Tracy Bannon about what software architecture really is, and what an architect needs to be able to do. Bannon is a senior principal at MITRE. She sees herself as a passionate software architect and change agent who also puts out the Real Technologists podcast.
-
Neal Ford and Mark Richards - Software Architecture: the Hard Parts
In this episode of the InfoQ Podcast, co-host Thomas Betts spoke with Neal and Mark about the role of a software architect and the skills necessary to be successful. One of the hardest parts is recognizing that there are no right or wrong answers, or easy decisions, and this can be especially challenging for those who come from a programming background.