I wrote this post after reading one too many articles about how coding is the skill that leads to a job. It’s a skill all right, and a useful one, but will it definitely lead to a job? We return again to the “purpose” of learning, or of education – and because of context so many people are fixated on seeking the magic formula for employment, and other factors are diminished. We also lose sight of the process by which people actually do end up with meaningful employment. Here is a link to the original post, from January 13, 2012:Cracking the code for unemployment .
The question of whether postsecondary education is a good investment, of whether the “risk” is too much or if it is “worth it,” is one generally framed in terms of economic value now that PSE credentials have become ever more expensive and necessary for larger numbers of people.
Of course the correlation is there — I’d be the last one to deny it; graduates of PSE programs earn more over their lifetimes and are more likely to advance in their careers than those without such credentials. But how exactly does the correlation map out in practice? How do postsecondary graduates actually find and obtain jobs? How do they build their careers? And what image of this journey are we projecting, in the media and in classrooms? How are students being encouraged to make the connection between education and employment, and what are the consequences of that?
These are difficult questions because they relate to process: what happens between the point at which a student begins a degree and the time it is completed, such that somehow a student can obtain employment later?
Heavily emphasizing or highlighting certain skill sets, courses and degree programs because they are more highly correlated with employment is a bad idea because job markets can shift rapidly, and also because it places the skill or knowledge base outside of its larger context. As a small example, in this article the skill of computer coding is described as something that can “get you a job.” But stating this, alongside average hourly wages for computer programmers, is to present what looks like an overly simplistic equation. Who finds work that involves coding, and what is its use? How much experience, and of what kind, is required? How does coding fit into a larger skill set in a way that would help a candidate to “stand out” in a large pool of applicants?
Focusing on the university-to-job correlation without a balance of attention to process can mean that we place less value and emphasis on looking for other ways to build careers. And it means reducing the attention we pay to extra-educational factors, not only the enthusiasm, energy, talent, and work ethic that one may or may not bring to one’s education but also the privilege or lack of it, the social and cultural capital, and the many other factors that can be beyond the scope of one’s education-to-career planning.
There are no short cuts and no easy plans — no easy mapping of knowledge to employment, now that overcrowding plagues even formerly stable professions such as teaching and law. To imply that there is ever really a “guarantee” from a degree is to lead students down the garden path; it raises unrealistic expectations and re-inscribes unhelpful assumptions.
Even the availability of a degree-related job doesn’t guarantee one’s career pick. I recall about two years ago I met a young Belgian man at the hostel where I was staying in Picton, New Zealand, and by coincidence we ended up taking the same early morning ferry back to Wellington together. He came from a well-educated family, and had gone to university at 18 to become a doctor, as his parents expected. But now in his early 20s, having just completed his medical training, he seemed at a loss. He didn’t want to practice medicine, though he’d earned the credential; he’d done it not because he desired to use his time and talents in that field, but because it was just the next thing to do. I thought it was interesting that he had obtained a desirable professional degree but was now at loose ends, not even because of the job market but because of his own lack of direction outside of the university program.
Among other things, knowing yourself — your own capacity, your predilections, strengths and weaknesses and how you learn and think and function in different environments — is extremely important for making the decisions that lead to a career. There is little point in cobbling together a random kit of recommended skills if you have no real interest in those skills or in the things they enable you to do; you might find a job, but I think it’s unlikely that the recipe for employment will turn out the way you planned. Even an economic assessment of a possible career path must take non-economic, less tangible factors into account if it is to prove of any worth.