News for hackers. Stuff that matters.
Re:Show HN: gitdown - prevents you from coding drunk by eduardordm on Monday April 08, 2013 @10:00AM (#5511691)
What is the point of TDD if you are not allowed to code drunk? :D
Re:Show HN: gitdown - prevents you from coding drunk by koenigdavidmj on Monday April 08, 2013 @12:16PM (#5512607)
In light of Mr Kernighan's quote:

> Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.

I was advised that one should code stoned, debug caffeinated, and document drunk.

Re:Show HN: gitdown - prevents you from coding drunk by pavel_lishin on Monday April 08, 2013 @01:49PM (#5513260)
Sure, but who wants to read the FAQ section of a manual whose every answer is "Because fuck you, that's why. Wanna fight about it?"
Re:Show HN: gitdown - prevents you from coding drunk by civilian on Monday April 08, 2013 @10:55AM (#5512040)
I was like: "huh, I wonder if there is a quote about the TDD workflow being so good that you can code drunk." so I googl'd for "TDD drunk".

Turns out TDD also stands for Teenage Drunk Driving. :-/

Re:Show HN: gitdown - prevents you from coding drunk by bnycum on Monday April 08, 2013 @11:34AM (#5512323)
I think TDD was suppose to stand for Tequila Driven Development. I had just heard the term this weekend from a random tweet.
Re:Show HN: gitdown - prevents you from coding drunk by HeyLaughingBoy on Monday April 08, 2013 @03:23PM (#5513889)
Hmmm. I once coded a tiny app for a bottle of Patron. Wonder if that counts?