3 ms·
You're describing a scenario where an incompetent manager is both clueless about the technology and doesn't spare even a few minutes to do their job. I'm sure
by khazhoux 4y ago
You're describing a scenario where an incompetent manager is both clueless about the technology and doesn't spare even a few minutes to do their job. I'm sure that happens, unfortunately.
But, the point that I was making was simply that trust is an essential part of software work, and people who pride themselves on doing only the minimal amount of work, risk messing up this system of trust for everyone else. We all want a manager who trusts us when we say a problem is hard and it will take time. And managers want engineers who when they say they're working on a problem, they're actually putting time and effort into it.
In the (hopefully very rare) case where an engineer puts in a measly amount of effort during the week but pretends they're hard at work, this trust is broken, and in the worst outcome, the manager or company overcorrects and it becomes a shitty place to work.
- betwixthewires 4y agoYeah, but this is where knowing your people comes in. If you've got a bullshitter on your team and you know it, you need to be figuring out how to get them not just off your team, but out of the company. If you don't know it, you're not doing your job. This can be hard I know with the way contracts are, labor laws, severances, and often times it is easier to just offload the employee to another team, which compounds these problems and makes them systemic. That's the only sticking point I think that takes the blame off management. It should be easier to fire bullshitters.