CSCareerQuestions

947 readers

12 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 8 months ago by testeronious@lemmy.world to c/cs_career_questions@programming.dev

21 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

[–] kreynen@kbin.social 4 points 8 months ago* (last edited 8 months ago)

Beware of the "whatever" aproach.

Many years ago I was brought into a project where many variables where named after cars. Before I got there, if the team couldn't agree on a name, they'd use a car and move on. There was also a module in the code call "bucket". Didn't have a logical place to put a function? Add it to the bucket.

I'm sure they saved a lot of time not discussing what to name things up front, but by the time there was enough turnover on the team to change the variables and rewrite, it took months to fix.

Another, more product approach is to ask the "variable naming guy" to write up a naming policy document that would result in the names he has been suggesting. If there is logic associated his side of the "argument" it should be easy to document.

Have everyone on the team discuss and approve the policy. Hopefully you never spend time in a meeting arguing about this again.