CSCareerQuestions

910 readers

1 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Follow the programming.dev site rules
Please only post questions here, not articles to avoid the discussion being about the article instead of the question

Related Communities

!programming@programming.dev - a general programming community
!no_stupid_questions@programming.dev - general question community
!ask_experienced_devs@programming.dev - for questions targeted towards experienced developers

Credits

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

ericjmorey@programming.dev

odium@programming.dev

How do you deal with colleagues that argue 45 minutes on a call about a variable name? (lemmy.world)

submitted 7 months ago by testeronious@lemmy.world to c/cs_career_questions@programming.dev

15 comments fedilink hide all child comments

This dude is extremely persistent about having irrelevant things his way, and when he doesn't get it, he acts as if it were a personal attack. Do you guys have any argument or method to deal with this kind of people?

I used to say "whatever" and let him have things his way, but as I got more experienced I started to listen more to his arguments and basically respond "this makes no sense" (not with those exact words, of course).

you are viewing a single comment's thread
view the rest of the comments

[–] xmunk@sh.itjust.works 11 points 7 months ago

100% - elevate though not to their manager.

I often open up the discussion to a wider channel if me and a coworker can't compromise on a technical discussion and poll other engineers.

If it's not a technical discussion (I consider naming to be technical if it's "important" like a wide reaching functiona name) then I'll actually elevate to my manager - they'll consider it and vet it before elevating further which might involve talking to the dev or to the dev's manager.

If it's a real pattern and somebody is being an ass consistently you'll really want to go through your manager because it's likely that if you're locking horns that much someone may need to switch projects.