Michael went from being one of my heros to being someone I respected as having a similar pragmatic testing and software development philosophy as myself. I wish I had been able to talk with him more than I did. But I’m grateful for the time I did get to talk with him.
I don’t know why I feel the need to write down this timeline of my interactions with Michael Foord. But I do. So here it is.
2012 - I start blogging about Software testing in Python. Someone tells me I gotta get my site listed on Planet Python, so I reach out and ask. It’s Michael Foord that replies with a “I’ve added your feed to the Planet Python. It will show up shortly.”
2013 and later - The more I write and research testing with Python, the more Michael Foord’s name shows up. He’s been involved with the unittest core library. He’s the original author of the Mock library, that gets pulled into core as unittest.mock. He’s involved with the Testing in Python mailing list. He’s been a part of the Testing BoF (Birds of a Feather) meetings at PyCon.
2015 - I start Test & Code podcast
2016 - I ask Michael Foord to be a guest on the show. He was working with Go at the time and recommended I reach out to Robert Collins, the maintainer of unittest at the time. I do, and Robert’s interview is episode 19
2017 - Michael writes “30 best practices for software development and testing”
2018 (I think) - The first time I see Michael Foord in person. I’m walking down a hallway at PyCon in Cleveland and I see him walking in a long black coat, a black hat, and goggles on the hat. He looks like he just came from a steam punk conference or something. Hey may have. I see he’s talking with a bunch of people and honestly, I’m too star struck to say hi. At least, that’s how I remember it.
2018 - I find the “30 best practices” artcile and love it, and think "here’s my opportunity to ask him on the show again. So I do. I ask Michael to come on the show to discuss the article, and he says yes. Yay!. However, scheduling conflicts on both his and my part push the interview to 2019.
2019 - We end up recording an interview at PyCon. However, it didn’t go well. I had a portable recording set up with a travel recorder and a couple of mics. I’d like to blame the equipment, but honestly, I don’t do very many in person interviews and also I’m still kinda freaking out that I’m talking to the Michael Foord in person and really the recording ends up sucking. I wonder if I still have the raw audio lying around somewhere. I’ll have to look. Anyway, I fess up to Michael that I don’t have enough usable audio and he agrees to reschedule.
2021 - We finally get an interview done and released. This is 5 years after I first tried to talk with him. But it ends up being a great talk. This is Test & Code episode 145, titled “For those about to mock”. At the end of the interview, I allude to us talking again. I really thought we would.
I’m very grateful that I did finally get an interview with Michael Foord done. Through his writing and though talking with him, I’ve learned a lot. He helped shape my ideas around software development and testing.
I’m grateful our paths crossed. I will miss him.