• Cat@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Yes it is. Look at the eyes on the ducks. Also the guy’s hands and nose. Dead giveaways.

  • ytrav@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    why would you use a synthesized picture for this meme? Couldn’t you just pick a random, even a lame image from google? You had to make it nonsensical, lifeless and discomforting

  • NotAnonymousAtAll@feddit.de
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    About comments:

    Please please please, do not always write comments. Try to write code that does not need comments whenever possible. Proper variable, class and method names go a long way. If you think a block of code needs a comment, turn it into a method and give it a proper name instead.

    Comments should be a last resort for cases where making the code self explanatory is not possible, and those should be rare.

    About optimization:

    Optimal code is code that fulfills it’s purpose without observable issues.

    If you try to make something faster without any prior complaints or measurements indicating that it being slow is an actual issue, you are not optimizing, you are just engaging in mental masturbation.

    • Square Singer@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I strongly disagree with the comments. “The code is the documentation” was a dumb joke about being to lazy to write documentation, not a best practices guideline.

      Proper naming is good, but there are a lot of issues with not commenting code. Obviously it’s dumb to comment every line, but it’s really useful to comment functions/methods, because otherwise you never know if something’s a bug or a non-obvious feature. Comments act as a parity check to the code, since they tell you what the dev who wrote the code wanted the code to do.

      Also, everone thinks they write good, clean and obvious code. Hardly anyone purpously writes bad, hacky code. Yet if you look at code you wrote a year ago, or code someone else on your team wrote, it’s full of non-obvious hacks. That means, people constantly misjudge the obviousnes of their code. Comments should be put on anything that could maybe be non-obvious.

      And putting documentation of the code anywhere else than in a comment (e.g. Confluence) is a total waste of time (unless you put a link to the specific page of the documentation in a comment in the code), because documentation that you don’t directly see without effort will not be found and not be read.

      • Sotuanduso@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Also, everone thinks they write good, clean and obvious code. Hardly anyone purpously writes bad, hacky code.

      • haruki@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        “Code is the documentation” is the paradise we all want to be someday. But some people use that as an excuse to not write the documentation explaining why this piece of code exists in the first place. I find it extremely annoying when there is not a single architecture diagram is available and someone tell me to figure it out by reading his/her spaghetti code.

  • i_need_a_vacation@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Yeah, this grinds my gears. I use to comment my code when I’m working on my personal projects, then at the office I have to waste time trying to decipher my boss’s code because he won’t comment absolutely anything.

    That plus the ridiculous deadlines means that I don’t have time to comment my own code, fast forward several months later without working on a particular project and now I have to decipher his and my own code.

    One day he actually had the nerve to say to me: ‘Yeah, you should comment your code’. How I refrained of commiting murder that day I don’t know.

  • sj_zero@lotide.fbxl.net
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Don’t write comments for someone else. Write comments for yourself because you might write a million lines of code and then be told you need to do something to this now ancient legacy code at 3am because some nightmare scenario happens and you need to get it fixed and deployed before they’ll let you go back to sleep.