>I think the rest of us should rest easy knowing that LLM's can't (and maybe were never meant to) tackle the tacit-knowledge-filled, human-system-centric, ambiguously-defined-problem-space jobs most mortals work
I don't believe that anymore, to be honest. Models are starting to get good at ambiguity. Claude Code now asks me when something is ambiguous. Soon, all meetings will be recorded, transcribed and stored in a well-indexed place for the agents to search when faced with ambiguity (free startup idea here!). If they can ask you now, they'll be able to search for the answers themselves once that's possible. In fact, they already do it now if you have a well-documented Notion/Confluence, it's just that nobody has.
It's probably harder to RL for "identify ambiguity" than RL'ing for performance algorithms, sure, but it's not impossible and it's in the works. It's just a matter of time now.
> Soon, all meetings will be recorded, transcribed and stored in a well-indexed place for the agents to search when faced with ambiguity (free startup idea here!)
We were doing that over at Vowel a few years back, unfortunately it didn't pan out because you're competing directly against Zoom, Google Meet, Microsoft Teams, etc. They are all (slowly) catching up to where we were as a scrappy startup 4 years ago.
It was truly game-changing to have all of your meetings in an easily searchable database. Even as a human.
Tacit knowledge is definitionally not recorded in any of these systems. This proposes to solve the problem of tacit knowledge by getting rid of it. It is not clear to me if that solution is either possible or desirable.
So self chosen total surveillance and transparency so your fav LLM can be better?
Why record when it can build in realtime as meeting is going on.
Slack is kinda there with Salesforce - can do a lot already on Agentforce and in Slackbot, but two aren't integrated just yet and Slackbot doesn't support group chats/channels. One interesting aspect in this will be - who has superiority boss, client, analyst or developer?
In coding the ambiguity is very, very limited and constrained compared to any non dev job that involves any decision making
Unfortunately you can't record meetings in many jurisdictions, including court sessions. Hence we have to rely - for worse, or perhaps even for better - on human driven note taking.
> Models are starting to get good at ambiguity
That's fair, and something I've observed too. I wish I had written "the rest of us shouldn't freak out and quit software today".
But here's another data point: At the biotech I work for, writing good code has never been the bottleneck. I actually told my boss that a paid Claude vs free subscription wouldn't be that much value because even if it took every piece of code or algorithm we've ever written and 10x-ed the hell out of them, we'd still be bottlenecked by the biology and physics which dictates that we wait 24 days for our histology assay pipeline.
I have a hunch most fields outside of software are this way. And I'm personally not planning to quit anytime soon.