First off, the best programmers I know are the laziest.
Second, being a prospective employer myself, I can verify that I would hardly scoff at a recruit with a firm grasp of OO, never mind his 'tool' of choice (java, c++, CORBA/COM[gasp]). However, if the only skills listed on a resume are the ones you mention (C, COBOL, FORTRAN?) I'd wonder what rock this person had been under, and imagine my training budget skyrocketing as I attempt to bring this geezer up to speed with the rest of my team.
Of course, having these skills in your background don't hurt, but they hardly help, in terms of 'being thrust into the "real world"'.
Thirdly, if you think OOP only about assembling blocks of code written by other people, then you're either sorely mistaken, or perhaps poorly educated on the subject. The joy of getting to reuse something you wrote 6 months before, in a new and interesting way, is hard to describe. The joy of adding features you didn't know you needed to an architecture, without breaking it, is hard describe. The joy of hearing about someone you hardly know, reusing and extending a library of classes or objects you created, in new and interesting ways, is wonderful.
In all three examples above, proper planning and vision is required before the programming starts. You need to have a full analysis of the requirements, and you need to build in enough flexibility to support change, without bloating it. Science? Who cares?
If all you're getting from your CS program is the so-called "Science" of computing, I guess you'll never be subjected to the "horrors" of the real world anyway, as you'll have few skills we want or need.
Slashdot Mirror
Second, being a prospective employer myself, I can verify that I would hardly scoff at a recruit with a firm grasp of OO, never mind his 'tool' of choice (java, c++, CORBA/COM[gasp]). However, if the only skills listed on a resume are the ones you mention (C, COBOL, FORTRAN?) I'd wonder what rock this person had been under, and imagine my training budget skyrocketing as I attempt to bring this geezer up to speed with the rest of my team.
Of course, having these skills in your background don't hurt, but they hardly help, in terms of 'being thrust into the "real world"'.
Thirdly, if you think OOP only about assembling blocks of code written by other people, then you're either sorely mistaken, or perhaps poorly educated on the subject. The joy of getting to reuse something you wrote 6 months before, in a new and interesting way, is hard to describe. The joy of adding features you didn't know you needed to an architecture, without breaking it, is hard describe. The joy of hearing about someone you hardly know, reusing and extending a library of classes or objects you created, in new and interesting ways, is wonderful.
In all three examples above, proper planning and vision is required before the programming starts. You need to have a full analysis of the requirements, and you need to build in enough flexibility to support change, without bloating it. Science? Who cares?
If all you're getting from your CS program is the so-called "Science" of computing, I guess you'll never be subjected to the "horrors" of the real world anyway, as you'll have few skills we want or need.