this post was submitted on 04 Oct 2024
190 points (94.8% liked)

PC Gaming

9516 readers
1504 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, within reason.
  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 2 years ago
MODERATORS
all 36 comments
sorted by: hot top controversial new old
[–] [email protected] 106 points 4 months ago* (last edited 4 months ago) (3 children)

There's a million reasons why in the professional world it's common for developers to have some sort of personnel buffer between them and their userbase.

[–] [email protected] 64 points 4 months ago* (last edited 4 months ago) (3 children)

My dad once called a client stupid for continuing to ask for a feature that made no sense. Technically, he asked "why would you want that? What, are you stupid?"

Then he got chewed out by his boss who told him that clients who ask questions aren't stupid. My dad told her that the client asked a stupid question. His boss told him that it wasn't a stupid question, that she thought it was a very good question from an uninformed client. So then my dad called his boss stupid.

Then he got sent to sensitivity training. He completed the mandatory hours, got his certificate, and a letter recognizing his difficulties with reasonable discourse vs arguing and calling people stupid. The instructor recommended that my dad shouldn't interface directly with any clients anymore. So they made my dad's younger brother his supervisor since he could translate my dad's comments and questions into more diplomatic terms.

ETA: this story was from the '80s. He got better over time.

[–] [email protected] 69 points 4 months ago (5 children)

That’s a bad look. He may be smart but that’s really unprofessional. You call them whatever you want behind their backs. You don’t insult clients to their face no matter how stupid they are. He’s lucky he kept his job.

[–] [email protected] 27 points 4 months ago (1 children)

You don't insult clients, period. You never know who is listening, who will rat you out, etc. Worse yet, you might send that email to the client too by mistake and get fired.

[–] [email protected] 6 points 4 months ago* (last edited 4 months ago)

you might send that email to the client too by mistake and get fired

That's an unfair dismissal lawsuit: https://www.independent.co.uk/news/uk/smith-oxford-b2616638.html

[–] pancakes 21 points 4 months ago

Also it shows a lack of empathy. 9/10 times it's not that the client is dumb, but that they're unfamiliar with processes, recieved conflicting information, have other requirements you don't know about, have personal things going on, or an endless host of other factors.

It could even be that you didn't do your job properly in explaining or walking them through. Like if I was a customer and the client-facing representative was so fragile that he'd blow up in my face over a minor inconvenience, I probably wouldn't feel comfortable asking for something explained a second time.

[–] [email protected] 16 points 4 months ago (1 children)

My father was an incredible genius with a terrible temper. He softened up over time and eventually would talk to clients politely. And then he died. The end.

[–] [email protected] 12 points 4 months ago

See what being polite to clients gets you...your dad had it right in the beginning calling it how he sees it!!!

[–] [email protected] 8 points 4 months ago

Some people can deal with stupid people, some can't. Manager is stupid to not know the difference.

[–] [email protected] 8 points 4 months ago (1 children)

Not a disagreeing with you but I worked with few engineers like this. This is the reason for project managers and sales people as a buffer with clients. They kind of made that joke in Office Space.

https://youtu.be/m4OvQIGDg4I?Oosz1OyOb9lRBLKT

[–] [email protected] 3 points 4 months ago (1 children)

Meanwhile, I'm a dev who can actually talk to people, but I still have to go through 5-6 layers of business people mangling what the user said...

[–] [email protected] 3 points 4 months ago (1 children)

I can 100% understand that frustration of not cutting out the middle man. In some cases it would be highly beneficial. I remember the story where they customer wanted to have the back of passenger plane open up, sales guy sold it, engineers did it without question. At the end someone asked why, it was because the customer wanted to quickly exchange air.... People loss their minds but management was too busy counting the money.

[–] [email protected] 3 points 4 months ago (1 children)

It's as if they don't remember playing telephone when they were kids.

[–] [email protected] 1 points 4 months ago

"Hey boss, @[email protected] says they don't like the new telephones? Says they're made for kids or something."

@[email protected]: I still don't know why I was fired... The boss kept telling me to shove the phone system? Maybe they meant push? Was I supposed to work on some branch of the phone system?

[–] [email protected] 16 points 4 months 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.

[–] [email protected] 7 points 4 months 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 4 points 4 months ago

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

[–] [email protected] 3 points 4 months ago* (last edited 4 months 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?"

[–] [email protected] 29 points 4 months ago

posts a selfie while outdoors

why aren't you finishing the game i want to play?

[–] [email protected] 10 points 4 months ago (1 children)

I'm glad he basically confirmed Half Life 3 by talking about lambda.

/s

[–] [email protected] 3 points 4 months ago

Lambda lambda lambda and...?

Omego-Muuuuuu....