WRITE FUCKING DOCS FOR YOUR CODE YOU FUCKING RETARDED PROGRAMMERS!! FUCK YOU ASSHOLES!!!!!

WRITE FRICKING DOCS FOR YOUR CODE YOU FRICKING moronic PROGRAMMERS!! FRICK YOU buttholeS!!!!!

Beware Cat Shirt $21.68

Rise, Grind, Banana Find Shirt $21.68

Beware Cat Shirt $21.68

  1. 2 months ago
    Anonymous

    sorry im just not gonna do it
    they didn't allocate enough time for me to explain the odd bits
    maybe ask a LLM to guess why it is the way it is

    • 2 months ago
      Anonymous

      skill issue

      any decent programmer can figure it out, like how hard is it to just look at the code to see what it's doing?

      Good code is self documenting. This can't be done without a strongly typed language, though, ideally OO.

      >If I write my shitty code long and don't write documentation about it that's ok
      >But if Apple or others don't write documentation about X that's not ok
      IQfy hypocrisy

      • 2 months ago
        Anonymous
        • 2 months ago
          Anonymous

          ESL here, is this proper grammar? serious question

          • 2 months ago
            Anonymous

            Part of the joke is the fat redditor deliberately employing convoluted syntax as though he's being formal

          • 2 months ago
            Anonymous

            The other half is the deliberate choice to place the most absurd part of the statement last because "leave the multimillion company alone" shoots the joke's wad halfway through

        • 2 months ago
          Anonymous

          >pointing out individual hypocrisy is defending big corporation
          fricking moron lol

    • 2 months ago
      Anonymous

      >sorry im just not gonna do it
      You stay a perma-junior then. Wrong attitude for advancement anywhere.

      • 2 months ago
        Anonymous

        if only it worked that way

  2. 2 months ago
    Anonymous

    >hey butthole, put that finger up your ass!

  3. 2 months ago
    Anonymous

    skill issue

    any decent programmer can figure it out, like how hard is it to just look at the code to see what it's doing?

    • 2 months ago
      Anonymous

      i'm pretty sure if i share my code with you you'll go through all the files and read 10k lines of my code, right?

    • 2 months ago
      Anonymous

      That's not the issue, I shouldn't have to pick through your shitty 100 line function to find where I need to change to make my small modification.

  4. 2 months ago
    Anonymous

    Good code is self documenting. This can't be done without a strongly typed language, though, ideally OO.

    • 2 months ago
      Anonymous

      >Good code is self documenting
      It sort of is but it's so much easier to read 3 lines of comments instead of jumping between classes like a moron to make sense of the abstractions.

    • 2 months ago
      Anonymous

      Wrong
      Well written code explains what its doing
      It doesn't explain _why_ its doing it

    • 2 months ago
      Anonymous

      for the longest time I thought this meant you have to hit the keys on the keyboard very forcefully when you use it

    • 2 months ago
      Anonymous

      Comments are supposed to explain why, not how, something is done.

    • 2 months ago
      Anonymous

      >Good code is self documenting.
      unfortunately the morons I work with don't write good code

  5. 2 months ago
    Anonymous

    I can't even reread my own code and know what it does. I keep forgetting what stuff does.

    And this is only with bash I have no idea how you guy deal with this on big stuff lol.

    • 2 months ago
      Anonymous

      If a shell script that isn't something like .bashrc is more than 10 lines long I ask myself why I'm using shell scripting, considering how horrendous most shell languages are as general purpose PLs, and I say this as someone who writes a lot of shell scripts. They're widgets not full fledged applications.

      • 2 months ago
        Anonymous

        Looks at my 80 line script.... I only know bash bros....

        • 2 months ago
          Anonymous

          >I only know one PL
          Show hand

  6. 2 months ago
    Anonymous

    programmers will write 100k lines convoluted of code, but are too lazy to write 200 lines for an example use

    • 2 months ago
      Anonymous

      If your IDE has plugins or similar to generate *Doc headers for functions that it itself understands when you invoke that function in code, correctly prompting you for the parameters and their types with descriptions of their purposes as you invoke it, that's a huge incentive to actually incorporate that habit.
      >But I use emacs/vi
      homosexual

  7. 2 months ago
    Anonymous

    Ever heard of job security?

    • 2 months ago
      Anonymous

      Can't be fired if you're the only one who can keep things working.

  8. 2 months ago
    Anonymous

    the doc is in my head. Sorry that you can't mind read. Big skill issue on your part.

  9. 2 months ago
    Anonymous

    But I do
    Both separate docs and comments in source, including links to code I found elsewhere
    >Oh what a mindful good boy you are, if you get hit by a bus a co-worker can pick up where you left off
    No, my memory is shit and this is for my own sake esp with larger codebases. I literally have comments like "do not optimize this statement using X method, it creates mustard gas." It just happens to also have the side benefit of potentially helping someone else some day.

  10. 2 months ago
    Anonymous

    What are you talking about I have all my coding documentation right here haha
    *pulls out notepad with mini sticky notes*
    I've even color coded the sections! Please return it to me as I have to put it into the bucket as that's almost done

  11. 2 months ago
    Anonymous

    >licks paw

  12. 2 months ago
    Anonymous

    How is my startup supposed to make money from support contracts off of my hastily cobbled together "open source" software written in a meme language that is actually just a more complicated version of something that has already existed for 20+ years if I just give you documentation for free?

  13. 2 months ago
    Anonymous

    By documenting your code you make it easier to train AI on it.
    Non-dox Chads were right from the start, I wish I wasn't documenting my code on GitHub repo, Microsoft 100% trained their AI on it.

    Write misleading documentation instead.

    • 2 months ago
      Anonymous

      Our company's GH repo is enterprise i.e. private, plus copilot is a fricking joke

      • 2 months ago
        Anonymous

        How do you know they didn't use it for AI training? It's not like they'd tell you.

        • 2 months ago
          Anonymous

          He who steals from me steals shit

  14. 2 months ago
    Anonymous

    do that next and next is project managers making bad decisions for you

  15. 2 months ago
    Anonymous

    >WRITE FRICKING DOCS
    Sorry it's not in the ticket. My performance reviews are entirely about my Jira metrics.
    If you want it make a business case and write tickets.

  16. 2 months ago
    Anonymous

    do you mean comment? I do.

    ># OP is a gay.

Comments are closed.