Jon Fazzaro

Information & Communications Technology

Agile Coaching Extreme Programming Business Agility Zen

Jon Fazzaro

Software Craftsman/Full Stack Agile Coach/Advanced Beginner, probably off looking for a cup of coffee right now.

Jon took this whole nerd thing pro back at the turn of the century, and has been slinging code with Aptera since 2008. He holds an MCSD, a PSM, a PSD, a PSPO, and is a BMF besides. These days, he may or may not be unhealthily consumed with building sustainable software, and with building teams that build sustainable software. Whatever you do, don’t follow @jonfazzaro.


"Make him a permanent speaker every year. Seriously."

"Wow! Excellent. One of the best speakers embracing a change mindset."

"What you teach applies to everyone."

"Off the wall way to clearly say what I have experienced as a developer. I can use this for my developers on scrum team."

Current sessions

Oh! The *Humanity*

“Agile” is a bit lost.

Like a couch potato resolving to go to the gym in January, we threw off the chains of Scientific Management and declared a manifesto of people-centered values.

And here we are in our February, right back on the couch. We prescribe process and certification. We try to do *literally* Twice The Work In Half The Time™. And we wonder why middle management doesn’t want to pay for our membership anymore.

Agile was always about humanity. Messy, “unprofessional” humanity. But when it got tough, we ran right back into the arms of mechanics.

In this talk, I want to expose the relics of industrial thinking. I want to shine a light on the madness of trying to build the perfect machine out of people. And I want to get into some strategies for embracing our humanity at the organizational, team, and individual levels, so we can meet the work of the 21st century like only humans can.


Stuckness: Zen and the Art of Software Development

> Stuck. No answer. Honked. Kaput. It's a miserable experience emotionally. You're losing time. You're incompetent. You don't know what you're doing. You should be ashamed of yourself. You should take the machine to a real mechanic who knows how to figure these things out.

-- Robert Pirsig, *Zen and the Art of Motorcycle Maintenance*

Pirsig makes zero mention of software in his book. Yet he narrates the development experience tangibly--tell me you’ve never felt this way before.

Let's talk about why we get **stuck**, how it cows us into feeling like imposters, and what we can do to dispatch it more effectively (even to use it to our advantage) and make great software fast anyway.

Feedback from attendees:

"Make him a permanent speaker every year. Seriously."

"Mindblowing. I wasn't sure what to expect, but it did offer a different perspective."

"I really enjoyed this - I am not a developer but work with developer. What you teach applies to everyone."

"Off the wall way to clearly say what I have experienced as a developer. I can use this for my developers on scrum team."


We Don't Type for a Living: Plural Programming Practices for Productivity and Profit

"Why would I pay twice as much for two developers to do one thing? Get back to your desks!"

Pair programming is a preposterous idea. Until you see it work, and then it's not. In fact, pairing and mobbing are transformative techniques for building great software, and for building teams that build great software. And yes, Virginia, for going faster.

But we only get to cash in on that when we do it right.

So let's talk plural programming—I've been at it for years, and I'm in the mood to share. We'll turn over some pairing myths with data. We'll talk about how you don't need your boss's permission to do it. And we'll cover the pairing anti-patterns that can ruin it for everyone.