CONNECT
009 Introducing the Test Driven Development series
Today is the future. [echo, jetsons sounds or future sounding music] The world has been marching forward but still there are no flying cars. [whawha wha..] Well, there are flying cars but none mass produced. Why not? Are We developers and we managers part of the reason why we still don’t have such nice things? Is the low quality track record of IT to blame? Must we be used getting patches, and upon installation, hoping this new version doesn’t make things worse?
Lancer has taken a journey into the internet, companies, meet ups, and bars to find out why TDD is not yet mainstream. In upcoming episodes we’ll cover what TDD is, hear from developers why they don’t TDD, and hear from managers what they see as the problem. We’ll also cover how to do TDD, what the project characteristics look like when TDD is working, and early warning indicators of failed adoption. And finally we’ll cover how to start doing TDD as: a developer, a team lead, a manager, and as a director.
Developers who actually do TDD are rare, like unicorns and flying cars. So if you like the idea of flying cars, and like me, are unsatisfied being tied to the earth whenever you want to go somewhere, then take a deep look within yourself as you may be part of the holdup. We all complain that the other person’s or company’s software quality is low because every other release something that used to work, stops. That is a test automation problem. That shiny flying car we all want, the code that operates it is going to need a good micro test suite. By each of us being quick to hop to the latest “something.io” library yet unwilling to spend much effort to learn something as powerful as TDD, we’ll never get our flying cars because you and your passengers will be tits up in a shallow impact crater when the software stops working.
FIND ALL THE EPISODES FOR THIS SERIES AT THE SERIES PAGE.
