68

Dev: So how do you want this feature fixed?

Manager: It should work how it worked before.

Dev: I'm new to this feature, I don't know how it worked before or what is broken about it.

Manager: Well just make it work like it worked before.

Dev: I DONT KNOW HOW IT WORKED BEFORE THAT IS WHY I AM ASKING YOU. PLEASE TELL ME SO I CAN DO MY JOB.

Manager: Just how it worked before!

Dev: ...

Manager: ...

Dev: fuck you

Comments
  • 5
    Well.

    Not sure... Maybe waste 5 days emailing with people about "how that feature worked before"?
  • 7
    @magicMirror totally that...

    And even then, I manage to get 5 different stories.

    + on top of that, the end user tells at that point that they don't use the feature because it was not working as they wanted before...
  • 5
    but steel is heavier than feathers
  • 3
    git checkout <someOldCommit>

    and test how it was back then.
  • 5
    Looks like a fractal fuckup. You aren't able to find out what a feature does?! Your manager can't articulate what he wants! And there are literally no actual users whom you could ask?

    If you actually aren't able to research it yourself, just set the ticket as "information requiered" and wait till someone who actually uses the damn thing provides you with an actual bug report.
  • 0
    @Oktokolo The noose tightens, death approaches... 💀
  • 3
    @fullstackchris: I doubt it - you don't seem to be in an environment, where anyone wouldn't botch a hangman's knot...
  • 2
    Get into the git hub history and roll it back to as early as possible.
    They’ll get exactly what they asked for.
  • 3
    Well... You were told to bring it back to how you know it used to work before... And as far as you know about this, it never worked, so just deleted it 🔥
  • 2
    @Oktokolo hahaha I can just see it.
    Knot spec: make it work like in the old days. You know like you can see in the movies...

    The noose tightens, the knot unravels.
  • 1
    @hjk101: Yeah, it's funny unitl you realize that most people are botchers and you probably have to deal with their "output"...

    Learn how to tie a hangman's knot now! Lest you botch it when trying to finally get rid of a botcher!
  • 1
    I felt that
  • 1
    Shocker to no one: how it worked before was the result of a bug, not a feature.
  • 2
    Manager Dev
  • 1
    Times like these I like to harness the common hatred of meetings. Schedule a meeting for a few days from now with all stakeholders to discuss documenting the previous behavior. Add in that it is unclear from the source history when the feature was “broken”. You’ll hopefully get one of the following: 1) Nevermind, it’s not that important, 2) Hey, here’s an old email on how it’s supposed to work, can we cancel the meeting?, or 3) You have the meeting and actually get an answer.
Add Comment