Man, the domino effect of bottom up worker replacement from LLMs is going to be a wild ride.
Can you imagine how many companies are going to hollow out their knowledge and skill base?
How often we'll have to deal with compounding hallucinations until the whole thing collapses on made up numbers and accounts?
We already have this problem with people, but can you imagine how fast this will go when less and less people are there to supervise? To cross T's and dot I's?
@nickdrawthing I have so many friends and family that have worked in call centers & the amount of 'not in the book' problems they solved from fucking around and finding out was most of it. This is gonna be fun.
@batichi 100%. Unrelated to LLMs but the place I work had massive layoffs a year and a half ago. We are still constantly stumbling over gaps left behind by our missing team members.
"Oh shit, a thing broke. Who is responsible for maintaining it?"
"Michael, Juli, Derek, and Diego.... all of whom are gone."
@nickdrawthing 100% true for most companies tbh. A lot of software that's been around forever have 'legacy' features specifically because they let people go without knowing what the created at companies they bought out & the core understanding of those features are lost.
You're already seeing this with retail reviews & customer services. People trying to navigate a cheaply spit out bootstrap website with chat bots as customer service have issues getting problems solved.
Telecommunications services can have someone on the phone for HOURS trying to sort out a bill issue with people. I already hit the 'take me to a person' button ASAP because a lot of answering machines did away with button input (why???) to be voice only.
How many issues on the bottom get solved because of some inside hacked together ingenuity that corporate can't know about? Because it's not 'proper protocol'. It's just the most efficient way the humans on the bottom learned to solve problems and make customers happy.
An LLM doesn't have the ability to learn beyond it's database. It's going to be given flowcharts to solve issues that ignore edge cases. Edge cases that tend to compound when not addressed properly.
Add comment