3 ms·
Let's define "bad" as the second worst to forth worst engineer in your class of 30 engineering students that made it through. I would say bad engineers tend to
by rightbyte 8y ago
Let's define "bad" as the second worst to forth worst engineer in your class of 30 engineering students that made it through.
I would say bad engineers tend to know they are bad and either tend to go into managing, coordination roles or grab a subset of tasks they get good at, like being the only one on the company working with eg. a specific third party system and doing support and integration for that.
Bad engineers that have worked with the same system for three years are way better with it than super-engineers that have never touched it for at-least a couple of months.
As you said, I have never really had problems with bad engineers messing things up.
EDIT:
Reluctance to hire engineers and saving pennies for a dollar on the other hand have messed up some projects.
- webmaven 8y ago> Bad engineers that have worked with the same system for three years are way better with it than super-engineers that have never touched it for at-least a couple of months. It's when that bad engineer starts protecting "their" turf at the expense of the rest of the org in order to provide themselves with job security that things start to really go south.
- rightbyte 8y agoYe, but not really a big problem where I live where it's a lifo que for firing people. On stack ranking US corps on the other side the Atlantic I imagine it's another story ...