We (little ISP) get them for a few hours each day after school and put them to work answering phones. They get some work experience and credit under the high school's "industry as shop class" scheme.
The better ones get a job for the summer and a raise. If they show the right blend of bordom doing phone support combined with motivation to learn systems stuff we promote them and give them sysadmin projects.
Worst case they end up with some clerical work experience in a office environment. Best case they learn some combination of Sysadmin/Netadmin/Coder. Either way it beats working fast food or stocking shelves.
As for this project, I, for one, would like to learn about 3D rendering -- that's always been something that I'd admired from afar.
1. This will attract a large pool of young talent and some of them will make direct contributions and contributions through feedback and interplay of ideas.
2. This creates goodwill in the developer and education community which helps experienced industry professionals to think more highly of Valve. They will be more likely to apply or recommend applying.
3. This, as has been said, improves conditions at Valve and helps to shine light on more stultified areas of the company.
I helped out at http://studentrnd.com/ a few times. Hooooly crap. Some of those 14 year olds can code! Having two Microsoft Devs as parents is a pretty good strategy if you want to grow up and be valuable to Valve.
It's a weird conflict, really. As others have said, there is a bitter taste of manifestly unwarranted ageism in your post.
It's not the "right" way for every company. Valve and other companies do the opposite. But for most of the industry it is a cost of doing business.
I could have chosen to be politically correct or realistic & honest. I chose realistic & honest.
That's the part that is disconcerting. It's a despicable way to conduct your business.
You could say people new in the industry haven't been conditioned and molded yet. They're young in the industry and thus make stupid mistakes in the process and in the process find new ways of doing things. That would be far more accurate.
I think you misspelled "wise up"
But, is that bad?
As ChrisNorstrom's sibling reply points out, companies really do want young workers in technology. They're more up to date on languages and tools. They'll produce more work and dedicate more time when unencumbered by family concerns. They don't have an expectation of or a lifestyle that requires a six-figure salary. Experience is less of a concern in game and entertainment development than in other industries; it doesn't matter so much if a young hotshot clutters up the codebase a bit or reinvents some wheel algorithm, when this game will be shipped and a new one begun within a year. Even bugs stemming from inexperience are less of a concern for Valve than anyone else, when they own the distribution platform that can automatically push patches and updates anytime.
It's also not illegal if the "older" victims are under age 40. The Age Discrimination in Employment Act only forbids age discrimination against workers 40 or older. http://www.eeoc.gov/laws/types/age.cfm
Sure, it sucks for the fired workers. Sure, it sounds ruthless and inhumane. And sure, if Valve is blindly firing everybody between age 30 and 40, then they're being dumb, since of course some programmers are still 10x animals at any age. But Valve is not a charity or a government, and is presumably smarter than that. It's a business in mission to make games and money. Every business should be seeking to replace low performers with fresh faces. And in game development, the performance and business value of an employee does bear an inverse correlation with age, so lower performers will skew older.
This philosophy is just another extension of the fetishization of youth. Just because someone is young doesn't mean they'll be better than an older employee (and vice versa, of course).
Judge people on their merits and what they actually achieve, not on what their birthday happens to be.
1) Good for Valve. I think this is the beginning of an already awesome company evolving even further.
2) Jeri Ellsworth (fired valve employee) was right. Some of the older Valve employees really have been holding the company back in terms of culture and new hires. This seems to be Valve's response by fixing itself and focusing on recruiting new younger staff. The problem with being an awesome place to work is that employees don't leave even when they should. They might in turn refuse to let younger employees in out of fear that they'll be replaced. So slowly it destroys the natural cycle of replacement of old ideas with fresh new ones. It might not be set up as a recruitment platform but it sure can be used like one to Valve's advantage. They can support kids who want to get into the industry and at the same time snap up the best of the best before other companies do.
3) Also, Valve hires only the most experienced who can self manage themselves. This has allowed them to do a lot with only 300 or so people but expanding seems to be slow. Other companies hire juniors, work them hard, pay them below market wages, and can expand faster and create more IP. If Valve wants to launch more IP or expand they're going to have to change their ways. And it seems they've come to terms with that.