This is like saying that automobiles are overhyped because they can’t drive themselves. When I code up a new algorithm at work, I’m spending an hour or two whiteboarding my ideas, then the rest of the day coding it up. AI can’t design the algorithm for me, but if I can describe it in English, it can do the tedious work of writing the code. If you’re just using AI as a Google replacement, you’re missing the bigger picture.
For thousands of years the ruling class has tolerated the rest of us because they needed us for labor and protection. We’re approaching the first time in human history where this may no longer be the case. If any of us are invited to the AI utopia, I suspect it will only be to worship those who control it. I’m not sure what utility we’ll have to offer beyond that. I doubt they’ll keep us around just to collect UBI checks.
Right on. AI feels like a looming paradigm shift in our field that we can either scoff at for its flaws or start learning how to exploit for our benefit. As long as it ends up boosting productivity it’s probably something we’re going to have to learn to work with for job security.
This is how it went down with Agile at my company 10 years ago, and some process certifications and database technologies before that. Based on what I’m hearing from upper management microservice are probably next.
From my perspective the corporate obsession with microservices is a natural evolution from their ongoing obsession with Agile. One of the biggest consequences of Agile adoption I’ve seen has been the expectation of working prototypes within the first few months of development, even for large projects. For architects this could mean honing in on solutions in weeks that we would have had months to settle on in the past. Microservices are attractive in this context because they buy us flexibility without holding up development. Once we’ve identified the services that we’ll need, we can get scrum teams off and running on those services while working alongside them to figure out how they all fit together. Few other architectures give us that kind of flexibility.
All this is to say that if your current silver bullet introduces a unique set of problems, you shouldn’t be surprised if the solutions to those problems start to also look like silver bullets.
OP says you can sync memories both ways - easy solution is to just take turns.
One clone so that I can be a stay-at-home dad without losing my income. Finally finish grad school and fix up the house. Show my kid the world when they get old enough to appreciate it. Get a second job once they start school - something to get me outside, or working with people face-to-face. That would be amazing.
It’s certainly possible that Meta has a plan to destroy the fediverse with Threads, but I wouldn’t dismiss the possibility that they’re just doing this because they can. If their plan was to take over the fediverse from within, and that plan hinged on instances not defederating out of caution, then it’s off to a poor start. I might just be totally naive but this feels more like them testing the water by opening their doors to the fediverse - I don’t know if they know what happens next.
A lot of people are doing work that can be automated in part by AI, and there’s a good chance that they’ll lose their jobs in the next few years if they can’t figure out how to incorporate it into their workflow. Some people are indeed out of the workforce or in industries that are safe from AI, but that doesn’t invalidate the hype for the rest of us.