Comments

• impossible_silver@programming.dev ⁨1⁩ ⁨year⁩ ago

  Is the Pic AI generated? Lol

  source

  • Cat@kbin.social ⁨1⁩ ⁨year⁩ ago

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

    source

    • cake@lemmings.world ⁨1⁩ ⁨year⁩ ago

      Alien ducks

      source
  • BluesF@lemmy.world ⁨1⁩ ⁨year⁩ ago

    I wouldn’t be surprised if the whole meme was. What on earth does the picture have to do with the text lol

    source

    • Zorque@kbin.social ⁨1⁩ ⁨year⁩ ago

      Have you not heard of rubber duck debugging?

      source
    • VigilantQuasar@lemmy.world ⁨1⁩ ⁨year⁩ ago

      The image is definitely AI, but I assume the rubber duckies are in reference to this en.m.wikipedia.org/wiki/Rubber_duck_debugging

      source
    • TheGreenGolem@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Rubber duck debugging

      source

      • -> View More Comments
    • name_NULL111653@pawb.social ⁨1⁩ ⁨year⁩ ago

      ‘Rubber duck’ debugging is a thing…

      source
    • icepuncher69@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      Ir just looks silly

      source
  • mriormro@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Why tf does someone need ai to make memes?! Jesus Christ…

    source

    • Sotuanduso@lemm.ee ⁨1⁩ ⁨year⁩ ago

      You expect a meme maker to photograph that themselves?

      source
• NotAnonymousAtAll@feddit.de ⁨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.

  source

  • JDubbleu@lemmy.world ⁨1⁩ ⁨year⁩ ago

    For my current job we’ve all agreed to take the approach of not writing comments that say what the code does, but why you did something the way you did. Probably about 90% of our code is uncommented because it just doesn’t need to be, but every once in a while you have to do something out of the ordinary to get the desired behavior, and explaining why you made the weird decision you did is infinitely more helpful.

    source

    • dukk@programming.dev ⁨1⁩ ⁨year⁩ ago

      This exactly. I love this approach to commenting and use it all the time. I also like to write doc-comments wherever possible; it’s saves time and makes working on an unfamiliar part of the codebase much easier.

      source
  • squaresinger@feddit.de ⁨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.

    source

    • Sotuanduso@lemm.ee ⁨1⁩ ⁨year⁩ ago

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

      Image

      source
    • h_a_r_u_k_i@programming.dev ⁨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.

      source

      • -> View More Comments
    • NotAnonymousAtAll@feddit.de ⁨1⁩ ⁨year⁩ ago

      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.

      Unit tests should be the parity check for other code. Those don’t get outdated with the next refactoring where someone didn’t remember to also adjust all the comments.

      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.

      Why would people be better at judging if something needs a comment than at judging if something needs a better name or refactoring? Asking people to skip that judgement step and comment everything just gives you a bunch of useless boilerplate comments. That trains everyone reading that codebase to ignore comments because they are almost always useless anyway.

      putting documentation of the code anywhere else than in a comment (e.g. Confluence) is a total waste of time

      At least this we can 100 % agree on. Documentation should be a as close as possible to the code. (I just think most of the time that place is in the name of things, not in an actual comment.)

      source

      • -> View More Comments
  • blackbirdbiryani@lemmy.world ⁨1⁩ ⁨year⁩ ago

    The problem here is that every junior programmer thinks they write clean code when they really really don’t. Often I find the act of writing comments makes you go back to the code and clean things up, so it’s still worth encouraging comments.

    source

    • Von_Broheim@programming.dev ⁨1⁩ ⁨year⁩ ago

      Just do TDD instead

      source
  • sweeny@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    I just get AI to write my comments lol. I’ll paste the function or component and tell it to write comments in tsdocs format and it works great every time (I will also add to it sometimes of course).

    Don’t get me wrong, I also write clean code with good function and variable naming, but I find comments are also useful for a few reasons; they make the code even more quickly readable, they can explain why the code is the way that it is, and my favorite reason, they make it so when you hover over a reference to the commented item in an ide you get an explanation of exactly what the code does and what it expects without having to find and read the code itself

    source
  • uberrice@feddit.de ⁨1⁩ ⁨year⁩ ago

    If you think a block of code needs a comment, turn it into a method and give it a proper name instead.

    Really depends. Yes, if someone doesn’t get what’s wrong with this statement, they should. But you shouldn’t wrap something in a method all the time just because. Sure, maybe you can make it an inline method, but usually, a method call takes time, and while it’s not a lot of time, in constrained or complex system that can accumulate. A lot. Sure, the compiler might optimize stuff away, but don’t just go blindly trusting your compiler.

    source
  • marty@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

    This is the way. In ‘some’ cases comments are perfectly fine. Like when you need to document ‘why’ something was done the way it was our to link to a specific piece of documentation.

    When you start commenting ‘what’ the code does, you code is not self explanatory enough. And those comments will get outdated and need refactoring too. Just more unnecessary work.

    source
• i_need_a_vacation@kbin.social ⁨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.

  source

  • wdx@feddit.de ⁨1⁩ ⁨year⁩ ago

    Could a pre-commit hook have caused the murder to not get committed?

    source
• quazar@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Give a man AI and he’ll make a meme

  teach a man AI and he’ll make money making memes

  source
• UsernameIsTooLon@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Oh no. 2 weeks ago ThioJoe created a program that allows you to AI generate memes and this looks scarily similar.

  source

  • PipedLinkBot@feddit.rocks [bot] ⁨1⁩ ⁨year⁩ ago

    Here is an alternative Piped link(s): piped.video/7LBLESXAJh0

    Piped is a privacy-respecting open-source alternative frontend to YouTube.

    I’m open-source, check me out at GitHub.

    source
• dylanTheDeveloper@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I just want variable names to be consistent. You do variableName then 5 lines down Jerry does a typo VariableNames and so Bob makes a function that’s gets it’s value from variableName and sets VariableNames with it 100 lines down. You know forgot it I should’ve made a comment

  source
• sj_zero ⁨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.

  • rh4c6f@lemmy.world ⁨1⁩ ⁨year⁩ ago

    This is why I leave my phone in the basement when I get home.

    source

    • sj_zero ⁨1⁩ ⁨year⁩ ago

      This man works
• ytrav@lemmy.world ⁨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

  source
• uphillbothways@kbin.social ⁨1⁩ ⁨year⁩ ago

  test comment. please ignore.

  source
• FlaminGoku@reddthat.com ⁨1⁩ ⁨year⁩ ago

  The code itself is enough documentation!1

  source
• MrGeekman@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Yeah, he’ll beat deadlines by a longshot.

  source

  • iByteABit@lemm.ee ⁨1⁩ ⁨year⁩ ago

    I wish, companies just expect you to write garbage code as quick as possible, only to create tens of bugs afterwards that will take way more time than it would if they had left you enough time to do it correctly

    source