His finale after all that was clarity. He suggested it'd be better to aim for being a software writer more than a software engineer, and to focus on writing software well.
As others have pointed out, he did argue that unit testing is sometimes a waste of energy when taking to the extreme. However, along with that he pointed out that he believes system tests are in fact important, and his take is that they're much more important than 100% code coverage in testing. Does your whole system work?
Comments
I am not at RailsConf and haven't watched the talk yet, but:
"In many ways, the prism of computer science is harmful for the development of information systems" - https://twitter.com/wycats/status/458616115451527168
"DHH is essentially talking about how getting overly concerned with testing millions of isolated pieces is more trouble than it's worth." - https://twitter.com/wycats/status/458620203711344640
"A good TLDR of this talk is that pseudo-CS exploits your desire for "science" but does more harm than good." - https://twitter.com/wycats/status/458622138099183616
EDIT: I'm most of the way through the talk now, I agree with wycats' summary.
His finale after all that was clarity. He suggested it'd be better to aim for being a software writer more than a software engineer, and to focus on writing software well.
As others have pointed out, he did argue that unit testing is sometimes a waste of energy when taking to the extreme. However, along with that he pointed out that he believes system tests are in fact important, and his take is that they're much more important than 100% code coverage in testing. Does your whole system work?