Confidently WrongClever machines. Same old humans. What do you do when your boss asks you to build a colleague job killer? It seems, you build it anyway...A software developer has been asked to build an internal AI tool, but he's also quite sure it's going to get his coworkers fired. This does not seem to be a problem for him, or many others as it turns out. This is, depending on your perspective, entirely rational or a betrayal of every colleague who's ever offered you a cup of tea. The developer, Pressberg, is clear-eyed about the situation. He doesn't have close relationships with the people who'll likely be displaced. He reckons he's not the only one doing this. And his summary of the available options is, genuinely, hard to argue with: you can ride the horse, or get trampled by it, but you can't just watch the race. Which is a sensible framing, and also exactly the kind of sensible framing that makes something slightly terrible feel inevitable. The uncomfortable part isn't that one developer in Florida made a pragmatic call. It's that this is apparently a widespread enough experience that Business Insider ran the story with "I think" in the headline, suggesting the builders often don't even know for certain. They're just guessing, building, and hoping the horse isn't coming for them next. The Human Side of AI
28% of music uploaded to streaming platforms is now AI-generated...but it accounts for 0.5% of streams. What does this mean for music, taste, discovery and that guy that makes jingles in his bedroom. Napster changed how we owned music. iTunes changed how we paid for it. Spotify changed how we found it. This one changes what counts as music in the first place. To bring this to life a bit, I've been testing a thing I'm calling an Impact Tree - a branching map of consequences across time, with the behaviours running underneath. Below: here and now, imminent, on the horizon, the long view, and five behavioural shifts running underneath. Have AI Got News For You!
Cheat Codes
|