|
|
|
|
|
by tunesmith
25 days ago
|
|
Unfortunately it will take longer for our bosses to walk it back. I feel like I'm fighting the battle daily, telling execs what kind of work LLMs do not replace... it's very slippery, they keep on doing the rhetorical texas two-step - I don't think they even realize they're doing it. We communicate that LLM is amplifying, they hear it can replace. "No, we need humans to help with specs" "But AI can help with that." "But only help, they can't come up with the idea." "Sure they can, we can just ask them." It's also amazing how hidden some of these realities were before. Like, you assign a ticket to a developer - in the past they just wanted to know the developer was working on it and didn't care so much which work was what. They'd probably be so surprised to find out that a large percentage of implementation was deriving exactly what was meant by the jira ticket or the specification or the product person's intent. Which is all the stuff you have to work on before you can type in a prompt to an LLM. But now there's this pressure to believe that the developers only do the implementation part that the LLMs do, so they can pretend there will be major efficiency improvements. And it's really hard to explain to them what it is that developers even do. I know I'm not saying anything new here, but at least where I'm working all of these matters feel much more present than they did months ago. |
|
I'm convinced this is in large part because of the anthropomorphism of AI.
AI is not people, the moment you start treating it as people you start believing and thinking of it as people and you now take the human safety check out of the loop.
If you take the human out of the loop you have an unsecured weapon/dangerous object on the loose. anything from excel spreadsheets through to actual weapons. it all needs a human in the loop.