5 ms·
Write drunk, edit buzzed, then?
by nscalf 7y ago
Write drunk, edit buzzed, then?
- vsareto 7y agoBeer code tends to forget about edge cases in my experience, so yeah
- beobab 7y agoI never remember to put comments in when I am beer-coding. Caffeine-code is much easier to follow later.
- kingpiss 7y agoMy weed code is usually really creative but riddled with bugs
- petra 7y agoDoes it help with solving hard problems ?
- mywittyname 7y agoWhen you come back sober, the solutions won't make any sense.
- oh_sigh 7y agoPersonally, weed might help in the creative phase of problem solving, but if it requires working memory weed is a big negative(at least how it affects me)
- chrstphrhrt 7y agoI think including some CBD in there negates the memory issues.
- nkingsy 7y agoI find it's great for diving into refactoring projects that I've been putting off. I like to do that stoned because it's usually not that hard, just tedious moving files around and organizing things. Same way my wife reorganizes the furniture when she gets stoned. I also sometimes find solutions to hard problems in my head when stoned, though I usually just write down the solution rather than coding it, as large-scale implementations are better done sober.
- deleted 7y ago[deleted]
- nicoburns 7y agoYeah, a former colleague of mine told me they used to regularly drink a pint of beer with an evening of coding, until on one occasion they introduced a subtle bug which took them two days to hunt down. They were working in C, which makes it a lot easier to introduce subtle bugs than most languages, but I certainly think twice about coding while under the influence since I heard that story!
- leesec 7y agoCode drunk, commit sober.
- mariodiana 7y agoI remember reading writing advice somewhere (prose, not code) that suggested you have an alcoholic beverage in the evening for your rough drafts, and then coffee in the morning for your editing. The strategy was: loosen up and then tighten up.