Test-Driven iOS Development

I took this knowledge with me to my first programming gig, as software engineer working on the Mac port of a cross-platform security product. (Another simplification— I had, a few years earlier, taken on a six-week paid project to write a LISP program. We’ve all done things we’re not proud of.) While I was working this job, I went on a TDD training course, run by object-oriented programming conference stalwart Kevlin Henney, editor of 97 Things Every Programmer Should Know, among other things. It was here that I finally realized that the point of test-driven development was to make me more confident about my code, and more confident about changing my code as I learned more.The time had finally arrived where I understood TDD enough that I could start learning from my own mistakes, make it a regular part of my toolbox, and work out what worked for me and what didn’t. After a few years of that, I was in a position where I could say yes to Chuck’s request to give the talk.