I disagree with your point that this analogy does not apply.
You say there are some codebases that need over 9000 IQ to do anything. While that might be true, it is not the norm and a small fraction, so it’s not relevant to the broader argument.
You say it’s completely different in programming.
Sure it doesn’t help if one of your workers is a complete idiot — but that was not the premise - it was unskilled but energetic.
And there are always menial tasks to do — you pointed out some example yourself.
So to sum up my points are:
- most codebases do not require gigabrain for every single change
- there are always menial tasks to be done in a team environment
- “untalented” people don’t necessarily slow things down in development
- in fact talent is irrelevant when writing code - I would even argue that being talented is not always an advantage, in any field or profession - but that last point probably would need some more explanation.
You say there are some codebases that need over 9000 IQ to do anything. While that might be true, it is not the norm and a small fraction, so it’s not relevant to the broader argument.
You say it’s completely different in programming. Sure it doesn’t help if one of your workers is a complete idiot — but that was not the premise - it was unskilled but energetic.
And there are always menial tasks to do — you pointed out some example yourself.
So to sum up my points are: - most codebases do not require gigabrain for every single change
- there are always menial tasks to be done in a team environment
- “untalented” people don’t necessarily slow things down in development
- in fact talent is irrelevant when writing code - I would even argue that being talented is not always an advantage, in any field or profession - but that last point probably would need some more explanation.