Software Architecture is about the important things, where “important” means high-risk and hard-to-change decisions. DevOps tries to develop a culture where constant experimentation and learning takes place while the environment changes rapidly. How can this fit together?
Blog iSAQB Software Architecture Gathering – Digital 2022 REGISTER NOW Gregor Hohpe Enterprise Strategist AWS Share on facebook Share on twitter Share on linkedin Share on xing Published on October 11, 2022 The Essence of Riding the Architect Elevator An interview with Gregor Hohpe by Richard Wallintin In anticipation of Gregor Hohpe’s keynote,
Software Architecture is about the important things, where “important” means high-risk and hard-to-change decisions. DevOps tries to develop a culture where constant experimentation and learning takes place while the environment changes rapidly. How can this fit together?
We have been building software systems for over sixty years, and they continue to grow in size and complexity. Many of them have become large obscure tangles of legacy code that drives up development costs. Is this inevitable? What can we do to get our Legacy in good shape and keep it that way?
We see a lot of confusion regarding architectural work these days. When? How much? Who? Tons of heated debates and nobody asking the essential question: Why? But without asking Why, all the other questions are futile. Thus, we will start this session by asking: *Why* do we need architectural work? And which problem(s) does it address?
Sponsoring a conference is a terrific way to support and connect with our global community of software architects.
