Jimi Smoot

13.7K posts

Jimi Smoot banner
Jimi Smoot

Jimi Smoot

@jsfour

latent space astronaut, builder of https://t.co/4ms0PmkdnY

Los Angeles, CA Katılım Mart 2009
655 Takip Edilen1.4K Takipçiler
Sabitlenmiş Tweet
Jimi Smoot
Jimi Smoot@jsfour·
agents are misunderstood and that is the heart of the problem with adoption. companies expect to replace current employee workflows with agents but ai will always fail at this because the accountability structures within the company won’t allow it. what do you do when a person messes up? you reprimand them. you have an organization that is designed to correct people issues so this is easy. but what do you do when you drop an agent into this type of system and the agent makes a mistake? you don’t have the structure in place to resolve the issue so you end up in a failed state that you can’t recover from. this is what we are seeing is happening in companies. coding is different because the workflow for code (design, code, review, merge, test) is resilient to mistakes. you don’t generally trust any code from a dev without review/test so the dev portion of the process can be more fungible. but something like customer service doesn’t really work like this. there is no review step…it’s all live fire. then there are things like accounting workflows —something i’ve been working on. there is no generally agreed on tooling to handle things like a quarterly close that makes the human fungible. the workflow is usually filled with tribal knowledge and caveats that the agent designer probably didn’t know about. so really the tools / workflows need to be rebuilt to be ai first then people can adopt agents within the context of the tool. for many companies this will be very hard to do so we will continue to see failed pilots. the companies that will succeed will have one or more of the following; 1) no existing workflows thus they can tool up and agentify from ground up. 2) the understanding that you can’t replace existing workflows with agents but you can replace new flows with agents. 3) a very strong sponsor who can cram new workflows / tooling down the throat of the organization.
Indra@IndraVahan

some intern at mckinsey is probably slopcoating a report on this but let me give you an insider news: most large corps are not happy with the agentic systems & POCs they’ve done this year. 2025 was supposed to be the year of agents. so far it’s been the year of letdowns.

English
0
0
5
926
Jimi Smoot
Jimi Smoot@jsfour·
@mcuban man, would love to chat about this. its what ive been working on.
English
0
0
0
9
Mark Cuban
Mark Cuban@mcuban·
Every LLM is a walled garden in a race to beat the hell out of the next foundational model. They all are hoping it’s not like search with one dominant player. They have to invest like it might be. That won’t change for ???? Every enterprise has to keep up with their changing and new models and decide when to move. When to go side by side. When to delete. That’s going to be stressful. And as long as those models don’t truly integrate, and will that ever happen, the amount of work for enterprises to maintain AI and be competitive is going to keep on growing and getting more expensive. And there will be a time when genAI models will be superseded by world view models and who knows what comes after that It’s going to take so many people specializing in various layers and levels of AI In the next 5 years enterprise AI is going to be a mess, with all the different implementations and flavors and sources and models. It’s not inconceivable there can be hundreds of different models in each big enterprise. Just because the company got overwhelmed trying to keep everything tied together. Which in turn could lead very large companies to choose to divest subsidiaries rather than thinking there is benefit from scale. Scale may be a boat anchor to your business. Purely because of AI Curious what everyone thinks ?
Aaron Levie@levie

Whether it’s existing consulting firms, new ones that emerge, FDEs from agent vendors, or new internal agent engineering roles, the amount of work that is going to be created to implement agents in enterprises will exceed anything we imagine today. The complexity of implementing agents in any existing organizations is very real. When I talk to large enterprises, as you move from a chat paradigm to agents that participate in meaningful workflows, there are a number of things they need to do. First, you have to get agents to be able to talk to your data securely across your systems. In many cases, enterprises have decades of legacy infrastructure that contain the valuable context for AI agents. That’s going to take a ton of work to go modernize and move to systems that work well with agents. Then, you need to ensure that you’ve implemented agents with the right access controls and entitlements, the right scopes to be safely used, and have ways of monitoring, logging, and securing the work that they do. Next, you need to actually document the processes in the organization in a way that agents can utilize for doing the work. You also need to figure out what the new workflow looks like when agents and people are working together on a process, and who steps in where. Just replicating the old workflow will mute the gains. Oh and you likely need to create evals for your top new end-state processes. Finally, you have to keep up with a rapidly changing set of best practices and architectural shifts happening in the agent space. While it’s fun for people to change their personal productivity tools on a dime, it’s 100X harder to do this in a business process. The speed of change is a blessing and a curse right now for anyone trying to keep a stable system design. All of this means that individuals and companies that develop expertise on the above set of components (and more) are going to be needed to help organizations actually implement agents at scale. This is also the rationale for vertical AI agents right now that can go in deep on a business domain and help bring automation to it. This is a huge opportunity right now whether you’re doing this internally or as an external business provider.

English
171
51
555
289.6K
Jimi Smoot
Jimi Smoot@jsfour·
people aren’t talking enough about gemma 4. it’s pretty incredible.
English
0
0
1
23
Lex Christopherson
Lex Christopherson@official_taches·
I’ve officially cancelled both Claude Max plans and have 2 x Codex Max plans. Codex - particular GPT5.5 is the best coding model.
English
108
38
2.4K
560.1K
Jimi Smoot
Jimi Smoot@jsfour·
best comp we have for this is shopify. before shopify you would need to build and maintain ecomm stack yourself. this is a nightmare. after shopify you can still build a webstore that is custom, but they abstract away all of the pain.
English
0
0
1
24
Jimi Smoot
Jimi Smoot@jsfour·
i’m listening to the latest @chamath @Jason @friedberg @DavidSacks podcast about vibe coding and they get one thing wrong. people won’t need to vibe code apps soon. agents will build and maintain applications automatically. security should be abstracted to the api system that contains the apps.
English
1
0
0
56
Jimi Smoot
Jimi Smoot@jsfour·
@paulg this is what i’m working on. it’s great.
English
0
0
3
41
Adam Robinson
Adam Robinson@RetentionAdam·
RB2B is becoming a less-than-one-man machine. 3 people $8.4M ARR And for the next 7 months, almost none of us are touching it. Tate (CTO) gets one day a month for dev work. Robb gets 30 minutes a day on escalated tickets. I post on LinkedIn 3 times a week. That's the entire human footprint on the business. Last year, we let AI run it for 7 days, and it worked… …so now we're doing 7 months. If the bet pays off, an $8.4M ARR SaaS basically runs itself while we build something new from scratch. If it doesn't, I'm completely delusional, and you get a front row seat to watch. Either way, my livelihood is on the table.
Adam Robinson tweet media
English
13
5
75
6.7K
Jimi Smoot
Jimi Smoot@jsfour·
@sama a network of dumb fast models can also be smart.
English
0
0
0
13
Sam Altman
Sam Altman@sama·
i keep thinking i want the models to be cheaper/faster more than i want them to be smarter but it seems that just being smarter is still the most important thing
English
2.5K
381
13.2K
1.1M
Yijie
Yijie@yijiefeng·
@Trace_Cohen Surprisingly the typical PE firm I talk to is more AI pilled than many of my friends in big tech
English
3
0
17
4.2K
Yijie
Yijie@yijiefeng·
I'm noticing a trend there's a growing number of "AI consulting" firms charging $20K+ to "deploy Claude" to legacy businesses (mid-sized law, accounting, PE firms) as "Anthropic enterprise partners" what this means: - they install claude code, cowork - run a few commands to connect to tools - give generic or misleading advice on a tech stack meanwhile, there's more interest than ever for firms with 0 technical staff to build SaaS in-house and there's an entire industry of advice givers seeking to profit off of this trend last week I was on a call with a PE firm (working with one of these agencies) and someone who had never written code was asking whether to run a RAG vector DB on a Mac mini to chunk internal docs can't make this up
English
131
54
1.6K
254.6K
Jimi Smoot
Jimi Smoot@jsfour·
why does this read like a defi ad?
Jimi Smoot tweet media
English
0
0
1
15
Jimi Smoot retweetledi
0xDesigner
0xDesigner@0xDesigner·
this is so accurate 😂
English
260
2.5K
23.6K
1M
Jimi Smoot retweetledi
patagucci perf papi
patagucci perf papi@kenwheeler·
agent driven workflows with a sprinkling of deterministic tools are a fools errand. especially with subsidization fading, expect to see deterministic workflows with a sprinkling of agent nodes, doing what they’re actually good at.
English
80
34
557
53.6K
Jimi Smoot
Jimi Smoot@jsfour·
@paulg how could you defend against the model companies in law?
English
1
0
0
448
Paul Graham
Paul Graham@paulg·
Just went to visit Legora. Most impressive startup I've been to visit in years. They're going to surpass Harvey in 2027. After that their only potential rivals will be the model companies. And if ever there was a territory you could defend against the model companies, law is it.
English
192
138
3.1K
535K
Jimi Smoot
Jimi Smoot@jsfour·
@nbaschez Ive been working on this problem for a year and a half. Would love to chat.
English
0
0
0
92
Nathan Baschez
Nathan Baschez@nbaschez·
I've worked with a few companies on this and spent a ton of time thinking about it The hard part is if you want your employees using Claude, you don't have enough centralized control over their system prompt or skills, so no matter how well-organized your Notion or whatever is, the agent likely won't use it effectively But everyone wants to use Claude and is very happy to be locked in by them, assuming they'll build whatever you need in a few months if it's not already there (probably correctly?) Hard to find the right lane for this as a startup
Y Combinator@ycombinator

Company Brain @t_blom Every company has critical know-how scattered across people's heads, old Slack threads, support tickets, and databases, and AI agents can't operate like that. We think every company in the world is going to need a new primitive: a living map of how the company works that turns its own artifacts into an executable skills file for AI.

English
55
4
320
112K
Jimi Smoot
Jimi Smoot@jsfour·
The more interesting move, I think, is the opposite. Don’t build a system that makes you more powerful. Build a system that doesn’t actually need you. open.substack.com/pub/zachscorne…
English
0
0
1
15