It took me a while to understand what the puzzle was asking me to solve. Is that a sign I’m a poor programmer? I mean, I had a suspicion which turned out to be correct, but it took me probably 15–20 minutes to confirm it (after rewriting the author’s script in Ruby).
I’m always curious how great programmers think and solve problems, and to be honest, it worries me that you were able to “immediately stop reading,” take five minutes and have it solved. In other words, I feel pretty slow sometimes.
Did anyone else take a moment to “gear up” to solve the puzzle?
Daniel Waite - 2007-10-31 18:27:58
It took me a while to understand what the puzzle was asking me to solve. Is that a sign I’m a poor programmer? I mean, I had a suspicion which turned out to be correct, but it took me probably 15–20 minutes to confirm it (after rewriting the author’s script in Ruby).
I’m always curious how great programmers think and solve problems, and to be honest, it worries me that you were able to “immediately stop reading,” take five minutes and have it solved. In other words, I feel pretty slow sometimes.
Did anyone else take a moment to “gear up” to solve the puzzle?