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 danso on Monday April 08, 2013 @09:55AM
(#5511673)
It's worth noting that swishing Listerine (which does contan real alcohol) will fool police breathalyzers, if you use it minutes before the test. This is why you do a long series of physical coordination tests before finally getting a breathalyzer test when being pulled over:
Re:Show HN: gitdown - prevents you from coding drunk
by Houshalter on Tuesday April 09, 2013 @06:03AM
(#5517173)
I looked it up and it is about 21% ethanol. Which is more than most drinks I think.
EDIT: On further research it seems that they put stuff into mouthwash to make it undrinkable, in order to prevent abuse and avoid taxes and regulation on alcohol. That doesn't prevent you from ingesting it however. It's just supposed to make it unpleasant.
Re:Show HN: gitdown - prevents you from coding drunk
by tterrace on Monday April 08, 2013 @11:52AM
(#5512448)
This is awesome, there's just something that's inherently cool about building things that take physical input using hardware other than a mouse & keyboard.
Re:Show HN: gitdown - prevents you from coding drunk
by systematical on Monday April 08, 2013 @11:48AM
(#5512421)
This is pretty cool, but why would anyone want to program drunk? Maybe I'll program for a few minutes over the occasional glass of wine as I am gearing down for bed, but full on drunk? No...
Re:Show HN: gitdown - prevents you from coding drunk
by gklitt on Monday April 08, 2013 @10:55AM
(#5512035)
Well, looks like we weren't the only ones to have this idea!
I think our project fits more naturally into a standard git workflow because the script is automatically called as a git hook. His project does have us beat with displaying messages as rainbow ASCII art though.. :)
> 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.
Turns out TDD also stands for Teenage Drunk Driving. :-/
It isn't measuring BAC very well at all if it is easily confused by someone who has used mouthwash.
EDIT: That's not to say it isn't an awesome project, which it definitely is :)
http://askville.amazon.com/Crest-mouthwash-make-fail-breatha...
We found that the Listerine effect seems to diminish quickly after several minutes.
EDIT: On further research it seems that they put stuff into mouthwash to make it undrinkable, in order to prevent abuse and avoid taxes and regulation on alcohol. That doesn't prevent you from ingesting it however. It's just supposed to make it unpleasant.
I think our project fits more naturally into a standard git workflow because the script is automatically called as a git hook. His project does have us beat with displaying messages as rainbow ASCII art though.. :)