• jol@discuss.tchncs.de
    2·
    5 months 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.

    • rockSlayer@lemmy.world
      0·
      5 months 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.

      • jol@discuss.tchncs.de
        1·
        5 months 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.

  • kaffiene@lemmy.worldEnglish
    1·
    5 months ago

    Coders who complain about documenting and tests are coders I don’t want to work with

  • MisterFrog@lemmy.world
    1·
    5 months ago

    Problems caught early are much easier to fix than problems caught later. This applies to any project (I’m not a programmer, but an engineer in the traditional sense).

    Just “doing it” without coordination and review is a great way to waste a bunch of effort down the line with re-work.

    Edit: typo