So two issues with this. > Pick the language and stack based on your team’s needs and comfort, based on your business’s need and risk tolerance, and based on h

So two issues with this. > Pick the language and stack based on your team’s needs and comfort, based on your business’s need and risk tolerance, and based on how easy it will be to produce software for your target users in that language or framework. Developers clearly do care what language they use so this is a factor to take into consideration. Plain and simple - Java 1.0 might tick all of these boxes but you'll struggle to find many interested and passionate developers. > I believe we can build better software, faster. I believe adopting Test Driven Development can change how we build software. I believe it allows us to build better software, faster. I believe it allows our software projects to reflect the needs our businesses and stakeholders have: To get the features stakeholders want, and demonstrate how the system works as quickly as possible. This is from George's homepage which reads exactly like the 'BS' he's targeting. Which I think nullifys his argument - he's just gone on to give a shit about programming techniques instead.