Abstract: Software is very much its own thing but we built our discipline in the presence of traditional engineering, where we concentrate on the qualities of what we are creating. We can measure coupling and cohesion in much the same way that an engineer might measure structural load and tensile strength.
In Agile, we’ve made development more human-centric. We’ve concentrated on ourselves at work and made software development much more dependable, but we seem to stop when we confront the code. We see it as the thing to be measured and assessed rather than measuring how, say, a bad class impacts us.
In this session, we will explore the idea that we can apply the same focus to issues of technical design and technical debt. Inspired by Janelle Klein’s book, Idea Flow, we will examine the dichotomy between artifact-focus and how work with artifacts impacts us, and consider what this could mean for the industry going forward.
Learning Outcomes: - Insights you have that others may be overlooking
- Insights others have that you may be overlooking
- Ways in which your insights and others’ can enhance each other
- Things you thought you knew, but there’s more to it than that
- New beginnings to explore this topic more deeply
