Arty Starr
Greater Atlanta Software Symposium
Atlanta · September 18 - 20, 2015
Author of Idea Flow, Founder, FlowInsight
Arty Starr is a recognized Flow Experience expert, researcher, speaker and thought leader, and author of Idea Flow, how to measure the friction in software development. Arty's PhD research is developing a theory of momentum in software development, and she is creator of the FLOWS platform designed to help developers thrive and find joy through more time in the flow state. The company she founded, FlowInsight, is on a mission to bring back joy to our everyday work.
Arty is also a 2D/3D animator and artist, and has spent the last couple years building 3D apps in AR. She loves to share about her experiences with these technologies.
Presentations
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.
How to Break the Software Rewrite Cycle
Despite our best efforts with Agile best practices – CI, unit testing, design reviews, code reviews – every few years we end up rewriting our software.
This talk is about my personal experiences with project failure, improvement failure, patterns across the industry, and the key lessons that were critical to success. I had a great team. We were disciplined with best practices and spent tons of time working on improvements. Yet still, I watched my team slam into a brick wall. We brought down production three times in a row, then couldn't ship again for another year.
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.