What if we could measure the indirect costs of pain building up on a software project? What if we could measure the effects of learning curves, collaboration pain, and problems building up in the code?
With visibility we can:
We've been trying to explain the problems of Technical Debt for generations, but we've never been able to measure it. By measuring the “friction” in a developer's “Idea Flow”, we can see the effects of disruptions, test maintenance, confusing code, unfamiliar code, and collaboration problems. They all have a direct impact on developer experience.
In this talk, we'll discuss what is “Idea Flow”, how we can measure it, then we'll talk through the implications for our teams, our organizations, and our industry.
Arty Starr has been a software engineer for 20+ years and is a researcher and pioneer of new theories of the developer's cognitive experience that help us recognize how developers' experiences are changing with AI. Her theories of developer momentum and troubleshooting help us see software development through an ecological lens, recognizing it as a living activity in motion and the living capacities of care and cognition that support this motion. Her aim is to bring heart, human-centric values, and agency to the craft of software development so we can build toward the type of world we want to live in. With richer perception and by recognizing what matters, we can light a path to a future of thriving habitats where humans and AI can collaborate well and thrive together.
Arty is the author of Idea Flow, a speaker, thought leader, and artist who loves mixing ideas across disciplines into a fusion of creativity to help make the world a better place through her projects.