• DerArzt@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    Isn’t this t the manager’s fault that those shitty developers are there as well though?

    • spongebue@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      In theory a decent QA team will catch things being done by shitty developers. If your dev and QA is shit, management is shit for letting it happen.

      • DerArzt@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 months ago

        Man I wish we had QAs still at my Mega Corp. They removed the role and saddled development with that responsibility (along with getting rid our our business analysts and putting that also on the engineer’s responsibility list).

    • chaospatterns@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 months ago

      Kind of but it’s not fair to put it all on the manager. Multiple people decided to hire the person. Somebody else approved that code review. People approved the technical design. Why didn’t the tech lead raise concerns with the manager about someone’s under-performance, etc. it’s unfair to just put all blame on the manager.

      The idea of extreme ownership is about not saying “not my problem I won’t do anything” or blaming your reports. It’s about saying I can and should do anything and everything in my ability to fix problems.

    • NotMyOldRedditName@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Maybe over an extended period of time, but that’s not something people get fired for right away. Also bugs are a fact of life in software, and while some developers may ship more bugs than others, work still needs to get done, and it’s often better to try and train and improve an existing employee than fire them too soon.