Very cool analysis, and I think especially relevant to LW.
I’d love to see more articles like this, forming a series. Programming and software design is a good testing ground for rationality. It’s about mathematically simple enough to be subject to precise analysis, but its rough human side makes it really tricky to determine exactly what sort of analyses to do, and what changes in behavior the results should inspire.
Thanks! This work owes a substantial debt to LW, and this post (and possible subsequent ones) are my small way of trying to repay that debt.
So far, though, I’ve mostly been blogging about this on G+, because I’m not quite sure how to address the particular audience that LW consists of—but then I also don’t know exactly how to present LW-type ideas to the community I’m most strongly identified with. I’d appreciate any advice on bridging that gap.
Very cool analysis, and I think especially relevant to LW.
I’d love to see more articles like this, forming a series. Programming and software design is a good testing ground for rationality. It’s about mathematically simple enough to be subject to precise analysis, but its rough human side makes it really tricky to determine exactly what sort of analyses to do, and what changes in behavior the results should inspire.
Thanks! This work owes a substantial debt to LW, and this post (and possible subsequent ones) are my small way of trying to repay that debt.
So far, though, I’ve mostly been blogging about this on G+, because I’m not quite sure how to address the particular audience that LW consists of—but then I also don’t know exactly how to present LW-type ideas to the community I’m most strongly identified with. I’d appreciate any advice on bridging that gap.