Timeline for Star developer didn’t get a promotion because he isn’t a people person, so he has scaled back his contributions. How can I motivate him?
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2019 at 3:31 | comment | added | user29234 | > He cost the company tens of thousands of dollars (according to OP) by being unavailable over the weekend... Were they paying him over the weekend? If not this is the companies own damn problem. | |
| Dec 3, 2019 at 22:46 | comment | added | Cypher | Let's stop with the fake outrage already. This is not sabotage. He or she is simply following directions to the T due to motivational issues. There's a massive difference between the two. | |
| Dec 1, 2019 at 17:39 | history | edited | Felipe Pereira | CC BY-SA 4.0 |
added 1333 characters in body
|
| Dec 1, 2019 at 9:59 | comment | added | user110557 | @Ángel, come on, please, everybody working IT knows sometimes, most of the times, specs aren't written to perfection, for a whole lot of reasons. It is expected from any developer, not just star one, that, when faced with such an ambiguity, they do a decent amount of work to verify such details. No one's expecting "above and beyond call of duty", but emailing/Slack-ing you manager saying "To which table other than [Not_this] do we put the data?" is the bare minimum. I'd personally fire any developer who didn't do this bare minimum, with cause! Cause being sabotage. | |
| Nov 30, 2019 at 23:32 | comment | added | Mavrik | Doing ones job without going above it is not sabotage. That word doesn't apply here. You're not entitled to extra work from your employees if you don't reward them. | |
| Nov 30, 2019 at 23:21 | comment | added | Felipe Pereira | @Ángel the difference between an honest and a deliberate mistake is not minor | |
| Nov 30, 2019 at 23:18 | comment | added | Ángel | In that case you should begin by firing the people that is writing bad task specs, not those following them to the letter. He is no longer going far and beyond to fix badly worded specs (which I guess isn't supposed to be part of his job), but that's quite different than sabotaging the company. Unless you consider that you used to have lots of sabotages that this employee avoided. | |
| Nov 30, 2019 at 18:35 | comment | added | Felipe Pereira | @donjuedo this person is even trying to make the company loose employees by suggesting open positions elsewhere, put that with the rest and it sounds as clear sabotage to me | |
| Nov 30, 2019 at 18:33 | comment | added | Felipe Pereira | @SolarMike I believe OP isn’t adding the developer’s vindictive behavior into his costs equation, just the good part, how he used to work, that is in the past | |
| Nov 30, 2019 at 17:28 | comment | added | WGroleau | Knowing of a flaw in code and taking action to hinder getting it fixed IS sabotage. | |
| Nov 30, 2019 at 17:03 | comment | added | donjuedo | Using the word "sabotage" is not a fair characterization of the dev's actions. It's a bit like labeling terrible people as terrorists, when quite literally, they are not. | |
| Nov 30, 2019 at 16:33 | comment | added | Solar Mike | OP made it clear he does not want to fire this person due to the cost of the loss of knowledge and time needed to get back up to speed. | |
| Nov 30, 2019 at 16:10 | history | edited | Felipe Pereira | CC BY-SA 4.0 |
added 5 characters in body
|
| Nov 30, 2019 at 16:04 | review | First posts | |||
| Nov 30, 2019 at 18:23 | |||||
| Nov 30, 2019 at 16:03 | history | answered | Felipe Pereira | CC BY-SA 4.0 |