News for hackers. Stuff that matters.
Re:Why programmers should play Go by mattmaroon on Monday July 14, 2008 @07:28PM (#246224)
I generally advise people to play games that involve some randomness, like poker, gin, or backgammon, before moving on to games without. The reason being that almost all of life involves decision making in situations with some random factor, and humans are ill-equipped by biology for this. Most decisions that don't involve some unknown are relatively easy.

Go might be better for programming specifically (since randomness isn't a factor) but programming is a subset of life.

Re:Why programmers should play Go by brent on Monday July 14, 2008 @08:14PM (#246251)
> Most decisions that don't involve some unknown are relatively easy.

Apparently you don't play go.

I play games for entertainment, not to mimic reality. Games with chance as a significant component aren't necessarily more entertaining than games requiring significant skill.

Re:Why programmers should play Go by mattmaroon on Monday July 14, 2008 @09:27PM (#246289)
I would say the general population disagrees with you, which is why are games of chance a multi-billion dollar industry and only a few people can make a good living playing chess.
Re:Why programmers should play Go by brent on Monday July 14, 2008 @11:47PM (#246353)
Well, other skill based "games" include the majority (or all?) of professional sports. If there were chance introduced at key points in the game (like drawing cards or flipping coins) I don't think anyone would watch baseball, football, or soccer.

Also, board games involving skill (e.g. chess and go) have stood the test of time over many chance games.

Re:Why programmers should play Go by eru on Tuesday July 15, 2008 @08:08AM (#246581)
From http://en.wikipedia.org/wiki/Penalty_shootout_(football)#History

"Where a replay or playoff was not possible, ties were previously decided by drawing of lots. Examples include Italy's win over the USSR in the semi-final of the 1968 European Championship."

Re:Why programmers should play Go by mattmaroon on Tuesday July 15, 2008 @12:46PM (#246810)
Chance is a huge element in sports. Otherwise nobody would watch them.

You're separating luck and skill as if games can't have both, and in the process entirely missing my point.

Re:Why programmers should play Go by brent on Tuesday July 15, 2008 @02:10PM (#246905)
Clearly there is a spectrum, I'm not missing your point. In this spectrum though, chess/go/sport are at one end and gambling is at the other. Poker is in the middle.
Re:Why programmers should play Go by mattmaroon on Thursday July 17, 2008 @04:09AM (#248330)
Sport is probably closer to the middle than you think, especially where a team is involved. If you don't think an athlete can get unlucky, ask anyone on the Falcons. One teammate does something stupid and your team is out of contention for years.

Teams are generally businesses too, and just like most other businesses have a huge random element.

Re:Why programmers should play Go by dood on Monday July 14, 2008 @08:25PM (#246258)
There is plenty of unknown in Go.
Re:Why programmers should play Go by mattmaroon on Monday July 14, 2008 @10:55PM (#246323)
I must be playing it wrong. I've only played a couple times, but I thought it was a game of complete information. Perhaps I was taught incorrect rules.
Re:Why programmers should play Go by skmurphy on Tuesday July 15, 2008 @01:07AM (#246397)
Event thought it's a game of complete information I find it hard to foresee the moves of better players that kill my stones and capture more territory. And I can't console myself that he got the right card or had a good die roll. There is clearly a place for games of chance but the level of complexity in the go game tree makes it very interesting.
Re:Why programmers should play Go by mattmaroon on Tuesday July 15, 2008 @12:42PM (#246806)
Well, not knowing your opponents' moves is common to every game. Otherwise its not a game.
Re:Why programmers should play Go by skmurphy on Tuesday July 15, 2008 @01:08PM (#246835)
Sure, but when I was five I found tic tac toe a challenge because I couldn't visualize the game tree. It's also a game of "perfect information."
Re:Why programmers should play Go by mattmaroon on Thursday July 17, 2008 @04:02AM (#248324)
Doesn't that agree with what I was saying? Games of perfect information are less skill intensive than some games that don't have it, because it's just a matter of visualizing the game tree, even though with chess or go the tree is too big.
Re:Why programmers should play Go by dood on Tuesday July 15, 2008 @02:06PM (#246903)
If you are a fan of games, I heartily encourage you to give Go a good chance. It is both beautiful and profound, yet of broad practical benefit. Poker, though very different, is the only other game I know which is comparably elegant, applicable and revelatory.
Re:Why programmers should play Go by mattmaroon on Thursday July 17, 2008 @04:07AM (#248328)
I'm sure I'll spend some time on it some day.
Re:Why programmers should play Go by jon_dahl on Tuesday July 15, 2008 @05:13PM (#247089)
I'd look at it more like chaos. Theoretically, there is absolutely nothing random in the shuffling of a deck of cards or the roll of dice, bracketing the human elements. It's just really really complex, so we call this chaos/random.
Re:Why programmers should play Go by dood on Monday July 14, 2008 @11:17PM (#246339)
I mean unknown in the sense of unpredictability, chaos, combinatorial complexity.
Re:Why programmers should play Go by ken on Monday July 14, 2008 @08:22PM (#246255)
I've never heard anybody complain that Go was too easy.
Re:Why programmers should play Go by mattmaroon on Monday July 14, 2008 @08:26PM (#246259)
I meant more decisions in life in general. Go is certainly not easy.