this post was submitted on 04 Oct 2024
192 points (94.9% liked)

PC Gaming

8553 readers
435 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ICastFist@programming.dev 16 points 1 month ago (3 children)

As a dev who does the client talking, sometimes it's really hard to avoid calling the client stupid. One time, while trying to confirm some stuff for a system, the following exchange happened:

M - Ok, so is this field mandatory?
C - Yes!
  * Shows off other stuff, comes back to that first field *
M - Alright, so the user will fill this field, which is mandatory
C - No! That field shouldn't be mandatory!
M - ? But you said it was?
C - No, I didn't!
  * Rewrite my notes, which the client saw me writing in the first place, stating the field is not mandatory. Proceed with the flow, come back to the field *
M - Alright, this field, is it mandatory, yes or no?
C - Yes!

There was also a different client that asked for a number of changes to a system, we did them, then, once he was supposed to test them give the final Ok, he came with "oh, we won't use that flow anymore, everything changed" - My boss chewed him hard and left his request at the lowest priority.

[–] BallsandBayonets@lemmings.world 7 points 1 month ago

In my experience they want the field to be mandatory but don't want anything preventing them from skipping it if they've personally decided to skip it, "just this once."

[–] tabarnaski@sh.itjust.works 4 points 1 month ago

Time spend undoing/redoing stuff and delays caused by clients should always be billed, and contracts should address that.

[–] thefartographer@lemm.ee 4 points 1 month ago* (last edited 1 month ago)

That sounds like one of those "okay, I know you want the field there, so it's mandatory for me to include it, but is it mandatory for your customers to enter values in this field? If your customers can leave the field blank, is that good or bad?"