Hello again, I’m in a situation where the one the senior devs on my team just isn’t following best practices we laid out in our internal documentation, nor the generally agreed best practices for react; his code works mind you, but as a a team working on a client piece I’m not super comfortable with something so fragile being passed to the client.

He also doesn’t like unit testing and only includes minimal smoke tests, often times he writes his components in ways that will break existing unit tests (there is a caveat that one of the components which is breaking is super fragile; he also led the creation of that one.) But then leaves me to fix it during PR approval.

It’s weird because I literally went through most of the same training in company with him on best practices and TDD, but he just seems to ignore it.

I’m not super comfortable approving his work, but its functional and I don’t want to hold up sprints,but I’m keenly aware that it could make things really messy whenbwe leave and the client begins to handle it on their own.

What are y’alls thoughts on this, is this sort of thing common?

  • pink@programming.dev
    link
    fedilink
    arrow-up
    29
    ·
    1 year ago

    It shouldn’t be up to another engineer to fix their PRs. They wrote the code, they are responsible for making sure it is in a state to merge. If it’s not, request changes and move on to your work.

    • DAVENP0RT@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      Yeah, we comment in places where we see issues, leave tasks, and just mark the PR as “needs work.” I ain’t touching code in a branch that’s not owned by me.

    • Ismay@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Soooo much. It’s the biggest of red flags to have to fix other’s reviews.

      Maybe take it up with managment. Those kind of profile are a hinder for every other devs that are working with them