You get shitty fast programmers and shitty slow programmers.
You get good fast programmers and good slow programmers too.
'Fast' or 'slow' in isolation are not really a measure of anything valuable, except perhaps how an individual fits into the team culture.
The crucial thing to measure is how long it takes to get to good, robust software that does what it needs to do.
There are many strategies to achieve that (agile or big design up front or others) but software engineering as a medium is too immature to have found the one true way (maybe there will never be a one true way). Up front design and emergent design have both succeeded and failed on many occasions.
This post reads to me as someone who doesn't like working with younger teams as the work style often doesn't fit, and therefore concludes the team's working style is wrong, rather than he just subjectively doesn't like it.
Most of this thread sounds the same to me too.
Maybe the benefit of a fast programmer is it is quicker to find out if they are shitty?
Agreed. I am fast, but refactor constantly, so there really is no "final" code or "finished" result. The current form is continously honed and refined. My cycles are very quick, however the design is not rushed but rather well thought out over many iterations.
'Fast' or 'slow' in isolation are not really a measure of anything valuable, except perhaps how an individual fits into the team culture.
The crucial thing to measure is how long it takes to get to good, robust software that does what it needs to do.
There are many strategies to achieve that (agile or big design up front or others) but software engineering as a medium is too immature to have found the one true way (maybe there will never be a one true way). Up front design and emergent design have both succeeded and failed on many occasions.
This post reads to me as someone who doesn't like working with younger teams as the work style often doesn't fit, and therefore concludes the team's working style is wrong, rather than he just subjectively doesn't like it.
Most of this thread sounds the same to me too.
Maybe the benefit of a fast programmer is it is quicker to find out if they are shitty?
I'm 42 and consider myself fast-ish FWIW.