There is a great graph-filled post over at Slate Star Codex called Technological Unemployment – much more than you wanted to know. After analysing a lot of data from the US economy, the author arrives at some tentative conclusions: The main point seems to be that the evidence for large-scale technological unemployment is mixed. There is evidence of technological underemployment however. There are signs that people are now struggling to adjust. The final paragraph is:
“This is a very depressing conclusion. If technology didn’t cause problems, that would be great. If technology made lots of people unemployed, that would be hard to miss, and the government might eventually be willing to subsidize something like a universal basic income. But we won’t get that. We’ll just get people being pushed into worse and worse jobs, in a way that does not inspire widespread sympathy or collective action. The prospect of educational, social, or political intervention remains murky.”
Jon Perry has written an interesting post listing some strategies for dealing with the Technological Unemployment Problem.
The Technological Unemployment Problem is the issue of technology replacing humans to the point that there is massive unemployment.
Continue reading “The Technological Unemployment Problem”
There is a very scary article on the Atlantic about how you essentially become shunned by employers after 6 months of unemployment. It is about an experiment by Rand Ghayad of Northeastern University. He applied for 600 job openings using fake resumes, within which he varied 3 factors – how long the applicant had been out of work, how often they had switched jobs, and how much experience they have. What he found is that how long you’ve been out of work is the most important thing that employers look at. People prefer to hire someone with no experience, than someone that has been out of a job for more than 6 months. Scary stuff.
I read the post “Don’t Call Yourself A Programmer, And Other Career Advice” on the weekend. It is mostly aimed at permanent employees at companies, although I thought there were some useful takeaways for contractors as well.
Below is my summary of the points that resonated with me:
Continue reading “Not a programmer!”