3 ms·

"I drive better when I've had a few" is something I have actually heard from people in my past. Far, far past. And they think that because they no longer have t

"I drive better when I've had a few" is something I have actually heard from people in my past. Far, far past. And they think that because they no longer have that voice in their head that tells them they're doing something stupid. "I code better when I'm high" is something that can only be judged by those around you. If somebody else judges your code to be better, fine. But your self assessment is fundamentally flawed.

vegai_ 5y ago
Those are wildly different actions though, unless you're modifying live production code for a pacemaker or something like that. Doing a bit of inebriated coding that you verify later might be just fine. I'm almost certain that the resulting code won't be better, but there may be situations where a clear head would have produced no code at all due to mental blocks.
- BoxOfRain 5y ago
  As a hard rule I'll never be impaired at work or anything like that, though on my personal projects I've found slowing drinking a glass of a good rum is a very useful aid to programming. As others have said there's a wonderful objectivity to programming, you can't really blag it when you're working with others as I am on the personal project. I think it's the lack of inhibition that helps, it's telling the voice in your head to shut up with over-engineering things and just get to the instant gratification of a panel of green tests and features that work. Debugging while inebriated is another thing altogether, that's no fun at all.
- achenet 5y ago
  Yeah, this is like the Hemingway quote - "Write drunk, proofread sober."
scaramanga 5y ago
That would be true if programming didn't leave a trail of indisputable evidence. If those drunk drivers had to constantly re-live and review telemetry data for their trips they would change their tune?

3 ms·

"I drive better when I've had a few" is something I have actually heard from people in my past. Far, far past. And they think that because they no longer have t

by geocrasher 5y ago

vegai_ 5y ago
Those are wildly different actions though, unless you're modifying live production code for a pacemaker or something like that. Doing a bit of inebriated coding that you verify later might be just fine. I'm almost certain that the resulting code won't be better, but there may be situations where a clear head would have produced no code at all due to mental blocks.
- BoxOfRain 5y ago
  As a hard rule I'll never be impaired at work or anything like that, though on my personal projects I've found slowing drinking a glass of a good rum is a very useful aid to programming. As others have said there's a wonderful objectivity to programming, you can't really blag it when you're working with others as I am on the personal project. I think it's the lack of inhibition that helps, it's telling the voice in your head to shut up with over-engineering things and just get to the instant gratification of a panel of green tests and features that work. Debugging while inebriated is another thing altogether, that's no fun at all.
- achenet 5y ago
  Yeah, this is like the Hemingway quote - "Write drunk, proofread sober."
scaramanga 5y ago
That would be true if programming didn't leave a trail of indisputable evidence. If those drunk drivers had to constantly re-live and review telemetry data for their trips they would change their tune?