Outsourcing to another continent of humans and supplementing workflows with LLMs are entirely different operational universes. I think it is fair to put them on the same spectrum, but they're really far apart.
I'd argue outsourcing is a far more aggressive abdication of ownership of the technology than bringing an LLM agent in house and having it light a few fires under a few asses.
[edit] as the sibling points out, decayed system knowledge leads to relying on the LLM to fix the bugs the LLM introduced, which causes further decay in the institutional ability to reason with the business logic in code.
So the "knowledge base" an LLM generates is not useful as code, nor is it useful to humans. It may be useful to other LLMs as a lossy compression scheme for the original intention of the business logic and code.
That's not even in the same universe as institutional knowledge. Handing any serious business to something like that is malpractice, and sloppy beyond belief.
I'm not surprised that a lot of people think this way, because they never really grasped the benefit of holistic business knowledge united with code to begin with. Those people always outsourced, always got shitty code, and never really unified their systems. Cheap people and cheap companies take cheap exits. That's fine. But yes, many fragmented humans who all understand their portion in depth is much better than a bunch of markup files at retaining the knowledge of why things are done, procedurally, the way they are.
Once every six months the CEO calls me and asks me to remind him why our software does something like, idk, create a reverse payment instead of voiding a charge in some situation. Or some other thing he has asked a dozen times before. And I know the answer to why, or I know where to look, because I was in those meetings 5 years ago or because I wrote the code myself and asked the question when I wrote it.
Institutional knowledge is a very large context window, if you need to think of it that way, and LLMs are a shitty compression method for that. They can tell you how, but they don't reason well with why.
I think I know the reason to this one. Maybe. Because the money is already gone! There are no rollbacks in the banking system only "counter"-transactions.
I've, for better or for worse, jumped full-on in with LLMs, and I can already feel my abilities radically declining over time. That's fine by me, but if you're a company looking to protect your institutional advantage - just handing over everything to an LLM suddenly means anybody can do exactly what you're doing, literally. At best and this is an absolute best case scenario, you're transferring your advantage to the stewardship of another company.
The "if AI code breaks, who will fix it? -> "AI will fix it" exchange has (anecdotally) been very common among executives, which is much closer to outsourcing than programming.
Something completely different (but with the same logic): do you outsource legal, hire your own team of business lawyers or will you let customer services use AI for legal problems (and only hire a lawyer for a day in court)? I think all three solutions are currently active in different firms. From a risk perspective I would always want a lawyer on my team. Insource those learnings. But perspectives vary.
Moreover, any of us can run essential questions by each other, the marketing director, the lawyer, the CEO, the GM. And everyone has a stake. So all the creative and business decisions are worked out pretty quickly, and new features roll out with everything vetted and in place.
https://github.com/minimaxir/hacker-news-undocumented/blob/m...