14
ZioCain
343d

In a call with the big boss of the huge company I'm working for:

HER: Yeah, this MUST be in the next release or we better not even release

She's talking about a fucking carousel to let the user know its stuff has been merged, I get the point! It's important, but do you fucking realize that the user is currently NOT EVEN LOGGING IN?

HOW TF IS YOUR PROBLEM WHAT THEY SEE ONCE INSIDE THE PLATFORM IF THEY CAN'T EVEN LOG THE FUCK IN?

FUCKING BUSINESS BITCH JUST SAYING WHAT HAS TO BE DONE AND THEN PRENTEDING SHIT TO ACTUALLY WORK PROPERLY

Comments
  • 1
    I'm always annoyed when stakeholders try to say a feature needs to be block in the next release - as it's almost always possible to release what we have now and then do another release once that important thing is done
  • 3
    Allthough I didn't quite get the problem: is the login feature broken?

    If not then it doesn't get the issue.

    Maybe missing some context.
  • 3
    Given a stable release, the question that always needs to be asked is "Does this release deliver new value to the end user in some way?" It could be a new feature, stability improvements, security improvements, etc.

    If the answer is yes, then there should be almost no reason to hold the release. If the answer is no, then why is there even a release scheduled?
  • 3
    Did she know that user can't even log in currently? The big boss can't possibly know about such things, it's you guys' responsibility to tell her.
  • 0
    @daniel-wu She knew, and she also knew that what was fucked up wasn't an easy fix
Add Comment