• merc@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      11 months ago

      Most of the places I’ve worked I’d have been told to get rid of the cursing before checking something in. But, my own personal codebase has tons of this sort of thing.

      But, aside from the cursing, these actually look like excellent comments. Comments should warn you when the code isn’t what you might expect. These are excellent from that point of view. If this is what a random sampling of the comments in the codebase looks like, it is probably a very well commented codebase.

  • Mountaineer@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    These are pretty calm messages to an Australian and Garry is British, so culture checks out.

    // What the fuck
    // Fuck dynamic compiling.
    // what the fuck is this shit
    // What the fuck, why isnt this a method

    Should this by the by commentary be there?
    Not really.
    But as a programmer, I understand each and every time I see something like:

    // Urgh this is so dirty, Invalidate() and Refresh() do nothing.
    tButt.AutoSize = false;
    tButt.Width = maxWidth;
    tButt.Height = maxHeight;
    tButt.AutoSize = true;

    • Deebster@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago
        // this is bollocks, delete it
      

      That’s almost certainly from a Brit.

        // this looks like I'm being a fancy arsehole, but this is all because  
        // the window shows up white for some reason when first opened, and this  
        // disguises it.
      

      Could be either.

      chefkiss.png

  • SilentSyntax@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    Wasn’t there a graph posted somewhere at some point which showed the frequency of different swear words in comments in the Linux kernel code?

  • Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    11 months ago

    Man, at $DAYJOB, if we open-source something, they tell us to check for checked-in passwords and whatnot, and force us to throw away the commit history, which always feels stupid when we’ve known upfront that we’re going to open-source it and so kept things clean from the start.

    But then, yeah, you see a post like that and just think that it really wouldn’t have been too difficult to search for swear words before publishing.
    I mean, I also don’t really care, since it’s code rather than an official communication channel, but I can understand why management might care.

    • SpaceNoodle@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      Management can go fuck themselves. Do they want the code to fucking work or not? These are load-bearing fucks.