Source item
Open original source ↗TL;DR: Use a control plane, pick your model on a per task basis, do it massively cheaper as a result, keep your edge, don’t leak it to the frontier labs.
The thoughts below are exactly what we find in large enterprises that use 8090’s Software Factory control plane.
Our control plane is agnostic and sits above all the model chaos. You use it to manage your engineering team. It creates a more rigid conformation to the software development lifecycle so Owners and executives get well documented, governed, auditable software - not broken promises, vaporware pr large T&M bills. Engineers need to do a bit more work upfront but then are relieved of dealing with infinite slop in return.
For example, on a typical migration task of an enterprise workload (PHP—>next.js), when we chose Opus 4.8 inside our control plane, Software Factory gets to the right answer 1.5x faster and 1.4x cheaper than using Opus alone.
If an Enterprise asks our control plane to use an open weight model like GLM, instead, the costs fall even more dramatically. The migration is 16.4x cheaper but 3x slower but still works!
This brings up the obvious: at some near point in the future all large enterprises - ie those currently spending millions per month or more on tokens so they seem brilliant to a Wall Street analyst or their Board - will have to rationalize why the would spend so much more for inefficiency, poorer outcomes and data leakage to providers that increasingly also want to compete with them.
Quoted context
These are the quoted author’s words.
Coding is most of the LLM TAM, and half of that TAM is inefficiency. The models burn tokens generating garbage code and redoing it. Nothing else burns tokens like this. Deflate the waste away and there's not much left to sell, until physical robots.
dennisihong ↗