• jol@discuss.tchncs.de
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    26 days ago

    I mean, you’re not hired to “code”, you’re hired to do software engineering. That usually means working with other people. Reviewing code is a win win situation because both get a second pair of eyes on their code and prevent each other from committing dumb shit that you might have to fix later.

    I feel like these memes of hating everything other than lone coding is because you keep working for toxic companies. Ffs you’re programmers, it’s probably super easy to get another job. It doesn’t have to be like this.

    • Fubber Nuckin'@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      26 days ago

      Ffs you’re programmers, it’s probably super easy to get another job. It doesn’t have to be like this.

      Who’s gonna tell them?

    • rockSlayer@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      26 days ago

      I think QA engineering needs to become more widespread. The “extra pair of eyes” can’t compare to a department of people dedicated to code review and testing.

      • Windex007@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        26 days ago

        You don’t want a department that you throw it over the fence to, you want them embedded on your team. Keep those feedback loops TIGHT bois

      • jol@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        26 days ago

        QA and Code reviews do different jobs. Manual and automated testing will not notice your code is shit, so long as all test cases pass.

    • AggressivelyPassive@feddit.de
      link
      fedilink
      arrow-up
      0
      ·
      26 days ago

      I feel like these memes of hating everything other than lone coding is because you keep working for toxic companies.

      No, it’s because we are working with humans and their deeply flawed organizations. As much as people hate corporations and love startups, both are always a mess. Every organization I’ve seen from the inside is barely functioning. Cruft, interpersonal conflicts, incompetence, or simply very bad market situations.

      Software engineering kind of has to get involved with almost all of that. If you need to get approval from department A and Stacy just keeps changing what she wants, you’ll have to carry that chaos into the development and it will usually percolate through half the engineering department, because hardly any interface is actually a stable attack surface. That means meetings, calls, meetings, reviews, meetings, and fucking Stephen again wants to pitch this weird framework he’s so in love with, meetings, budget calls, because there’s no way, simply changing the field length can take that much work, meetings, …

      • jol@discuss.tchncs.de
        link
        fedilink
        arrow-up
        0
        ·
        26 days ago

        It’s not about corps vs startups. It’s about having processes, good communication, dialogue, empathy. And it’s also your manager’s job to protect the team from externals that keep interrupting and making adhoc requests. If you don’t feel safe in ignoring calls and replying with “I’m busy now, schedule smth today please”, I consider that a highly toxic workplace.