“Like with all things agile, we’re looking for a feedback loop, and we’re looking to make that feedback loop smaller.” That’s how Jon Fazzaro, a Software Architect with an avid devotion to craftsmanship, describes the rationale behind Test-Driven Development. Over the past handful of years, Jon has been instrumental in introducing agile principles and practices to Aptera’s custom development practice. And TDD plays a key role in our processes.
“Test-Driven Development,” he explains, “is a way of developing software where you are using code to write tests that verify that your code works. That sounds nutty until you’ve done it.” Now that Jon and the other members of the software team have done a lot of it, they’ve embraced it as the most reliable way to write clean, stable code.
In this week’s episode, James and I talk to Jon about what TDD is, how it works, why it’s important, and how he came to not only embrace it but advocate for it.
How TDD can help you become an emotionally whole developer
Jon’s knowledge about agile software development is as deep as his commitment to passing on what he’s learned. At first, you may not consider software craftsmanship the most exciting of topics, but listen in and you’ll get a sense of why so many of us have come to be completely fascinated by it.
I'm Aptera's Content Strategist. I've been writing about tech and marketing for 5 years and have certifications from HubSpot and The Content Marketing Institute. A big science and literature geek, I taught college rhetoric and composition while I was still busy going to school for way too long, earning bachelor's degrees in anthropology and psychology, along with a master's in British and American literature. Look me up on LinkedIn.