4 ms·

The unfair thing in the scenario you describe is the employee choosing to upskill while they continue to do their jobs? And not the company firing them for spea

The unfair thing in the scenario you describe is the employee choosing to upskill while they continue to do their jobs? And not the company firing them for speaking their mind - giving them 3 months of runway to switch careers in a situation OP already said felt like a shit job market? Micromanaging employee time is one of the worst signs of a toxic company culture. And definitely not a sign of an efficient one

v3ss0n 2y ago
Op is not upfront about the toxicity situation to their management.And he haven't said anything about how toxic it is. > Micromanaging employee time is one of the worst signs of a toxic company culture I agree micro managing alot is bad but I don't agree it is toxic. I agree if leadership knows nothing about software engineering and microing it it is bad. There's always two sides. I had seen projects fail because developers are doing what they want with their time, doing things unrelated to current project and end up missing delivery deadlines. I had seen company fail because they don't say anything to their developer because they afraid their developer will feel bad. I had saved client projects by joining in and driving their team to their potentials. There's nothing rude or toxic about it. Unless OP provide more details we can't really know if his company really toxic or not. If job market is shit, build something in your own time, take ownership, make it grow and showcase it. A good C++ dev can learn new things so much faster than others.
- codingdave 2y ago
  If you have saved projects by coming in and micromanaging the devs... are you sure that was the only way to incentivize them to stay focused? And are you sure that they appreciated being micro-managed and did not think it rude and toxic? Because the success of a project and the toxicity of its leadership are orthogonal to each other. It sounds like you are coming from a perspective that if the business succeeds, the environment must not be toxic, which is sadly not at all true.

v3ss0n 2y ago

Op is not upfront about the toxicity situation to their management.And he haven't said anything about how toxic it is. > Micromanaging employee time is one of the worst signs of a toxic company culture I agree micro managing alot is bad but I don't agree it is toxic. I agree if leadership knows nothing about software engineering and microing it it is bad. There's always two sides. I had seen projects fail because developers are doing what they want with their time, doing things unrelated to current project and end up missing delivery deadlines. I had seen company fail because they don't say anything to their developer because they afraid their developer will feel bad. I had saved client projects by joining in and driving their team to their potentials. There's nothing rude or toxic about it. Unless OP provide more details we can't really know if his company really toxic or not. If job market is shit, build something in your own time, take ownership, make it grow and showcase it. A good C++ dev can learn new things so much faster than others.

codingdave 2y ago
If you have saved projects by coming in and micromanaging the devs... are you sure that was the only way to incentivize them to stay focused? And are you sure that they appreciated being micro-managed and did not think it rude and toxic? Because the success of a project and the toxicity of its leadership are orthogonal to each other. It sounds like you are coming from a perspective that if the business succeeds, the environment must not be toxic, which is sadly not at all true.