3 ms·
Do you work with people who are experts in things you are not? When one of them raises a concern from the field they're an expert in, you generally must take it
by musingsole 6y ago
Do you work with people who are experts in things you are not? When one of them raises a concern from the field they're an expert in, you generally must take it as a given that the issue is real and must be addressed, as the expert raised it and wouldn't have otherwise. Your role might be to point out how the presented fixes to the issue might/will cause issues in your field of expertise, but it'd be pretty unprofessional to question the validity of the other expert's designated problem.
- mmm_grayons 6y agoSorry, who exactly is the expert here that shouldn't be questioned? While I generally respect experts' opinions, I also find it reasonable to question them when they don't pass the smell test.
- musingsole 6y agoI can respect your smell test if you can respect that it's highly susceptible to Dunning-Kruger and the various mishaps of not knowing what you don't know.
- mmm_grayons 6y agoYou still didn't tell me who these "experts" are, though it seemed you were referencing several in a prior comment, so I'm unsure how to address that point. I'd of course respect the opinion of an expert, and I'd recognize that I have a very good chance of being wrong, but that makes it even more important to question things. If I'm right, we come to a better conclusion; if I'm wrong, I learn something.
- musingsole 6y agoI didn't answer your question because it's rather obvious. Thanks for the downvote though!
- mmm_grayons 6y agoHN doesn't permit users to downvote replies to their comments, so you can be sure that wasn't me. Maybe it's obvious to you, but I'm not sure how one qualifies as an expert in the necessity (or not) of removing the word "master" from github branches. Would you please elaborate?