3 ms·
>Avoid snarking (pithy, unproductive, sniping comments) On the other hand... 9 out of 10 really skilled devs/engineers or profs that I met had tendency to be
by tester756 5y ago
>Avoid snarking (pithy, unproductive, sniping comments)
On the other hand...
9 out of 10 really skilled devs/engineers or profs that I met had tendency to be kinda snarky, especially when somebody's trying to do bullshit
Is lack of subtle/direct snarkiness a good thing?
It's like putting constrains on language/tools to express yourself, maybe too harshly?
Maybe it's considered normal in "cultures" where people are more straightfoward
- diob 5y agoI've had the opposite experience, and thus worked to make my team a safe place for folks where they don't feel the need to hide from snarkers (who often are trying to put themselves above others by pulling everyone else down). As a senior engineer / team lead, I really have no patience for bad behavior. Directness is the opposite of snark. If you think something is a bad idea, propose an alternative. Or work with the person. Anyone can throw out snark, it takes a "really skilled" person to do something productive instead.
- smoldesu 5y agoCompanies hire you because you're opinionated, and they retain you because you're obedient. You can mix and match the two to reach whatever desired effect you want, but them's the rules.
- lastofus 5y ago> Is lack of subtle/direct snarkiness a good thing? It's quite possible to call out and dismantle bad ideas, without making it reflect poorly on the originator of the idea. A snarky tone can have an underlying implication that the idea was so bad, the idea originator is not even worthy of a respectful reply. Maybe this is warranted in some cases (e.g. a bullshitter bullshitting), but in the case of coworkers/contributors with good intent, this is just unnecessary abrasiveness.