2 ms·
It boils down to "because they don't get to be in control." Or perhaps "they have to answer to someone else." Or lastly "they don't like being told they're wr
by mgkimsal 15y ago
It boils down to "because they don't get to be in control." Or perhaps "they have to answer to someone else." Or lastly "they don't like being told they're wrong."
I'm not sure any developers like any of those situations either.
"My data structure is killer!. What's that? Oh, we now need to track more info at a different level? But... that'll KILL all my ORM work! Users should just deal with what's there - it already works!"
The 'ugly pastiche' issue - I'm not sure why it'd be an ugly pastiche. The author seems to be suggesting that sections that 'won' from multiple disparate tests would be thrown together in to one interface without testing that interface. The little a/b testing I've seen done tended to be more iterative and sequential - design a vs b, then b vs c, then b vs d, then d vs e, etc.