News for hackers. Stuff that matters.
Re:Why HN was down by RyanMcGreal on Monday February 18, 2013 @02:01PM (#5239924)
I'm not sure if rubber duck debugging would have helped here. The problem was in the data, not the code. (I know, I know: in Lisp code is data.)
Re:Why HN was down by chernevik on Monday February 18, 2013 @02:10PM (#5239984)
That's exactly the sort of thing a duck will tell you. "So what has changed? Let's see, new code, new server, and I fixed the commenter's comment. That was simple I just hard-hacked the comment id and . . . excuse me a second."
Re:Why HN was down by RyanMcGreal on Monday February 18, 2013 @02:24PM (#5240086)
Good point. I was thinking in terms of going through the code line by line, which if anything would lead you away from the trail.
Re:Why HN was down by DanielBMarkham on Monday February 18, 2013 @02:09PM (#5239979)
Yep. I thought this through as I was typing my comment.

(There must be some joke involving the use of a meta-duck, but I can't come up with it. :) (Same principle applies, of course, just LISP makes the determining of "what" a bit more tricky. (insert discussion here about the general differences between debugging imperative and functional code)))

Re:Why HN was down by cube13 on Monday February 18, 2013 @02:14PM (#5240014)
Rubber duck debugging may have actually been the distraction that caused pg to make the mistake, too!