About this Case Study
This session enables participants to appreciate how different tensions and ways to resolve them manifest at different scales, and by so doing, gain an understanding of the often fractal nature of the problems we face.
It draws on examples from concerns in software architecture and translates these into the process and collaborative domains.
Many of the forces that come into play building a (micro) service-oriented system are also present within larger systems, but are often obscured by our inability to recognise the patterns and listen to the weak signals.
From a people and processes perspective, we can see how minor problems (small enough to ignore) in the small team become major pain-points when we scale up.
Ramifications of a layered perspective:
- examining higher-level solutions can guide and alert us about what's problematic but unseen in the small
- selective experimentation at the foundation level and using that to predict how the large might behave
- developing these capabilities allows us to pick solutions because they solve tensions rather than adopting products or frameworks blindly
Learning outcomes - you will understand:
- how to improve quality at the unit code level and reduce technical debt by looking at larger-scale patterns and architecture
- how experimenting at the foundation level can help us avoid costly mistakes in the broader systems design
- an appreciation of the fractality of IT work and the benefits of a layered perspective
About the Speaker
Tobbe is an organisational debugger, developer, architect, hugger and collector of ideas. He has a deep belief in the untapped potential of folks and the power of mutually meeting needs to improve the way work works.
He's currently serving as the CTO of Nepa.