• LagrangePoint@lemmy.world
    link
    fedilink
    arrow-up
    30
    ·
    1 year ago

    Yeah, this was torture in grade school. I figured it would get better in middle school.

    Then it was torture in middle school and I thought it would get better in high school.

    Then it was STILL torture in high school and I thought it would surely, surely get better in college.

    Then I got to college and there were still mofos reading. like. this.

    • maniacal_gaff@lemmy.world
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      I am an engineer who oversees a team. Most of them can’t write more than a coherent sentence. Code and analyze data, sure, but put together a coherent paragraph? Not really.

      • ChickenLadyLovesLife@lemmy.world
        link
        fedilink
        English
        arrow-up
        27
        arrow-down
        2
        ·
        1 year ago

        There’s a weird ongoing thing in the programming world where about half of coders think code should be well-commented and the other half not only think that code shouldn’t contain comments but also think that comments are an indicator of professional incompetence (aka a “code smell”). I’ve long noticed that the anti-commenting crowd are also the ones that can’t write very well.

          • Gabu@lemmy.world
            link
            fedilink
            arrow-up
            4
            arrow-down
            2
            ·
            1 year ago

            People who dislike code documentation are often overoptimizers, from my experience.

                • afraid_of_zombies@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  1
                  ·
                  1 year ago

                  Assuming it even does save it. The complier is going to do what it wants to do. Unless you really know your stuff any high level language is going to be a black box. One guy I worked with loved to do that but he would be able to prove that it did matter.

        • kicksystem@lemmy.world
          link
          fedilink
          arrow-up
          9
          ·
          1 year ago

          One way my code improves is by thinking what I need to comment. Then I refactor some and the comments become somewhat redundant.

          • ChickenLadyLovesLife@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            I was basically driven out of my last job by someone who wouldn’t agree to work with someone (me) who did comment their code. Like I said, it’s a really weird dividing line in programming.

            • afraid_of_zombies@lemmy.world
              link
              fedilink
              arrow-up
              2
              arrow-down
              1
              ·
              1 year ago

              I am sorry that happened to you but it sounds like it was for the best. I work at a place where knowledge sharing is pushed for. Everyone shares what they know. It makes things so much easier even if we do “waste” time cross training.

              My last job was me replacing the inhouse developer, I got it by demonstrating on the interview that I could reverse engineer his code. The versions he had put into production had all the comments stripped out and he had replaced every variable with random alphanumeric sequences about 8 characters long.

              Shouldn’t have known right there and then what kinda workplace I was dealing with.

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

        I have had to tell software engineers time and time again that is is totally okay to make error strings beyond one sentence or one word. It almost seems to me that they never realized that strings can hold multiple sentences and and don’t have relevant memory constraints.