Can't remember how many times I had to change project structure just because they provided wrong/misleading/half-ass requirement

  • 0
    E) All the above!
  • 4
    Can't be C and D because if you are using that convention 0024 would be "Two Zero one Two one Four", similarly for D. We can argue for B by saying it should be "Two Zeroes Two Fours", So, A is the safest guess.
  • 6
    @theabbie if you think you just argued your way out, think again. If anything, you made it much more complicated. And that's how it ends up.
  • 2
    @Aitkotw Answer is A anyways, using unnecessary logic is a waste of time.
  • 6
    @theabbie as a programmer thinking logically is the way. Although, for clients, there's no logic, they have wague idea of what they want and you fight with their perception and make calculated assumptions.
  • 1
    @Aitkotw I am talking about this specific question. This one is supposed to be ambiguous. we don't have to use logic here.
  • 1
    at least you know it's not 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4
  • 2
    @theabbie requirements were written by Jamie the intern who always came in at work high as fuck. It was less expensive than hiring a PM and a PO.
  • 3
    This is why project managers/business analysts need to know exactly how to translate a client requirement into actionable development requirements. All the damn PMs at my company are glorified note takers so this is what we devs get all the time.
Add Comment