Well, I'll do my best to synthesize what JimmieMac and capitalist_mao are saying, since they seem to be more concerned about arguing with each other than exchanging the meaninful discussion they should be.
Mao: Jimmie knows what the

he's talking about, but his delivery is lightyears beyond coarse. If you've worked in any kitchen before, ANY interaction takes place in the context of a dick-waving prick fight. He's normally like this (not that that's any excuse), but not just online, I could imagine. You have to be exceptionally thick-skinned to work in the back of the house. If you get mad because someone yells at you to "bring me some goddamned chickens, a hotel pan, and a stack of towels, cocksucker," then I don't think you'll find a single kitchen in the US you wouldn't hate working in. The nature of the beast is that kitchens are hypermasculine (and more often than not, the women *far* tougher than the men).
Learning to cook is one thing. Can I cook? You bet yet ass. I realize how this limits me; you want prep? You want a line cook? You want desserts made? I'm your dude. You want me to make a special?

you, I'm going for a smoke.
Jimmie is drawing the line between being a cook and a chef; the former is lesser-paid manual labor, long hours in front of boiling pots, spitting steamers, open-flamed grills, and sautee pans that melt to your hand. The latter makes sure all the junkies they call cooks don't call in, show up on time, get shit done before opening, place orders, create specials, discuss the specials with the waitstaff, do inventory, and work longer hours than cooks. The former deals with everything from the kitchen to your plate; the latter everything before that. I should also emphasize that chefs create the menu (in a few places; you most certainly won't exit school and be given the reigns of a menu, so most graduated "chefs" earn their stripes line cooking for someone for years - honestly, the transition from cook to chef isn't always about skill, so much as it is about networking with the right people).
Jimmie: Sit down and have a massengil. Mao is simply interested in going to a culinary academy. Perhaps instead of being a prat and busting his balls from the get-go (as if he wouldn't experience any of that for the rest of his culinary life

), let's find out what he wants to do (alright, so you did ask that, which he treated rather flippantly, I admit). So you make the judgment call that he has no idea what he's talking about or getting into (and perhaps you're right); why not guide him in that direction? Not everyone knows the difference between "cook" and "chef," and I'm sure many people attribute the difference in title to a puffy hat. Ask him if he's interested in general cooking, pastry cooking or desserts, or some other shit I'm sure I can't think of. Does he prefer italian, or french? I'm sure you were initially trying to be helpful, but it's not like some of the best cooks I ever worked with knew their middle names half the time.
On last point that many are trying to make, mao; having credentials from a culinary academy guarantees you nothing. Moreover, having little to no real-worl experience (which is pretty unlikely, as you'll likely have a co-op program) makes you a nobody. In my life I vowed (and thankfully don't have to do this) to NEVER hire a bartending school graduate. You know why? They learn that Tom Cruise bullshit there, and they think that their booze degree means they can't be told shit. Instead, I'd rather teach someone to pour a four-count than reteach some douchebag to make drinks the way we do it here. The same goes for cooking; if you have the credentials but no experience, then the chef will, in all likelihood, think you a brat know-it-all with no real world proof that you can cook. The chef would rather not have someone they have to reteach.
Are culinary degrees worth pursuing? Of course they are; but it's also about how you apply your studies while in school, and most importantly, the networks you make.