4 ms·
I had a project that would have gone so very much better if we had simply recorded the minority report, and reviewed them when too many surprises stacked up to
by hinkley 4y ago
I had a project that would have gone so very much better if we had simply recorded the minority report, and reviewed them when too many surprises stacked up to see if anyone was more right than wrong when disagreeing.
There’s a very disturbing misunderstanding about the difference between consensus and unanimity, made doubly so on projects that actually embrace distributed computing concepts like consensus and unanimity.
- camgunz 4y agoYeah this stuff seems so basic right? If you're trying to be as right as possible: - decide what success and failure are - record your successes and failures - adjust your priors based on your failures I have a "what have you changed your mind about" interview question I use on both sides of the table that's really illuminating. The specifics aren't important, but what I'm looking for are the above: what were you aiming for, what did you get instead, how did that experience change you. Hopefully the other party has had lots of these and they've built up an immune system against the various things that caused them to fail, stuff like "test hypotheses", "there is no silver bullet", "everything is a tradeoff" and so on.