4 ms·

The incentive to not act like the slackers is how it impacts your "network". It's pretty insufferable to work with these people, when the success of your projec

The incentive to not act like the slackers is how it impacts your "network". It's pretty insufferable to work with these people, when the success of your project depends on them or their team for whatever reason. If our team is hiring and I see a former coworker got laid off who was a slacker I won't put in a referral for them. I guess it won't impact them much, because tech is still growing and demand exceeds supply, but at least it will keep my work slightly more enjoyable. A job well done is it's own reward.

selcuka 3y ago
From the article: > [they] say their new goal is to be “perfectly mediocre.” Note that mediocre is not the same as slacker. It is impossible to distinguish a genuinely mediocre developer from an intentionally mediocre one, so no, it won't impact their network unless they are really careless and tell everyone that they can in fact perform better. Do you stop talking to a colleague because they have never found a security vulnerability and fixed it?
- kapp_in_life 3y ago
  The 4 case examples in the article are absolutely slackers. Not mentioning a 6 figure cloud inefficiency, or knowingly shipping bugs, or leaving 100's of diffs for compiler warnings and not publishing them. You're right about not being able to tell a genuinely mediocre developer from an intentionally mediocre one... unless they tell on themselves like the above did. >Do you stop talking to a colleague because they have never found a security vulnerability and fixed it? This feels like a reach? Obviously not, I'm perfectly cordial to everyone I work with. If they find a security vulnerability, and don't fix or even bother reporting it then I'll obviously think less of them and probably not give them a referral. But I'd never hold it against someone for not identifying one or accidentally shipping one.
  - selcuka 3y ago
    > This feels like a reach? Obviously not, I'm perfectly cordial to everyone I work with. Sorry if you were offended, but I didn't mean that you do. Nobody does. That was a rhetorical question to emphasise my point.

selcuka 3y ago

From the article: > [they] say their new goal is to be “perfectly mediocre.” Note that mediocre is not the same as slacker. It is impossible to distinguish a genuinely mediocre developer from an intentionally mediocre one, so no, it won't impact their network unless they are really careless and tell everyone that they can in fact perform better. Do you stop talking to a colleague because they have never found a security vulnerability and fixed it?

kapp_in_life 3y ago
The 4 case examples in the article are absolutely slackers. Not mentioning a 6 figure cloud inefficiency, or knowingly shipping bugs, or leaving 100's of diffs for compiler warnings and not publishing them. You're right about not being able to tell a genuinely mediocre developer from an intentionally mediocre one... unless they tell on themselves like the above did. >Do you stop talking to a colleague because they have never found a security vulnerability and fixed it? This feels like a reach? Obviously not, I'm perfectly cordial to everyone I work with. If they find a security vulnerability, and don't fix or even bother reporting it then I'll obviously think less of them and probably not give them a referral. But I'd never hold it against someone for not identifying one or accidentally shipping one.
- selcuka 3y ago
  > This feels like a reach? Obviously not, I'm perfectly cordial to everyone I work with. Sorry if you were offended, but I didn't mean that you do. Nobody does. That was a rhetorical question to emphasise my point.