https://arxiv.org/abs/2404.10002

Abstract (emphasis mine):

The concept of a ‘Ballmer Peak’ was first proposed in 2007, postulating that there exists a very specific blood alcohol content which confers superhuman programming ability. More generally, there is a commonly held belief among software engineers that coding is easier and more productive after a few drinks. Using the industry standard for assessment of coding ability, we conducted a search for such a peak and more generally investigated the effect of different amounts of alcohol on performance. We conclusively refute the existence of a specific peak with large magnitude, but with p < 0.001 find that there was a significant positive effect to a low amount of alcohol - slightly less than two drinks - on programming ability.

  • katja@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    30
    ·
    6 months ago

    I’ve found that the best way to utilize alcohol when programming is to code sober and comment drunk. It’s a wonderful way to make commenting both fun to write and to read later.

    I have tried coding under the influence, but I can’t do it. Even small amounts of alcohol makes it really hard to do anything complex. But if it works for you, good on ya.

    • Affidavit@aussie.zone
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 months ago

      Also works for customer service. Have a ridiculously minor issue that really doesn’t matter but still irks a small part of you and you’re too much of a wimp to speak up about? Check your sent folder in the morning after a night of drinking.

      Protip: support@company.com.

    • zeekaran@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 months ago

      I did some of my best problem solving on Vicodin.

      Two beers and I’m fully functional.