5

what to do with devs that don't review code?

Comments
  • 2
    Review their salary opportunities (lack of thereof, to be precise).
  • 0
    They write it, why would they want to read it too? Bet you’re going to say “don’t deploy on friday” and “never push directly to prod” next. 😝
  • 3
    🤷‍♂️
  • 1
    @heyheni is that tar and feathers?
  • 1
    Ask them nicely to review while pointing a gun at them. Each time they say no, shoot...lol
  • 0
    Serious question: what do you mean by code review?
  • 2
    Slip in a crypto miner 😉
  • 2
    We have code review and one guy straight approves everything as soon as it hits our version control. Most of us are like, “Stop what are you doing?”

    We have an unspoken rule that nobody merges on his approvals alone. Also his boss won’t bring it up with him because he is a pushover.
  • 1
    Put 'em in a bed with the Captain's Daughter?
  • 0
    @JustThat I might want to start doing that.

    Back to topic, code review sounds good in theory, but the reality is most people want everything done yesterday, and code written in haste is code you're going to hate.

    Just hit approve and have QA find a problem is there is any.
  • 1
    @JustThat ha, that sounds good but I see way too much reasons for that kind of thing to be useless and inefficient when applied to a dev team.
  • 1
    Do you know how many of your co-workers rant about you on devRant @Bobu ? 🤡
Add Comment