Re:Amazon CEO reportedly told remote employees: It’s probabl...
by sokoloff on Monday August 28, 2023 @08:52PM
(#37302211)
Tabs vs spaces, braces on the line above or a line by themselves, allowing implicit true/false vs requiring a leading 0 != in c/c++, function naming conventions, documentation system conventions, etc., etc. Sure, you could quit every time you disagreed with any of those decisions, but that seems like a lot of wasted effort and time. For all of those, I could disagree and commit to working collaboratively on the team that had made a decision other than the one I preferred.
[ Parent
| on HN ]
Re:Amazon CEO reportedly told remote employees: It’s probabl...
by dekhn on Monday August 28, 2023 @09:03PM
(#37302306)
Disagree and commit isn't about minor style guide details.
It's about making major strategic decisions that affect lots of people.
(I should have thought this would be obvious from context)
Re:Amazon CEO reportedly told remote employees: It’s probabl...
by sokoloff on Monday August 28, 2023 @09:19PM
(#37302386)
Disagree and commit is ideally suited for something like the tabs vs spaces or other style guide debates where there's no obviously/universally best answer. It's more important that all devs in a given file (at least) are using the same convention and people have different opinions about it. Have the discussion (the time to disagree), make and publish a decision, expect everyone to commit to the made decision.
Every time the style guide says something that you didn't like, that you argued against, and you vigorously comply anyway, you've just disagreed and committed. Like you're supposed to as a professional in minor matters.