Which is just something many people don’t really care to do. And that’s fine. The problem is trying to get everyone interested in it, denying the fact that many lack interest and aptitude, and then diluting the experience for everyone while saddling the next generation with decades’ worth of debt.
For example, with engineering, an airplane built from your design flies or does not. There's no pretending it flies when it doesn't. Reality cannot be fooled, so one is forced to learn to think critically.
But with liberal arts, the same person can argue both points of view with equal facility - how does one tell which is correct? What good is being able to criticize without a mechanism for determining the correct way? Or even a better way?
To argue from the other side, the point of liberal arts isn't to make you argue both sides of an issue equally. And telling a good essay from a bad essay can often be easier than telling a good airplane design from a bad one.
(Full disclosure: I'm an engineer and I only took 2 semesters of humanities classes in college.)
The idea of liberal arts is that their study enables one to participate as a full-fledged member of society. Thinking critically about arguments that concern society requires not just checking the validity but also the soundness of an argument. I suppose you really need some understanding of culture and history to make up your mind about many issues of importance to the society in which you live.
In engineering, you learn to discern logical fallacies rather quickly. Insulting your computer (ad hom) won't fix bugs in your programs. Insults in issues of importance to society are the norm, even going to the highest levels.
As a lawyer friend told me once:
1. if justice is on your side, argue justice
2. if the law is on your side, argue the law
3. if neither the law nor justice is on your side, insult the other side
Where the grandparent said "employers think college degrees are more valuable than they probably are," you've highlighted the disconnect between what employers think they're getting from a college grad (certain skills) and what colleges actually do (teach students to think, to learn, to read).
That's not High School 2.0. In fact, High School seems to be the right place for vocational training. It's the pinnacle of state-mandated schooling, and in fact includes vocational requirements. Some schools implement that as wood shop. Others focus so completely on teaching computer skills they become a "magnet school" for that one thing only.
Unskilled work is disappearing and simultaneously employers are demanding more unskilled laborers. The work is disappearing because it's cheaper to have a machine do it flawlessly. The employers don't want skilled labor...labor versus capital all over again.
For a while yet, it may be possible to become really skilled in computing and successfully straddle the divide: make enough money to be comfortable as a skilled laborer. But I think it would be wise for _colleges_ to cross-train all their Science/Engineering students in business.
Colleges (traditionally) focus on the whole person. A person with business skills, connections, and potential funding becomes the new bar for entry. I'm always thankful my professors took the time to do that last part: take us (a team of students) into the real world.
I'd like to argue for the opposite. Since everyone goes to high school, it should be a place to teach people to think, learn and read (that's how it used to be in some European countries). This is where students could explore and find out what they like, as well as read as many books as they can.
After that, college should be for white-collar training. You really do need several years of focused learning on certain topics before jumping in (I don't think you can ever jump straight into medicine, building bridges or designing microprocessors without a few years of reading in advance).
This is base on my experience, but most of them are bad. They lack vocabularies and such that when they try to convey what they're doing or what they want other people to do or hell just to communicate with the team it takes a fucking long time and in the end might not even get anything done. They also want to get shit done without thinking about any other possible solutions or the consequences of their chosen solution.
I've worked under one. From my imperfect memory, he basically ask to make the API to be as good as their competitor.
When I ask more questions to clarify it. The said programmer got frustrated and threw a tantrum. Eventually, I found out the asshole, who lack soft skills, just wanted a async call methods in the api from client to the server.
edit: added most, because I'm sure there are a few exceptions out there.
I think the real difference between the good developers and the bad is more a result of "passion" for the field. If your only care is about getting the job and the salary that comes with it, you may very well spend a lot of time and effort getting to that point, but you probably won't go beyond that. On the other hand, the guys on my team, myself included, are all passionate. Now that doesn't mean "slaves away for ungodly hours" or even that they spend their time working on side-projects. The common-denominator is that we very much enjoy the line of work. We try to be "craftsmen" and not just a desk-bound office rats. Some jobs allow you to get to a point where you just don't have to put forth much effort unless you actively try to be the best. Software development/engineering/<term du jour> is not one of those fields.
The degree is the best effort so far in our society that shows that someone is competance in their field.
I never finished my degree but instead I finished a ton of other projects, businesses and employment that has made me a ton of $$. And I would do it all over again for a fraction of that money because I go to bed at night (reluctantly) thinking about all the cool shit I get to build and program the next day.
Passion is abstract, excitement is visible. If one day you are looking to hire someone and they don't have the academia creds but do have the experience and are pumped up about your company, team, product or project then give them a shot, you wont be disappointed!
Here's a thought: knowing and understanding concepts is more difficult than learning the lingo. Why not just, very respectfully and casually, insert the correct word into the discussion and help the guy pick this stuff up? It's called "teamwork" and it's really quite good at making work (and life) better.
I've worked with too many guys with EE and CE and CS degrees that just totally fall down on the job to believe that a degree is the silver bullet of ignorance that you're suggesting. I think in reality it's about individual drive and intellectual appetite. But that's just my own observation.
I don't believe knowing and understand goes hand in hand.
Computer Science have tons of vocab. If you get rid of all of them then you mind as well spend the whole day doing nothing but describing all the absract concepts.
The reason why we invent vocabulary is so we can ignore the lower nitty gritty details and talk on a higher level and focus on the problems we're trying to solve. I don't need to spend more than sentence or so to describe a singleton. I can just say hey I'm thinking that we should implementing a singleton because it's resource intensive.
Instead hey, let's ensure that there is only one instance of this class because we don't need more than one instance. Even in that sentence, Instance is also a vocab of CS.
>> to believe that a degree is the silver bullet of ignorance that you're suggesting.
I'm not suggesting that this is the silver bullet. But this is an indication that a person have some competent to at least get a degree.
The odds are still against you. You will lose opportunities due to credentialism. The best bet is to become better than your peers and be in the top 5% of the talent pool. When you work with someone who really knows their shit, shadow them.
The better bet is to eventually go independent once you know you're more towards the top of the heap. Years ago, a McKinsey subsidiary ultimately ruled me out due to a lack of degree. Nowadays they're a customer and have no problem subcontracting me out, because "I run my own business" and a proven track record is just as sufficient as the degree they otherwise look for.
And it's even worse now.
In the end, I lucked my way through a succession of jobs, due in part to the fact that my chosen career, systems admin, doesn't really have a university career path leading to it, so my personal experience was worth as much as anyone else's.
My recommendation: do lots of projects, contribute to open-source, put a bunch of personal projects up on github (and do them right; document them well and write good code), and apply to forward-thinking companies (startups, etc.). Show that you can do the work and no company worth their salt will care too much about how you learned it.
I need to put a plug in for my alma mater: http://www.rit.edu/programs/networking-and-systems-administr...
A lot of my friends from high school have part-time jobs / intern over the summer at the startups/companies from where around I used to live...
But I don't live there anymore. And I'm kind of hesitant to move back to Sunnyvale (It is the most boring, soul-sucking place on earth) so I guess that doesn't really count for anything.
Meh.
The apprenticeship model should be re-embraced.
Generally, you don't want your DBA discovering the 3rd normal form halfway through a project.
Of course, this, like many factors, is both a cause and an effect of this more fluid labor market.
Yes and yes I wasted the first two years in college learning High School 2.0 and the last 2 learning technical concepts that people used 5-10 years ago. XHTML, CGI and using tables for layouts to name a few.
I'm sorry for you. My college experience was very valuable to me (not for the diploma, nobody cares about my diploma, least of all me). I learned a great deal about how to solve problems, how to figure out what was important, how to separate truth from crap, how to learn, and the confidence that I can do it.
Caltech's honor system has also been very formative for me and I've applied it since then with considerable success.
The more I hear about other peoples' college experiences, the more I appreciate how lucky I was to wind up at Caltech.
The statistics would quickly show that people with minimal or no education do almost as good, and are willing to work for less, and so they just hire them instead. Or maybe see that people from "lesser" universities are just as good as those from more prestigious ones. Maybe certification agencies would compete on the basis of how well their certification actually correlates with employee performance. Schools or training agencies could compete on a similar basis.
We keep running into this problem where employers think college degrees are more valuable than they probably are. Part of that is impressed culturally, but more than anything we lack better methods of certification in most jobs. We need certification that matters, is widely accepted, and that employers actually trust. It has to be marketed well, and it has to actually produce graduates with up-to-date skills. It's not easy, especially in fields where curriculum must change yearly.
Underlying all of this is a larger, unavoidable change taking place: the disappearance of unskilled work. Computers and machines are slowly taking over every unskilled job, starting at the least skilled and moving upwards to things we used to think of as skilled labor. Taxi drivers and factory workers will hardly exist in 10 years. Construction workers will only supervise machines in our lifetimes. Unless you want to work in a low-paying retail job for the rest of your life, you need to get a degree so you can work your way up some corporate ladder - or so the thinking goes.