I think it goes a little deeper. Kent's original post (test && commit || revert) describes the strategy as just a curiosity. "I’m not arguing for “test && commi

I think it goes a little deeper. Kent's original post (test && commit || revert) describes the strategy as just a curiosity. "I’m not arguing for “test && commit || revert” nor even describing its trade-offs. I’m saying it seems like it shouldn’t work at all, it does, and I hope you try it (if you’re the sort of person who just tries new programming workflows)." But the problem is Kent has probably never been on the wrong side of a CxO's dictum: "This company is using agile, starting now. Thank you." Programmers who have felt that pain want to make sure that a random musing from Kent Beck doesn't turn into a "movement" that ruins their work, so they try to shut down his idea hard. I don't blame them.