46

Dev: Your PR only addresses a quarter of the ticket

Dev2: *limps a commit so that now 1/2 of the ticket is addressed and creates a new PR for a separate ticket*

Dev: Your original PR only addresses half of the ticket

Dev2: *limps a commit so that now 3/4 of the ticket is addressed and creates a new PR for ANOTHER new ticket*

Dev: Your original PR only addresses 3/4 of the ticket

Dev2: *limps a commit so that now all of the ticket is addressed but two new bugs are introduced and creates a new PR for ANOTHER new ticket*

Dev: Your original PR introduces 2 new bugs

Dev2: *limps a commit addressing one of the two new bugs and creates a new PR for ANOTHER new ticket*

Dev: Your original PR still has one bu—

Manager: WOW GOOD JOB DEV2 THAT’S 5 PRs TODAY AMAZING! Dev you need to pickup the pace, you only have 2 PRs so far today. And get these PRs from Dev2 QA’d fast. He’s a rockstar!

Dev: …

*The 4 other PRs turned out to be equally dogshit*

Manager: Hey hurry up with QA, you’re holding Dev2 back!

Dev: …

Comments
  • 4
    I’d say leave this place if possible.
  • 3
    Why did Dev push Dev2 to do anything ?
  • 1
    @-red Dev is the senior and accountable to the success of the project
  • 2
    Well... maybe some day managers will understand that you cannot measure a dev teams output by counting tickets or prs
  • 0
    Tbh sounds like that ticket is too big
  • 0
    Both devs are clueless. A principal would just rubber stamp that shit
  • 0
    So why do managers make more again?
Add Comment