The two sides are shown an end state considered to be the goal. One side writes directions to accomplish the goal, including whatever constraints he wants. His opponent tries to fail to accomplish the task while still following the directions an fulfilling the requirements.
The second player should always be able to win in absolute terms. His real goal is to be minimally obtuse—find the minimal distance between our usual priors and the priors he has to assume so that the directions don’t complete the task.
For any of the rationality skills, probably the most important meta skill is to have some reliable way to evaluate how well you are doing. Just as EY talked about use cases, you need your test cases as well. As the years have gone by, I’ve noticed how the methodologies in engineering/software development are generally applicable to life.
My game is close to one you can see everyday in contracting. Company A contracts on a fixed price bid to fulfill the requirements spec of Company B. Company A wants to minimize it’s cost for fulfilling the contract, so it prefers defensible interpretations of the requirements that minimize their cost. On the other side of that pancake, Company A tries to find a defensible interpretation of the contract that maximizes their value.
I’d suggest a game—I Don’t Wanna.
The two sides are shown an end state considered to be the goal. One side writes directions to accomplish the goal, including whatever constraints he wants. His opponent tries to fail to accomplish the task while still following the directions an fulfilling the requirements.
The second player should always be able to win in absolute terms. His real goal is to be minimally obtuse—find the minimal distance between our usual priors and the priors he has to assume so that the directions don’t complete the task.
For any of the rationality skills, probably the most important meta skill is to have some reliable way to evaluate how well you are doing. Just as EY talked about use cases, you need your test cases as well. As the years have gone by, I’ve noticed how the methodologies in engineering/software development are generally applicable to life.
My game is close to one you can see everyday in contracting. Company A contracts on a fixed price bid to fulfill the requirements spec of Company B. Company A wants to minimize it’s cost for fulfilling the contract, so it prefers defensible interpretations of the requirements that minimize their cost. On the other side of that pancake, Company A tries to find a defensible interpretation of the contract that maximizes their value.