3 ms·
slight-OT: Yes, it is. Which is frustrating in itself. In general, I've developed a strategy: Me: "So, what should the program do when XYZ occurs?" Marketing:
by MrGilbert 7y ago
slight-OT: Yes, it is. Which is frustrating in itself. In general, I've developed a strategy:
Me: "So, what should the program do when XYZ occurs?"
Marketing: "Uhm... Dunno, haven't thought about it. I'd decide by, you know, gut instinct. We haven't thought about that yet."
Me: implements a virtual coin-flip using Random.Next()
Once you've done that, it's easier.
- ryandrake 7y agoOr, file a bug for each corner case, mark it release-blocking, and assign to whoever is responsible for the requirements.
- CGamesPlay 7y agoIf you're interested in actually shipping, a more helpful approach is to choose the simplest behavior to implement, notify the requirements person that you've done that, and offer to create a release-blocking bug for the issue if that is unacceptable. Chances are, if the requirements person doesn't have an opinion on what the copy for the dialog should be if the customer is 65+ and it's a Tuesday in a month with 31 days, then it's because that choice doesn't really matter all that much.