Based on years of research studies, modern psychological science, and original empirical data from over 5000+ real people's voices and experiences, I'm writing a book about what developers and their leaders can learn from the social and evidence science of developer teams.

Why this? 

It's never been more important to understand what really helps software teams thrive -- and it's never been more clear that most engineering organizations aren't evidence-driven. Our world runs on code, but many of us never think about who is creating that code and under what circumstances. Developers are suffering, and so is the innovation in technology. 

Good problem-solving environments for innovation will determine what we can solve now and in the future, and that starts with using good social and evidence science to support our teams. Plus...developers deserve science. 

Why me? 

I have a uniquely empathic and data-driven point of view on this topic. Having worked my own way out from a childhood with little access to technology all the way to some of the most elite educational and technology organizations in the world, I understand the resilience that drives innovation. I've been spending fifteen years working on how we can better understand how teams and communities form and fall apart, and how meaningful measurement can change which path we take. I know what it's like to be mismeasured, and I also know what it takes to transform people and places with evidence-based practices that sustain real, authentic human wellbeing and innovation. Plus...how many software orgs have you ever worked in that had a psychologist on staff? This book will give you one.

Also yeah my grandpa really did always ask when I was going to write a book. Wish you could see it. Know you'd love it.