Recently, I have been giving talks about testability, and good software practices at my friend’s companies. My goal, is to change the developer community one-developer-at-a-time. I want to get to a world, where when a new developer gets hired, the question of testing does not need to be asked. It is understood that as a developer your job is to write software, and unit-tests hand in hand, because it is more fun, faster, and produces a higher quality product. I want to get to this world through my blog, the talks, and general knowledge sharing.
I just wanted to share a letter from my friend about the experience we had at Loopt. Together we can change the community! If you would like me to come and speak at your company about unit-testing and get people motivated and educated don’t hesitate to ask. It will be my pleasure.
Hi Misko,I never got a chance to thank you for coming to Loopt. It has made a big difference here. People are excited to write unit tests and there are lots of discussions over tools, architecture, etc. That’s all I really wanted – to bring some more attention to the topic. As for me, then I’ve been using most of your techniques while writing code – however, I didn’t know the terminology and couldn’t really explain why I was doing things in certain ways – it was just the way it had to be in order to write unit tests Now that I know the official terms its much easier to identify place where I drifted away - and more importantly, refactor other peoples code to make it testable. I’ve only ever tried to write unit tests to code you write from scratch, and never really had to write the tests after the code was written. At least now I know exactly why large parts of our code is not testable and what we can do to make it better.So to answer your question from Facebook; My update was intentionally vague as I wanted a screenshot for the posting I just wrote to our blog: http://www.looptblog.com/2008/11/unit-test-tuesdays.htmlFeel free to reference itLater, Heine