News for hackers. Stuff that matters.
Re:Objections are goals by pjc50 on Wednesday October 10, 2018 @09:13AM (#18184493)
Another way of looking at this is: all advice is conditional. It only works for people in certain setups and environments. People rarely specify their conditions, and may not even be aware of the other possibilities.

So when offering advice or suggestions for process improvement, always try to add at least a couple of sentences describing the context at the front. It'll reduce the amount of objections you get.

Re:Objections are goals by default-kramer on Wednesday October 10, 2018 @01:45PM (#18187231)
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.