Arty Starr
Central Ohio Software Symposium
Columbus · Apr 29 - May 1, 2016
Developer Experience Researcher, University of Victoria
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.
Presentations
Let's Make the PAIN Visible!
We've got some seriously big problems in our industry. Under constant business pressure, our organization's drive one project after another into the ground. Once the chaos and fire-fighting finally gets out of control, we rewrite our software… again. How long are we going to wait for somebody else to solve this problem?!
It's about time we took responsibility. OpenDX is a strategy to kick this problem's ass. How? By measuring the pain, and putting the ridiculous costs and risks on center stage for everyone to see, then working together to figure it out.
Stop Getting Crushed By Business Pressure
This is my story of lessons learned on how to stop the crushing effects of business pressure… I was team lead with full control of our green-field project. After a year, we had continuous delivery, a beautiful clean code base, and worked directly with our customers to design the features. Then our company split in two, we were moved under different management, and I watched my project get crushed.
As a consultant, I saw the same pattern of relentless business pressure everywhere, driving one project after another into the ground. I made it my mission to help the development teams solve this problem. This is my story of lessons learned on how to transform an organization from the bottom up. I'll show you how to lead the way.
Top 5 Reasons Why Improvement Efforts Fail
This is my story of lessons learned on why improvement efforts fail… I had a great team. We were disciplined about best practices and spent tons of time on improvements. Then I watched my team slam into a brick wall. We brought down production three times in a row, then couldn’t ship again for a year.
Despite our best efforts with CI, unit testing, design reviews, and code reviews, we lost our ability to understand the system. We thought our problems were caused by technical debt building up in the code base, but we were wrong. We failed to improve, because we didn’t solve the right problems. Eventually, we turned our project around, but with a lot of tough lessons along the way.