The concern is always that there is a finite amount of work[0] to go around in any given iteration of our current style of society. New kinds of work do get invented from time to time. Automation eliminates kinds of work. The two are rarely in sync with eachother and the difference is usually measured in human privation and suffering.
[0]work being defined as, "something you can trade for food and healthcare"
Though I can imagine a counter argument from a technologist/futurist positing that the incentive to automate in part comes from that merciless system of survival.
The modern Luddite, I think, doesn't necessarily "hate" looms, or their inventors. They just don't have any faith that those necessary compensations you describe will ever happen, or at least not quickly enough to save them. Perhaps the government is convinced by exactly that argument above. Or at very least too apathetic (or financially tangled) to fight it.
We all act along the axes where we can affect something, effect something. Smashing looms is a fool's errand, but sometimes that's all the power you feel you have.
Agree
> We all act along the axes where we can affect something, effect something. Smashing looms is a fool's errand, but sometimes that's all the power you feel you have.
However I think what's fascinating about this is it requires believing you can't change your skill set to something else. Sometimes I don't think its as simple as feeling empowered, but also fear and anxiety about change.
Oh my god, yes. The way it makes everything possible means you never get to feel like you actually know WTF you're doing, because the edge is always expanding. Bring back the days of having a small shelf of 5-10 books that contained 99% of what you needed to know to do your programming/sysadmin/whatever job.
Yes, it's absolutely exhausting. If you've never experienced or even seen what came before, it may not seem so just because you don't have a point of comparison.
I was less productive than I am now, but making something was more satisfying.
Today.. .. first one has to get up speed on whatever the F changed this week
Before the internet could pose a challenge to my bookshelf, I had over fifty that I referred to fairly regularly (my office library had about 100, my total library several hundred), ~5 of those covered 80% of what I needed for a given project, but which 5 those were changed from project to project.
This is made worse by their size and scope. Spring Boot is a giant ecosystem, as is .NET, as is Azure, etc.
Also, search results tend to be a sea of data which might, or might not, contain some crucial bit of information that will help.
So, all too often, "using Google to answer a question" becomes a 2-hour or day-long research project to figure out how to solve some small, arcane problem like why the POST to some service doesn't have the Authorization header.
And when there's internal and external pressure to be productive, meet deadlines, and not feel incompetent, sometimes it gets frustrating and stressful and tiring.
My point is that we couldn't possibly do our jobs now without Google, but that we used to be able to do it just by knowing the stuff in a few books really well and knowing where—in the books or in e.g. manpages—to find what we didn't know. A small shelf of books is way better than Google, if you can be reasonably certain that the answers you need are in there.
Yes, this situation is far more exhausting.
Who am I kidding, Idiocracy is already a reality. Just look at the comments here on HN.