Just had some requirements through for a query that a customer has specified.

“Set the value to 1 if the Outcome is not Complete or Cancelled or NULL”

This could be variously interpreted as:

“if the Outcome is NOT Complete and NOT Cancelled and NOT NULL”

Or “if the Outcome is NOT Complete, and NOT Cancelled, or IS NULL”

Or perhaps even “if the Outcome is NOT ‘Complete or Cancelled’ or IS NULL”

Obviously I’ll go back to them for clarity, but it’s a wonder why so often “bugs” arise based on interpretation of specifications.

  • Quicky@lemmy.worldOP
    link
    fedilink
    arrow-up
    7
    ·
    5 months ago

    Cheers yeah, that is standard usually. I was just having a whinge rather than asking for a solution. In this case the customer was trying to preempt having to complete a change request form (similar to what you’ve described) and get the relevant sign off etc, and had emailed over a “minor alteration” to an existing request, for which they should know better at this stage of the project.

    • tiramichu@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      Haha yeah, fair enough. Applogies for turning your deserved whinge into a serious question.

      Wrangling annoying customers is always the most annoying part of the job isn’t it. How nice it would be to spend more time programming…