> I am thinking is in IT industry 'too clever and hardworking' the same as 'stupid and hardworking'?
The thought of someone stupid turning out the most code in a team used to make me shudder. But then I got some not so bright people on my team.
It's true that stupid left to their own devices turns out terrible code. But they have their strengths. Janitors for example are often classed as stupid, but a stupid and hardworking janitor will do a far better job than of the other types.
The key insight (and this was pointed out to me by of all people someone in marketing, designing campaigns to make products appeal to certain crowds), is janitors like routine. I guess stupid doesn't like to be made to think, they like to do what they excel at, which is doing. So the key to making it work is the smart (and preferably lazy) people design the routine, and the stupid execute it. You can rely on stupid and hardworking to do it consistently and quickly.
In programming terms, this means you need strong coding rules, lots of examples, thorough reviews which takes enormous amount of patience. A smart programmer will cafe at the oversight required, as it prevents exploration of ideas. Give stupid that and something remarkable happens - they produce very good code. Why is it good? Because it's so simple. Anyone can understand it. It takes almost no effort to read.
An even more surprising thing happens when you get them to design UI's, as in "I want a form that takes in X and does Y with it". Again, what they come us with is so simple, my grandmother could use it. Stupid people don't design complex things. Give them anything more complex than a single form and you are asking for trouble of course, as they can't zoom out and pull in the big picture, then zoom back in and execute it.
So it's horses for courses. Stupid hardworking take a lot of investment in management time. They reward that in the long term by turning out a lot of code. But you need a cookie cutter task that lasts for years at least to make the investment pay back. They don't work in a consulting where novel short term tasks are the rule. But you'll find them happily toiling away in bureaucracies, and being paid stuff all for the privilege of being the backbone of the organisation. Which explains the why stupidest thinks we have to deal with in life are bureaucracy. The people you are dealing with aren't paid to think.
rstuart4133|2 years ago
The thought of someone stupid turning out the most code in a team used to make me shudder. But then I got some not so bright people on my team.
It's true that stupid left to their own devices turns out terrible code. But they have their strengths. Janitors for example are often classed as stupid, but a stupid and hardworking janitor will do a far better job than of the other types.
The key insight (and this was pointed out to me by of all people someone in marketing, designing campaigns to make products appeal to certain crowds), is janitors like routine. I guess stupid doesn't like to be made to think, they like to do what they excel at, which is doing. So the key to making it work is the smart (and preferably lazy) people design the routine, and the stupid execute it. You can rely on stupid and hardworking to do it consistently and quickly.
In programming terms, this means you need strong coding rules, lots of examples, thorough reviews which takes enormous amount of patience. A smart programmer will cafe at the oversight required, as it prevents exploration of ideas. Give stupid that and something remarkable happens - they produce very good code. Why is it good? Because it's so simple. Anyone can understand it. It takes almost no effort to read.
An even more surprising thing happens when you get them to design UI's, as in "I want a form that takes in X and does Y with it". Again, what they come us with is so simple, my grandmother could use it. Stupid people don't design complex things. Give them anything more complex than a single form and you are asking for trouble of course, as they can't zoom out and pull in the big picture, then zoom back in and execute it.
So it's horses for courses. Stupid hardworking take a lot of investment in management time. They reward that in the long term by turning out a lot of code. But you need a cookie cutter task that lasts for years at least to make the investment pay back. They don't work in a consulting where novel short term tasks are the rule. But you'll find them happily toiling away in bureaucracies, and being paid stuff all for the privilege of being the backbone of the organisation. Which explains the why stupidest thinks we have to deal with in life are bureaucracy. The people you are dealing with aren't paid to think.