• soggy_kitty
    link
    fedilink
    arrow-up
    8
    ·
    11 months ago

    To be honest, sometimes shit code is 100% the Devs fault. I’ve witnessed it happen with other teams in my own company.

    Let’s just say it was unavoidable to report it

    • SpaceCowboy@lemmy.ca
      link
      fedilink
      arrow-up
      6
      arrow-down
      2
      ·
      11 months ago

      Management could implement a code review process to avoid this.

      Software development isn’t a brand new field anymore. Most problems are well known and therefore have well known solutions. So it pretty much always comes down to management not wanting to implement the known solutions to the problems because its easier to blame the devs.

      • soggy_kitty
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        11 months ago

        They did, that’s why I said “team” in my response, however I will elaborate for you.

        two Devs must review and one dev lead has admin rights to push to protected branches. Problem is when the whole team is not meeting expectations and they all jerk off eachothers bad code.

        My team reviews internally just like they did, the issue isn’t the review process. At a professional level you should trust your peers therefore the issue was the hiring and/or training process