Imagine a PHB-engineer conversation something like "What are you working on?" "The jQuery plugin we're using doesn't have full support for the latest Chrome n

Imagine a PHB-engineer conversation something like "What are you working on?" "The jQuery plugin we're using doesn't have full support for the latest Chrome nightlies so I'm trying to write some Javascript to achieve the same effect." "Why are you wasting time? I don't know all that much about jQuery, but you can use an iPad to do it." We can all appreciate that that sort of conversation is pretty exasperating for the engineer, but if he were a nice guy, he'd want to try to explain at least enough engineering to the boss such that the boss understood why "Use an iPad" is not a compelling option there. But he might be disinclined to start that conversation at 2:40 in the morning because it would take a while. It is 2:40 AM in Japan and improving your understanding of A/B testing would take a while. There exist many comprehensible beginner's guides to it on the Internet. If after reading them you still don't understand why you need two more pieces of data in your hypothetical and why it is not extraordinarily likely that the 7% increase you measure in it reflects an action change in user behavior, I will be happy to explain it to you some day when it is not 2:40 AM.