This is good advice. I once worked under a kid just out of college -- he had connections to the big bosses -- and while he was smart and good for the amount of experience he'd had, the system got really, really messed up under his naive direction. I quit out of frustration.
It's important to respect experience and ascribe proper placement to it in your organization. You want someone seasoned calling the shots, not a relative "newbie". People from college have a lot of theory and homework pumped into their heads, and that's fine for what it is, but your systems are much better directed with the pragmatism and practicality incident of significant real-world experience.
Well, it depends. The college kid we hired had been coding since age 13, had passed up Harvard for a free ride at a lesser name regional school, and had interned for IBM & Lockheed Martin before. Dude serious had his shit together.
That said, my co-founder is 33 and had previous startup experience.
It's important to respect experience and ascribe proper placement to it in your organization. You want someone seasoned calling the shots, not a relative "newbie". People from college have a lot of theory and homework pumped into their heads, and that's fine for what it is, but your systems are much better directed with the pragmatism and practicality incident of significant real-world experience.