CLAM retweeted
Replying to @pvncher
You’re living in a bubble. You need to understand that a whole world lives beyond the constraints you have manufactured or imagined.
For example the codex harness provides very little in terms of actual functionality - the same goes for most coding harnesses. They will be generally superseded by more capable specialized harnesses. Even if you scoped codex to only a coding-focused harness - which it really isn’t - it is lacking compared to purpose built coding harnesses that compete with it.
Right now labs have the advantage and can somewhat dictate terms but you should not believe that will be true forever. There’s seemingly a belief that we should be thankful for the (limited) capabilities we’ve been given- that we should allow a few companies in the world to dictate what we can and can’t do with technology. That’s never worked before and nothing makes this tech any more defensible.
In five years we will almost certainly be consuming local models for a majority of daily tasks, and for the things that can’t be done locally it’s going to be entirely commoditized. Once that’s true it means vendors will have to start competing by giving up more to the customer rather than the increasing restrictions being done today.
The most common reasons why AI pilots fail, even at the 'best' companies:
In order of prevalence:
1. Not starting with a thorough process mapping exercise (standard operating procedures vs. what’s actually happening across systems)
2. Automating a process step instead of the entire process (saving 8 mins in a 22-day process still leaves you with a 22-day process)
3. Not capturing baseline metrics for cycle time, cost per transaction, error rate, etc.
4. Building a sidekick instead of a background agent (chatbots will always only be used by ~10% of users)
5. Not embedding the AI into the organization’s existing systems of record (if users have to login, adoption will be low)
6. Not assigning an AI owner (IT built it, the business tolerated it, and no one was “on call” when it broke)
7. Not engaging legal, infosec, and finance early (we routinely see pilots “discover” these groups in month 3 - and get immediately killed)
8. Not scoping for exceptions (the “demo” only covers the “happy path” - but exceptions often represent 40%+ of process volume)
9. Not running the AI in “shadow mode” for a period of time to build confidence (going straight to production often leads to an AI mishap in front of the CFO)
10. Building with only a single AI model provider (one price hike or deprecation later, the pilot is a migration project)
11. Focusing on vanity metrics (e.g. # of logins, “adoption”) instead of business metrics (time saved, $ generated, risk reduced)
12. Not planning for month 7 (who will own and pay for the AI?)
13. Not engaging the subject matter experts (if you capture all their knowledge in an AI, what incentive do they have to help?)
Varick does enterprise AI the right way. Work with us below:
absolute fax
deleting the product
it's funny how you can sometimes tell if a team culture is dysfunctional just by looking at how their app is laid out. behind every feature, or tab in a sidebar likely lies a PM or someone responsible for an OKR.
the problem is when individual performance is measured by these metrics. it becomes the singular focus of the responsible person to make those numbers look good, since it determines whether they get rewarded or axed, even if it comes at the detriment of the overall quality of the product. this is why you mostly see features get added, but rarely removed. if you own a feature, then it being removed feels like an aura loss.
this is even worse in the agentic era when the cost to add features has become so low. you can simply will a new feature into existence overnight and add another tab. but users will notice that you ship your org chart.
teams that make people play silly games under the guise of performance management rarely build great products.
to build a great product you need to first fix your culture
32
CLAM retweeted
Crazy how no other AI agency has talked about what happens after a company is fully AI native.
- The dependencies and bottlenecks are external
- Lower level roles get grouped into higher level roles with more pay and responsibility
- people spend more time talking to each other and collaborating on new ideas
- AI chatbot usage trends downwards
X is three years behind
Yes
Another way to explain this:
if it was AGI then YOUR skill wouldn't matter, you could babble nonsense at it and it'd be good at eliciting what the hell you actually want and then build something you couldn't imagine. And if anything more recent models just feel like they have a higher and higher skillcap
30
This illustrates my point perfectly , I will die on this hill. All this “it subsidised” bullshit is bullshit. Inference will keep getting cheaper, just wait until affordable personal hardware ships it’s going to be insane.
GPT-5.6 Sol is now $4/$20 per 1M tokens – the cheapest frontier model out there.
Just for fun, I dug up GPT-4's original API pricing back in 2023. It was $30/$60 per 1M tokens!! For 8k context at the time. How far we've all come.
53














