Mayuresh Bakshi

482 posts

Mayuresh Bakshi banner
Mayuresh Bakshi

Mayuresh Bakshi

@bakshim

AI Engineering and Security. 2x founder. Early Engineering @AristaNetworks, @JuniperNetworks, @Cisco

San Francisco Katılım Ocak 2010
469 Takip Edilen259 Takipçiler
Andy Fang
Andy Fang@andyfang·
Today we're opening up the DoorDash CLI in limited beta. `dd-cli` lets you order DoorDash directly from your agent: search stores, find the best deals, check out, and more. Early access for US/Canadian macOS developers by waitlist. Excited to see what folks build!
English
1.1K
556
12.7K
5.1M
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
Great summary of problems on top of mind for every enterprise leader: - Siloed orgs make cross-process agents hard to govern and deploy at scale. - Fragmented data across systems makes it challenging for efficient use of agents - Once models are commoditized, proprietary context becomes the only real moat. - Measuring token consumption to business output is challenging - Multi modal world is reality and routing layer is crucial - Shortage of talent that can actually build and run agents in complex environments.
Aaron Levie@levie

Just coming off of meetings with a couple dozen enterprise IT leaders discussing AI agents. Here are a few of the common themes that stand out: * Lots of conversation that you have to solve an operating model challenge to get the full benefits of AI. Most companies have orgs that have always operated in siloes; but agents are most effectively when they are tied to a process, which often cuts across these siloes. So the big question is how do you start to deploy centrally managed agents that can work across organizational boundaries. Who manages these agents? How do they get deployed and adopted? * Data fragmentation remains a major issue for most organizations. As long as data remains highly fragmented and not in standard formats, or data is not available to the right people and agents, enterprises are dealing with issues around being able to get answers from agents that are accurate or that conform to their business practices. This cuts across both systems with structured data (product metrics or revenue figures) and unstructured data (product roadmap or customer contracts). * Clear sense that companies need to figure out what their core data moats are going to be in the future. If everyone has access to roughly the same superintelligence from the various models, then the context that you feed the models becomes proprietary value in the future. Capturing this data and getting it into a format that agents can use becomes very important. * Everyone is trying to figure out the right metrics to manage to for AI adoption. General consensus that tokens are not the right metric per se, and people leaning more toward business outcomes (in an ideal world). For business outcomes (like more revenue or more shipped product), though, you have to get close to each individual workflow to figure out if it was successfully transformed with AI so it’s harder to manage top down. * Growing view that enterprises are going to live in a multi-model world. Lots of interest (though early in actual adoption) in layers that can route workloads to different models (frontside or open weights) for cost or performance reasons. Also enterprises are trying to figure out what things do you give to the models directly vs. what do you separate as horizontal systems and context so you can swap any system in and out. * Talent for driving AI adoption and implementation still remains a major issue and topic. Many view it as something you necessarily have to train for internally due to a shortage of talent being trained on this in the outside. As an aside, this feels like it remains a huge opportunity for those that get very good at deploying and management agents in an enterprise since most companies are looking for these skills. * The best use-cases for AI tend to be those that fundamentally change the work being done instead of just replacing an existing process and doing it more efficiently. Companies are working through their versions of this individually because it’s different per industry, but this often remains both the most exciting and higher upside uses of AI. Many more topics discussed recently, but overall it’s clear that there’s a ton of change going on with much more to come.

English
1
0
1
38
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
All great points and very much on top of every enterprise leader’s mind. With models becoming commoditized, the real moat does shift to proprietary context and how it’s structured for agents. In practice, turning raw event streams into agent-ready context at scale is tricky both for consistency and freshness tradeoffs. Curious how other teams are tackling these?
English
0
0
0
64
Aaron Levie
Aaron Levie@levie·
Just coming off of meetings with a couple dozen enterprise IT leaders discussing AI agents. Here are a few of the common themes that stand out: * Lots of conversation that you have to solve an operating model challenge to get the full benefits of AI. Most companies have orgs that have always operated in siloes; but agents are most effectively when they are tied to a process, which often cuts across these siloes. So the big question is how do you start to deploy centrally managed agents that can work across organizational boundaries. Who manages these agents? How do they get deployed and adopted? * Data fragmentation remains a major issue for most organizations. As long as data remains highly fragmented and not in standard formats, or data is not available to the right people and agents, enterprises are dealing with issues around being able to get answers from agents that are accurate or that conform to their business practices. This cuts across both systems with structured data (product metrics or revenue figures) and unstructured data (product roadmap or customer contracts). * Clear sense that companies need to figure out what their core data moats are going to be in the future. If everyone has access to roughly the same superintelligence from the various models, then the context that you feed the models becomes proprietary value in the future. Capturing this data and getting it into a format that agents can use becomes very important. * Everyone is trying to figure out the right metrics to manage to for AI adoption. General consensus that tokens are not the right metric per se, and people leaning more toward business outcomes (in an ideal world). For business outcomes (like more revenue or more shipped product), though, you have to get close to each individual workflow to figure out if it was successfully transformed with AI so it’s harder to manage top down. * Growing view that enterprises are going to live in a multi-model world. Lots of interest (though early in actual adoption) in layers that can route workloads to different models (frontside or open weights) for cost or performance reasons. Also enterprises are trying to figure out what things do you give to the models directly vs. what do you separate as horizontal systems and context so you can swap any system in and out. * Talent for driving AI adoption and implementation still remains a major issue and topic. Many view it as something you necessarily have to train for internally due to a shortage of talent being trained on this in the outside. As an aside, this feels like it remains a huge opportunity for those that get very good at deploying and management agents in an enterprise since most companies are looking for these skills. * The best use-cases for AI tend to be those that fundamentally change the work being done instead of just replacing an existing process and doing it more efficiently. Companies are working through their versions of this individually because it’s different per industry, but this often remains both the most exciting and higher upside uses of AI. Many more topics discussed recently, but overall it’s clear that there’s a ton of change going on with much more to come.
English
203
247
2K
508.4K
Mayuresh Bakshi retweetledi
Nikesh Arora
Nikesh Arora@nikesharora·
Just finished north of 200 meetings in Europe with customers and technologists. The conversations were primarily around AI, common questions include: 1. Are there examples of organizations who have been able to demonstrate production level systems and do those developments show a return in lower cost, efficiency or better top line? 2. What do you think about agents? How will we discover, govern and stop agents if need be. Perhaps the biggest security concern ATM. 3. The frontier AI models are expensive, what's the business case at these token prices to embed AI in our customer facing products? Where will token prices be in the future. 4. What are the longer term implications of Mythos like models? Do we need to update cyber infrastructure or all IT infrastructure? 5. What do you think of Chinese opensource models? Are they secure and what is the downside of using them if they can be secured and they are cheaper? The parts that surprised me were: 1. The pausing of Mythos and Fable 5 caused more consternation and concern in Europe both short term and raised longer term concerns on single model reliance or reliance or models not in ones control. I hadn't seen it from their POV. 2. Sovereignity which was always a topic and still is, is getting more nuanced - they want data residency, data localization and local resources, but there seems to be more willingness to accept global services on clouds. Classified systems continue to be an issue. Net net - we need to ensure we continue to build trust both on our Frontier models and their consistent availability, we need to get the right economics in place and spend more time in Europe communicating and building presence if we want AI adoption to keep pace with the US.
English
94
216
2.4K
1.3M
Mayuresh Bakshi retweetledi
Xiaoyin Qu
Xiaoyin Qu@quxiaoyin·
China’s AI playbook: kill OpenAI and anthropic with free great models. Make it free. Then use cheap electricity to export compute as well. Currently the blocker is chip but Hauwei would catch up soon. Imagine a world where instead of paying hundreds of billions to OpenAI and anthropic, you pay almost zero to similar level of intelligence with cheap cheap inference. What’s gonna happen?
English
659
860
7.2K
1.3M
Mayuresh Bakshi retweetledi
Nir Eyal
Nir Eyal@nireyal·
Confidence isn't knowing you'll succeed. It's knowing you'll figure it out. Most people get this backwards. They think confidence is the feeling you get after you've already won — the certainty that the next thing will go your way because the last thing did. That's not confidence. That's a winning streak. Real confidence is quieter and more useful. It's the belief that whatever shows up, you'll find a way through it. Not because you have the answer in advance, but because you trust yourself to work the problem when it arrives. This matters because the first version — "I know I'll succeed" — is fragile. The first failure breaks it. The second version — "I'll figure it out" — gets stronger every time something goes wrong, because every problem you work through is more evidence that you can. Beliefs aren't facts. They're tools. And the belief that you'll figure it out is one of the most useful tools you can carry.
Nir Eyal tweet media
English
4
6
28
2.1K
Mayuresh Bakshi retweetledi
Nikesh Arora
Nikesh Arora@nikesharora·
Woke up in London to all the conversation of Chinese Cybersecurity models getting to Mythos like ability with agent swarms. Swarms that can explore vulnerabilites, determine attack paths and potential fixes in addition to persistent red teaming. Happened just under 3 months, faster than my optimistic estimate. Expect that in a few weeks there will be more widespread capability. Highly likely that we will get US models released from bans faster with a promise of better hygiene. What does it mean for the rest. 1. Test your own code! 2. Validate your vendors, ensure they are doing the same. 3. Start evaluating direct and virtual patching approaches to ensure open source is protected. From a longer term perspective, we will need to ensure better security posture, no, no misconfigurations, robust platform products which can react swiftly, and a culture of constantly testing the enterprise with the most recent tools out there.
English
55
116
1.4K
1.9M
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
In mature, deployed systems the Maintainer and Sweeper roles rightly take center stage to protect stability. The practical question becomes how a Prototyper can still run fast, low-risk experiments on top of substantial legacy code (via flags, abstractions, or sandboxes) without creating the very technical debt the later roles then have to pay down. Curious how teams are making that Prototyper-to-Builder transition reliable at scale.
English
0
0
0
190
Boris Cherny
Boris Cherny@bcherny·
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
English
887
2.4K
19.8K
3.1M
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
@petergyang Both can co-exist, doesn’t have to be one vs other, it depends on the consumption use case IMO.
English
0
0
0
17
Peter Yang
Peter Yang@petergyang·
I'm trying to wrap my head around these two ideas: 1. Cloud agents are coming we should use VPS vs. our laptops 2. Everyone should buy hardware to run local models Aren't they conflicting a bit?
English
277
20
718
131.6K
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
@levie @paulg When cyber AI hits open availability, security tooling economics change fast. Expect a wave of composable agents for continuous verification rather than periodic scans, worth exploring how that integrates with cloud-native infra at scale.
English
0
0
1
172
Aaron Levie
Aaron Levie@levie·
It should be 100% obvious that there will soon be mythos level models on cyber security that are open and available to anyone. As a byproduct of this, alternative tech stacks will emerge that also drive more economic value and control away from the US’s tech stack. This is what should be considered when thinking through the gate keeping you want to have in AI. If advanced models will become open and available regardless, then by not allowing the release of models you’re neither more secure nor better off strategically. So much of the regulatory approach to AI has to assume China can’t catch up, when all current evidence suggests they can and are. And further, hard to imagine a higher priority than winning in AI for China; so you’re basically betting against their long term ingenuity, talent and motivation. Seems like a bad bet. So your options are either to create gates around your best models, which means you’re asymmetrically disadvantaging yourself, or you work to ensure you’re always at the frontier and driving the future architectures of AI.
Polymarket@Polymarket

JUST IN: A new Chinese AI model from Zhipu AI reportedly matches Claude Mythos’ performance at finding security bugs.

English
85
93
809
177.7K
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
Super clear breakdown, thanks @brian_armstrong . On the routing layer: do you use a small dedicated classifier model (or rules/embeddings) for preprocessing, or is it fully prompt-based with another LLM? Curious about the added latency and how you measure routing accuracy to avoid sending the wrong model.
English
0
0
0
705
Brian Armstrong
Brian Armstrong@brian_armstrong·
How to keep AI spend flat while token usage grows exponentially: Not with friction and spend alerts. With better defaults, routing, and caching. Better Defaults (not Usage Caps) – Engineers can choose any model they want, but defaults matter. We’re experimenting with defaulting to open weight models like GLM 5.2 and Kimi 2.7 through our LLM gateway, while still encouraging engineers to choose the right model for the task. 91% of our employees were never hitting their usage caps, so instead of lowering caps and driving up alerts, we're moving to cheaper defaults. Note that code reviews use a diversity of models, so they can check each other's work. Better Routing – In our custom harnesses, we preprocess prompts and route to the best model for the job, considering cache hits and model pricing. For instance, you may want a frontier model for planning, but not for execution where they can be overkill. Ultimately, humans shouldn't be choosing models - AI can automate this task. Better Caching – Cache misses are the easiest way to drive your cost up. All of our requests are cache aware, so we’re reusing a warm cache wherever possible. For example, our cache hit rate went from 5% → 60% in LibreChat once properly implemented. Keep Context Lean – Start fresh sessions when switching tasks. Scope file context narrowly. Disconnect unused tools. Don't just compact. The goal isn't fewer tokens used, it's fewer tokens wasted. Better Visibility – Our engineers can use as many tokens as they want, from whatever model they want, but we’ve made usage visible – and the more you spend on AI, the more impact we expect. The goal isn't to suppress usage. It's to build the infrastructure that makes exponential growth sustainable. Putting this into practice has cut our AI spend nearly in half, while our token usage continues to grow.
Brian Armstrong tweet media
English
474
745
6.2K
4.2M
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
AI overhype :) When builders are still struggling to go from prototype to production, tweets like this make the disconnect painfully obvious.
Bhavish Aggarwal@bhash

Got on the vibe coding bandwagon and built a bunch of AI agents this week for @OlaElectric. Wow! So many layers get built between the actual doers and the founder as the company scales. Agents will take away all middlemen in a company who are only “managing people” and not doing any problem solving! And the people actually building will be even more valuable 🫡

English
0
0
0
96
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
Love the opinionated stack for consistent controls @jedwards_27. Once these AI-generated apps are live and being used/composed with other tools, what kind of continuous security monitoring or anomaly detection do you have in place? Things like unexpected data access patterns or behavior changes. Also curious to know more about any sandboxing used to host
English
2
0
4
13K
Jude Edwards
Jude Edwards@jedwards_27·
AI can build an app in an afternoon. But getting it safely into other people's hands is a whole other challenge! This is the problem that I've been working on these past few months. I'm proud to finally share how we solved it with Block App Kit! engineering.block.xyz/blog/from-loca…
English
40
76
989
809.2K
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
Apple moment for OpenAI. Massive ~840mm² compute die + 6 HBM modules. Optimized for inference - custom silicon era for inference is here. NVIDIA still leads in versatility, but specialized chips like this will drive the next cost curve down
OpenAI@OpenAI

We’ve designed and built our first AI chip: Jalapeño. Designed from the ground up by OpenAI and brought to production with @Broadcom, Jalapeño is purpose-built for the LLM workloads powering ChatGPT, Codex, the API, and future agentic products. Chips are foundational to the AI economy. Building our own expands our full-stack platform from products to models to infrastructure, and will help us scale intelligence, serve more people, and expand access to AI.

English
0
0
0
69
Mayuresh Bakshi retweetledi
Arnav Gupta
Arnav Gupta@championswimmer·
Every piece of software I use which used to be originally produced with a lot of care has gotten shitty. Just to make a list from top of my head... 1. Starting with this site. I used to give an example of how the Twitter mobile app was epitome of saving list scroll state across app lifecycle and even app death, all the way back in 2016 when teaching mobile development to my students. Today, most tweets > 2 day old if I open, the replies do not load, I don't get notifications for DMs, and random parts of it don't work at random times. 2. MacOS which was once more polished than Windows on the UI and as hackable as Linux from inside out - now randomly freezes, has kernel panics, needs disabling needless safety features all they way from safe mode to get basics working or toning down the horrible glass UIs. 3. Spotify used to be one of my favourite products, having great offline-first experiences, seamless sync across devices, handover of songs midway between phone, desktop, car, etc. Now the app can't even load offline downloaded playlists properly when internet is down, sync almost never works, UI glitches, watch app can't figure out how to play on headphone, or when to sync from phone to watch. 4. Whatsapp - one of the most performant apps, with solid delivery rates even with as slow as 2G/EDGE internet, now actually has dead-end UI flows (when sending photos, trying to edit it can lead to an unknown state), message deliveries often don't work even on solid internet, and media uploads frequently need retries. 5. Microsoft's entire office suite which used to be a workhorse product - something so reliable, that non-tech people would never touch Google Sheets with a 10-foot pole and threaten to resign if they didn't have a proper desktop app license of MS Office. Now they push you towards the cloud versions which work way worse than Google Workspace, and have add tons of React UI elements in the Desktop apps that makes then visibly slow and janky and large Excel sheets even crash sometimes. Most of these were on the trajectory of enshittification before wide-scale agentic coding or Claude-driven development was even all that common. The entire industry is in a phase where everyone is just building things because it is their job, and the era of care, and sincere craftsmanship of products has mostly come to an end.
English
70
113
1.1K
52.2K
Mayuresh Bakshi
Mayuresh Bakshi@bakshim·
Great thread @nikesharora. Cheap tokens unlock pilots, but deployment needs verifiable outputs. How do you see FDEs evolving to deliver deterministic guardrails + explainability at scale? Will this shift model labs toward more “consulting-like” roles (owning workflows + edge-case training) rather than pure model providers? Curious if verifiable AI becomes the real Phase 2 moat over raw capability.
English
1
0
4
17.1K
Nikesh Arora
Nikesh Arora@nikesharora·
The AI Business model trap: LLMs want cash flow to fund the race to AGI or the next model. Enter free consumer AI - they are losing a lot of money on the breadth of models to serve consumers for free! They are caught in the post training data trap, free consumer usage feeds post training needs, it can't be right to stop serving customers for free? But they need money for the compute: The monetization challenge is being pointed to Enterprises. Phase 1 - seemed easy, value capture in coding, the most bottom up motion in enterprise - with low customization per customer. Developers continue to train coding, tasks and eventually will train flawless skills. Phase 2 is where the challenge lies, showing true enterprise value. The promise of efficiency, accuracy, elimination of resources - that requires a different approach, build depth with harnesses, context, memory, solving for edge cases with deterministic guardrails! Build skill libraries - enter FDEs. Yes,FDEs will train the enterprise Waymos of the world. The risk - high token pricing for enterprises while consumers for free! Yes for consumer distribution businesses (aka Google, Meta, Apple, etc) it makes sense to hold on the distribution with free AI. If you want to win enterprise, you should be forward pricing tokens. The cheaper the tokens for enterprises it will allow for experimentation, workflow reimagination - instead CIOs are busy restricting AI use and working on making the use more efficient! Paradox: They still haven't fully understood and embraced the value of AI in the enterprise. If I were them: 1. Cut token pricing now, else send enterprises to secure opensource and end up with friction filled routing layers. 2. Show me how enterprises can use their context, training and data as their competitive advantage. 3. Build tools for rapid edge case learning and reducing false positives. @HarryStebbings @sama @DarioAmodei @demishassabis
English
195
362
4.2K
6.7M
Mayuresh Bakshi retweetledi
Deedy
Deedy@deedydas·
Most software engineers are facing an identity crisis bordering on depression. As CTOs aggressively evangelize tokenmaxxing, a class divide ensues. The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working. The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy. This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.
English
345
492
5.1K
1M