3 ms·

My manager is well aware and pissed. I only really became aware after getting pulled onto the project a little over a month ago, seeing how little existed follo

by donatj 3y ago

My manager is well aware and pissed. I only really became aware after getting pulled onto the project a little over a month ago, seeing how little existed followed by being able to get basically zero feedback on how things should fit into the project. It was easy to not see (for me) when we were supposed to be heads down on separate projects. We’re given a lot of rope when it comes to what we’re working on so other than hearing about what others are working on in standup, often I’ll never see it. That said, I’m not sure he knows what to do about it. I’ve worked under him for over a decade and this is the first time we’ve had a real problem like this. I suspect he’s working with his own manager on how to handle it.

ShamelessC 3y ago
Generally the employee should be given a warning, then reprimanded on repeat behavior, then fired. Ideally the manager would have noticed this without you having to "rat out" the employee - that's the manager's job, not yours. This stuff isn't really unheard of outside of tech. It's common even. Is it shitty? Sure. But the rest of the world deals with it and makes far less money on average. I've seen this same inability to punish incompetence in my own coding career at [insert large retailer]. No one got in trouble despite my protests but rather were moved around the organization. Alongside lots of other signs, it was clear to me that the tech work being done there wasn't important to many or any people who would be using it. It seemed to mostly be about the value of the company's stock.
- donatj 3y ago
  For what it is worth I did not have to rat them out. By the time I got pulled onto the project my manager had figured it out. I didn’t know the extent though before complaining about lack of reply/feedback from the dev, at which point I started looking at the commits across projects see what he had been doing. Not much so it seems. In the time I have been here we’ve fired three people, but it was all for much worse. We’re not untouchable but it takes a lot. I would honestly far rather he just get back on track. We’re already short staffed and it’s becoming harder and harder to hire devs in our tech stack.
- scruple 3y ago
  > Alongside lots of other signs, it was clear to me that the tech work being done there wasn't important to many or any people who would be using it. It seemed to mostly be about the value of the company's stock. I worked for a medical technology startup for 8.5 years and the tech work really, truly mattered. Then we were acquired by a huge public company and I hung on to see what might happen. Before the end of the first year it was apparent that all that was happening is verbatim your last sentence here. I left shortly after. I have some former colleagues who have hung on and they report that they have literally nothing of value to do today. They think the company is playing chicken with them, more or less, and hoping that they'll get bored out and leave.

by donatj 3y ago

ShamelessC 3y ago

Generally the employee should be given a warning, then reprimanded on repeat behavior, then fired. Ideally the manager would have noticed this without you having to "rat out" the employee - that's the manager's job, not yours. This stuff isn't really unheard of outside of tech. It's common even. Is it shitty? Sure. But the rest of the world deals with it and makes far less money on average. I've seen this same inability to punish incompetence in my own coding career at [insert large retailer]. No one got in trouble despite my protests but rather were moved around the organization. Alongside lots of other signs, it was clear to me that the tech work being done there wasn't important to many or any people who would be using it. It seemed to mostly be about the value of the company's stock.

donatj 3y ago
For what it is worth I did not have to rat them out. By the time I got pulled onto the project my manager had figured it out. I didn’t know the extent though before complaining about lack of reply/feedback from the dev, at which point I started looking at the commits across projects see what he had been doing. Not much so it seems. In the time I have been here we’ve fired three people, but it was all for much worse. We’re not untouchable but it takes a lot. I would honestly far rather he just get back on track. We’re already short staffed and it’s becoming harder and harder to hire devs in our tech stack.
scruple 3y ago
> Alongside lots of other signs, it was clear to me that the tech work being done there wasn't important to many or any people who would be using it. It seemed to mostly be about the value of the company's stock. I worked for a medical technology startup for 8.5 years and the tech work really, truly mattered. Then we were acquired by a huge public company and I hung on to see what might happen. Before the end of the first year it was apparent that all that was happening is verbatim your last sentence here. I left shortly after. I have some former colleagues who have hung on and they report that they have literally nothing of value to do today. They think the company is playing chicken with them, more or less, and hoping that they'll get bored out and leave.