7

Call me a novice, but isn't the point of a user story to be concise, limited in scope and only concerning one purpose? Kind of like a class should only have one responsibility.

This stupid other reviewer developer comes whining at me saying I broke some shit in my user story and that I need to fix it. The weirdest part is that I didn't break anything. I wrote all my tests, they all passed and yep, this guy has the nerve to come and say that I broke other shit. Well genius, if it's OTHER SHIT, then it belongs as a bug in ANOTHER STORY. What the fuck man, seriously.
A few minutes of debugging later, I found out it was someone else who broke some code earlier on a piece that was part of my part of the application.

Why are others so quick to blame? This is unprofessional. OMG I DISCOVERED AN ERROR, YOU'RE PROBABLY THE ONE TO BLAME BECAUSE YOU'RE AN IGNORANT GUY BECAUSE YOUR TITLE IS JUNIOR DEVELOPER!
Right.

Companies like these, people, have bad communication. Bad companies.

Comments
  • 0
    Say what you want, but you gotta admit:

    1) Although he was wrong, he was absolutely certain you fucked up.

    2) You were not.

    I get it. I hate having to explain someone else's fuck-up, too. Get better so next time someone tries to pull that crap on you, you can refute their args and tell them to go fuck themselves right there and then.
  • 0
    @telephantasm The sad part is that he wasn't certain but he liberally decided to spread around #slack that I somehow must have fucked up. He's also technically less capable than me, which is even more offending. The most fun part of all: he's a front end developer.
Your Job Suck?
Get a Better Job
Add Comment