4
cb219
5d

In an email conversation the client asks for clarification about a behavior that exists that was never questioned for months. Upon clarification of said behavior the client claims that the feature is supposed to be totally different or they claim to remember that we agreed upon the new behavior. Our team cannot remember it was ever mentioned nor was it documented as a request. The change was rejected with a kindly written "fuck you there was never such a request" and "this use case was never mentioned, this is some new info". What a pleasure!

Comments
  • 1
    Good outcome.
  • 3
    Lesson for the client: Write down requirement or stfu.
  • 2
    Yeah, bossman likes to use BDD/give+when+then tests and writes those with the client
  • 1
    @BordedDev this is a good pattern but as it is with everything, it becomes annoying when you apply it everywhere unconditionally.

    I read a lot of needlessly retarded test code just because the dev who wrote it felt like they needed to stick to this pattern because threatened with a gun to their head.
  • 1
    @Lensflare Oh did he also work with bossman - he applies the BDD thing everywhere unconditionally and will bug you if you don't
Add Comment