10 ms·
If you accept the article's theses that older developers are a big asset AND that they're at a disadvantage in the marketplace due to discrimination, there's an
by codypo 16y ago
If you accept the article's theses that older developers are a big asset AND that they're at a disadvantage in the marketplace due to discrimination, there's an opportunity here. Rather than try to woo and retain 30 hotshot developers in their 20s, it'd be easier to hire 18 or 20 developers in their 40s. The turnover would certainly be lower, the output should be equal (or greater?), and there'd be less need for extensive management oversight.
Anybody know of a company that's tried that approach? If none exist, that leads me to think that either we're onto something interesting or that this approach simply doesn't work.
- blacksmythe 16y ago>> it'd be easier to hire 18 or 20 developers in their 40s. Great developers in their 40s have a wide range of contacts from their years of working, and rarely if ever look for jobs on job boards. Finding great developers in their 40s, and prying them out of their present jobs, is a non-trivial task. (One I am actually in the process of this week).
- pchristensen 16y agoI'd imagine that even if there's a opportunity there, it's still hard to separate great older devs from mediocre older devs, and older people have higher salary expectations.