Pack of programmers and game theory
Hi, I thought this from Jonathan Rees might entertain some people. (This is after the OO stuff.)
"In a pack you want to restrict everyone else's freedom as much as possible to reduce their ability to interfere with and take advantage of you, and the only way to do that is by either becoming chief (dangerous and unlikely) or by submitting to the same rules that they do.
"In such a pack-programming world, the language is a constitution or set of by-laws, and the interpreter/compiler/QA dept. acts in part as a rule checker/enforcer/police force. Co-programmers want to know: If I work with your code, will this help me or hurt me? Correctness is undecidable (and generally unenforceable), so managers go with whatever rule set (static type system, language restrictions, "lint" program, etc.) shows up at the door when the project starts."
Rereading on game theory reminds me of places I worked at. http://plato.stanford.edu/entries/game-theory/
Friday, June 6, 2003
Fog Creek Home