# Scaling AI Adoption in Large Engineering Teams

**Podcast:** How I AI
**Published:** 2026-03-02

## Transcript

People are skeptical that large, established, highly technical, highly capable engineering organizations can deploy AI at scale and get any effect.
But I think you've proven it's possible.
It's not only possible, it's adapt or die.
It's just been such a huge superpower for the team.
How many engineers are we talking about here?
A thousand plus.
So we're not messing around here.
The company tried to adopt other AI tools and we saw this uptick in adoption.
People opened it up, checked the box, did kind of like a hello world thing, but it didn't.
stick.
My biggest thing is how do I make this damn thing stick?
Because there's something here.
I do think that it's really important when you're doing this organizational transformation that you have a single person with incredible conviction at the leadership level who is also hands on the metal.
Show the engineers, not just tell.
And the worst thing any engine leader could do is just be like, I decree you must use AI.
Come on, no one's going to listen to you.
Welcome back to How I AI.
I'm Claire Bowe, product leader and AI obsessive here on a mission to help you build better with these new tools.
Today we have Chinthan Tarakia, Senior Director of Engineering at Coinbase, and he's going to show us, yes, it is possible to drive AI adoption and higher velocity in an engineering organization of thousands of engineers.
He's also going to show us the new expectations for engineering managers and engineering leaders, which is...
less meetings, and more code.
Let's get to it.
This episode is brought to you by WorkOS.
AI has already changed how we work.
Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically.
But there's a catch.
These tools only work well when they have deep access to company systems.
Your copilot needs to see your entire code base.
Your chatbot needs to search across internal docs.
And for enterprise buyers, that raises serious security concerns.
That's why these apps face intense IT scrutiny from day one.
To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features.
Building all that from scratch?
It's a massive lift.
That's where WorkOS comes in.
WorkOS gives you drop-in APIs for enterprise features, so your app can become enterprise-ready and scale up market faster.
Think of it like Stripe for enterprise features.
OpenAI, Perplexity, and Cursor are already using WorkOS to move faster and meet enterprise demands.
Join them and hundreds of other industry leaders at WorkOS.com.
Start building today.
Chintin, thank you so much for joining.
What I love about what we're going to talk about today is we've spent so much time talking about the individual vibe coder or the non-technical person becoming a software engineer, and still people are skeptical that large, established, highly technical, highly capable engineering organizations can deploy AI at scale and get any effect.
There's still so much skepticism, but I think you've proven it's...
possible.
And you're hopefully going to show us the way.
I think it's not only possible, it's, you know, adapt or die.
Like, it's just been such a huge superpower for the team.
And we've gotten so much efficiency out of it.
And there's just like ways to approach it.
I think I was reading a tweet yesterday, just about a very, very long story at Microsoft or someone like pulling Copilot in to their organization.
And it was just like just a fun tweet of just like, yeah, we're going to make graph go up into the right.
But like the actual adoption wasn't good.
And so like I've been spending the last year just absolutely obsessing about it.
And you can do it.
People can do it.
So how how can you do it?
Because, you know, how many engineers are we talking about here?
A thousand plus.
Yeah.
So we're not messing around here.
Yeah, we're not messing around.
This is a real team working on real products who know what they're doing, who have built great software.
And so where did you start?
Either culturally, from a product perspective, from a tools perspective?
So I think a lot of it actually just started around this time last year.
We had some changes to align the product I'm responsible for.
And a big part of that was...
effectively like rewriting the entire product from scratch uh from uh turning it from a self-custody wallet to actually a social consumer app that just happens to use crypto and you know we're using react native um but we made a lot of decisions for a self-custody wallet but to become a consumer app you gotta like rethink everything that was one Two, we needed to do it in like six to nine months.
So we were going head to head with like the big social players out there that have multi-thousand person teams that have a 10-year head start.
And we were really trying to just do something big and new and crazy, like absolutely just crazy.
And a big part of this is like, how do we rewrite the app so that it is the best possible app out there, like consumer grade, and do it in this insane timeline?
And the team is cracked.
They're amazing.
But like, you know, we became a smaller team as a result of some of these changes.
And so I started just looking at like ways to accelerate.
And, you know, like, I don't know, my team knows me well.
And if you know me, like, I obsess about efficiency.
And I think that's like so critical to like make teams accelerate their velocity.
in ways that make sense uh for tool and using the tool so around this time i think cursor had come out with their sort of initial release it was around like november of last year we we all tried it right 2024 and it kind of sucked and it's not like i love cursor i love cursor uh the models weren't there just the models weren't there like the models couldn't even you know really write a unit test right well and you know you're an engineer um and you understand like once once an engineer tries a tool and and they're like ah this is not so good like it's very quickly and very easy to write it off right it happens and so we we kind of went through this like trough of sorrow of just like okay god damn it ai tools are not here the models aren't ready what are we going to do and you know for even a year prior to this event like the company tried to adopt other AI tools like GitHub Copilot.
And we saw this like uptick in adoption.
Like people opened it up, checked the box, did kind of like a hello world thing, but it didn't stick, right?
And like my biggest thing is how do I make this damn thing stick, right?
Because there's something here, right?
And my mental model was just always the models will, the foundational LLMs will always get better.
And it's like going to the gym.
You need to go and build your reps and try.
And that's okay.
And the cost of doing it is like nothing.
It's just a little bit of wasted time.
We're not worried about compute right now because it's so early.
And so like from basically January all the way to like March or April of 2025, I just changed the mindset and the mentality.
I was like in cursor every single day, every single hour of the day.
And I was like, how do I make this work?
Right?
You know, it was great because I was writing code again.
It was great because, you know, it was unlocking all these like use cases.
Like we were doing interviews, like interviewing candidates and just like, I don't want to necessarily write up all the notes.
Right.
That takes a long time.
But I intuitively I like I know I've assessed.
Right.
So I would use it for like tactical day to day paperwork kind of things to accelerate me.
But also from like a coding perspective, we just pick up bugs and be like, hey, let's try this.
Right.
What's going to happen?
What can I learn?
What are the tips and tricks to like show the engineers, not just tell?
And the worst thing any engineer could do is just be like, I decree you must use AI.
Like, come on, no one's going to listen to you.
I have to empathize with this because I also running a large, like multi hundred person engineering organization, you know, was experiencing even early versions of these tools and had such innate conviction.
That it would, of course, transform how we did work.
That was very obvious to me.
I don't know if it's obvious because of experience or obvious because it was just obvious.
But then you just had these experiences as leaders, especially maybe 12 months ago.
One engineer tries it, doesn't work.
It's not just that engineer throws it away.
It's everybody else says, well, I think, you know, I trust their opinion.
And if they say it's not going to work, it's not going to work for me.
And I do think that it's really important when you're doing this organizational transformation that you have a single person with incredible conviction at the leadership level who is also hands on the metal.
Because until you can say, well, I understand it didn't work for that, but it worked for these three things.
Or I actually figured out how to make it work for that because we tried A, B, and C.
I think it's just the only way.
You cannot be in philosophy.
You cannot be in, you know, someday in the future, you figure it out.
You have to actually get back to it.
And then I think like bonus points.
So many of us in engineering leadership have like been pushed away from coding.
I know.
I was so happy to get back in it.
And I'm like, I just want to code again.
Like, give me some joy.
Give me some time.
And so I think that's the benefit as well.
And you have to show, not tell.
And so I did.
And like, I think what I learned very quickly is like, okay, there's something here.
There's a there, right?
And then we just started picking off like one or two use cases.
And the best way to get to an engineer is just give them the tools so they stop doing the shit work and so that they can build the stuff they love, right?
Right.
And so like, we would just like pick off unit tests.
We'd pick off like linting, all these like little things that just like paper cut and suck the soul out of you as a builder.
But the engineers and, you know, like the team just wants to move faster.
The team wants to build better things.
And so we started leaning into like cursor rules for some of these things.
Even the simplest thing.
I remember like, I think I remember my aha moment, which was like popping in some bug report, working through it.
And then I didn't think about it.
I just did it.
I was like, just create a draft PR.
Here's the ticket.
Here's kind of the PR delete.
And, you know, here's the PR description I want.
And it just did it.
And I was like, I never need to remember get status, get rebased.
Not like, why is anyone doing this anymore?
Like, like, what are we doing?
And it took a funny thing is it took some convincing of me to the team.
Like, guys, just type, create, draft a PR, like create a draft PR and it'll be done for you.
And like, like, well, you know.
I kind of have my workflow.
It's like, cool, cool, cool, cool.
I get your workflow.
You can modify it.
You can use cursor rules.
It's okay.
Like no one's getting bonus points for memorizing Git commands.
Exactly, exactly.
And so like we chipped away and we put in a bunch of rules, like cursor rules, and that helps so much.
And then like I was like sensing, I was like, okay, I have enough like folks on the team that are like, yep.
this is unlocking stuff and they would post in the team channel like look what we had literally a channel called cursor wins and like everyone was just posting in the channel like i just did like you know 20 unit tests and then went and had a coffee this was great like i love it and so people started seeing it in action and then we hit this like point i was like okay how do i speed run now the whole team there's a there's a little bit of conviction here so we just and i remember this like I think I had landed.
I was going to the East Coast.
I landed for my flight, got into an Uber, hopped on like an entire team, all hands, like speed run.
We call it, it was like basically cursor speed run.
And I was in the Uber using cursor, putting up a PR.
And the goal of the speed run was every single person would just pick up the most trivial thing.
It could be like copy change, a bug, whatever, and just put up the PR.
And we ended up, I think in 15 minutes, I think 100 people had joined.
In 15 minutes, we ended up putting up like 70 PRs.
And we broke GitHub too, which was cool because we learned like our infrastructure needed improvement.
So I want to pause real quick because, again, How I AI, a little bit about tactical techniques.
And you've used a couple that I have used, which is like one high conviction leader with hands on the metal that just says like, we just got to do this.
Access to tools.
Focus on toil.
I think it's very important.
You called out linting.
You called out tests.
Another one I would call out is like design debt where, you know, front end engineers or designers have just lived with parts of the app they hate.
Yes.
That is another really great one.
But and then and then a shared Slack channel and one like, you know, riff I would make on your cursor wins channel is we made ours wins and losses.
And so we were very clear like.
just post what you did and when it worked and when it doesn't because when it didn't people would be like oh yeah but you could try xyz or i have a cursor rule for you or whatever but what i haven't heard that i want people to just like perk their ears on and pay attention to is this like idea of a pr speed run which is like do a time down time everybody boot up whatever tool and just speed run some fixes because how much conviction does an org have to get Going from, look, I've been there, like the doldrums of like quarterly planning and this will be in four months and blah, blah, blah, blah, blah, to just like, we just got 70 PRs that we've been sitting on out the door in 30 minutes.
I just, that has to be such a transformational moment for an edge team.
You know, there was a success rate on those, on merging those PRs and like, it was just like, shit, this is possible.
They're like, everyone's eyes lit up.
And it was really sort of a death to status updates, long live building moment.
Yeah.
And this is the other thing I want to call out because I think you all have a really special culture there.
But so often we in product engineering design orgs get like really wrapped around the axle on like the rules of engagement.
Well, I'm not allowed to build it unless the product manager says it's important.
Or like, I can't really make that decision about what color that button is because design hasn't weighed in.
And like, I do think these moments where you just break all the rules and you're like, guess what?
Remember, you can just ship code.
You can just ship code.
Like put AI aside.
AI maybe enables it and makes it like a much less costly, you know, expense.
But like just doing that.
So powerful for velocity and for I also think for quality, like people just take more radical ownership of things.
So I'm going to 100 percent steal this.
I mean, I want everyone to steal it.
Like, you know, I really like the way you just put it right.
This is a moment where we should be breaking the rules because AI is breaking the rules for us.
And if we don't adapt to how like we can use it, we're toast.
Right.
And we is like a very collective, like whoever's not adapting is going to fall behind kind of thing.
Right.
And what all of this like ends up unlocking is like the reduction in coordination overhead.
So like one thing I've been obsessing about a lot is like, okay, cool.
Great.
Good job on the speed run.
Yes, we got a lot of stuff done.
We started then seeing those wins.
More and more people adopted.
Brian then, you know, we were sharing some information with Brian, like how adoption is going.
And then we just did a company-wide speed run.
And at that moment, like there was like 800 engineers on the call and we ended up pushing up for like three, four hundred PRs in 30 minutes.
And yes, again, we broke GitHub and that's fine.
That's good.
Like this is pressure testing.
We should be designing ourselves to break the rules.
Right.
But the thing I've been obsessing about is like, how do you how do you measure any of this like in terms of output?
Right.
There's there's this like tension where, OK.
The more AI we use, well, does that count as a replacement for people?
And like, I'm in the camp of absolutely not.
AI is an accelerant, right?
AI is an accelerant because there will always be more work to do, right?
And so the way I think about it, at least for my team and what I'm pushing across the board, is really like time from ticket to when the change lands to the user.
Like that actually encompasses every single piece you need.
Right.
And today, like even if you go from like ticket backlogs and stuff like that, like there's, oh, do I should I like like you said, should I prioritize this?
Is this important?
Let me ask my PM or let me ask the program product manager, project manager, whatever.
And now the whole team, like fast forward from back then to now, we just see someone give us feedback.
And literally within like seconds, we're like, we built this internal bot up.
I'm excited to show you.
And within seconds, like the PR is being authored, right?
An agent picks it up.
And within seconds, that feedback is like acted on.
And so we crunch the time to action.
The time then from ticket to the PR being ready for review.
Then the review time, like all my devs complain, review times take too long.
We found some solutions actually.
I think we were doing average of like 150 hours, like was the cycle time for a PR review because there was so much.
We reduced it by 10x down to like 15 hours or so, roughly.
And then the last piece is like from that merge, how do you do like that OTA update?
And you squeeze that whole cycle again.
And then the team is like just literally unlocked with sheer velocity.
Yeah.
And then you get stuff in front of customers.
Yes.
And then you have the velocity of like actual market ideas.
Yes.
And you get that feedback.
And we're obsessing also about how fast can we take like in real life feedback.
Yeah.
And then actually just fix it right then and there.
I think there is another aha moment.
I was on a call with like a user of our product, right?
And they're like, hey, it'd be cool if you like changed X, Y, and Z.
And literally while I was on the call, I just.
put up a pr and pushed it and they're like before the call ended it was 30 minutes i was like just you know reload that it's fixed okay before we put this into an hour of you know like two two end product leaders being like just ship really fast we'll go into the merits of reducing pr cycle time all that fun stuff let's actually show a couple things you built because i think The kind of meta commentary on like you can do this in engineering organizations.
There are steps to it.
There are measures you can take, I think, are things that everyone can learn from.
But you also have been building.
So let's talk about how you used actually cursor to drive how you drove this into the organization and understand adoption of AI.
Yeah, for sure.
I think a lot of it just comes like from honest curiosity and figuring out.
where the bottlenecks are like why aren't folks adopting how are people using it etc etc i want to show you like i think the the kind of crazy thing i'm about to walk you through is like i just got this harebrained idea cursor has like great analytics right and so you go to the admin panel you look at the analytics and uh you know awesomely they let you download into csv i was like what if i just use cursor to figure out what my team is doing in terms of using cursor But not in just like from a vanity metric point of view of like lines of code committed by AI.
I think that's like kind of misleading actually digging more into how they're using cursor and how do we sort of like replicate power users.
So let's see.
We have some data.
It's in this file here.
And it's just like a standard CSV from cursor that you can like download from their site.
um like your admin panel and then there's also here a bunch of different sort of fields um so like accepted lines chat lines chat lines deleted um various like data elements but you know one thing like i just sort of started with i want to understand the usage of cursor right and i already know um we have like light users all the way to power users And one of the things I really wanted to figure out was like, what are the natural clusters of usage?
Can you find them across the team?
What is the best way to cohort them?
Right.
And I'm just going to pick up the standard analytics file here, maybe pop in another one here.
And then I love Opus High.
I also love plan mode because it gives you a chance to like see what it's thinking through.
So we can let this cook and see what it comes back with.
And what I want to call out here for engineering managers or engineering leaders is this is the kind of quantitative analysis that we would all have loved to be able to do across a bunch of engineering metrics at some point, right?
Like how often do we get asked by...
The board or our boss, like what's velocity, what cycle time, which of our engineers are super, you know, like are really on the far edge of the curve in terms of efficiency.
How are our junior engineers ramping into the repo?
All that kind of stuff.
And that kind of analysis is actually really onerous and hard to get at because of the structure of the data and the nature of the analysis.
And so what I love about just LLMs in general and in particular using something like Cursor.
is you can get to really nuanced cohorting analysis on human behavior and human analytics as a manager in a way that I think has been really challenging to do before.
Yeah, I totally agree.
And like the beautiful thing is now with MCPs, with data accessibility, like I think of tools like Cursor as just my daily operating system.
If I have a question, it doesn't matter if it's technical or not.
I just go into Cursor and ask it.
and so it's like super super powerful that way okay so it's asking me a little bit about like what outputs do i want i do want to enrich csv um just it makes it easier i do want a static dashboard just for fun like i'm not really trying to create a brand new dashboard right now but my main goal here is just honestly honestly like fine natural cohorts right um and so it's gonna kind of try to do light moderate active power super user It's going to look at line suggested, so volume, sophistication, agent mode, model preference, acceptance rate, and breadth.
What features are they using?
I'll spit out, you know, a CSV dashboard, likely generate a Python script too that I can reuse.
So I'm just going to kick off build mode.
While that's cooking, I do want to just maybe bop over to like, it's going to create all this stuff in Python, create the scripts for me.
Awesome.
But we can look here at some of the...
the information right so like this is all sort of random made up data it's like sample data but what it did was in a previous run it looked at all the data generated the python script which is great super simple and it sort of just did some like high level status metrics like ai code percentage again on all this made up data ai lines per week composer lines this is when you're using the agent mode in cursor or tab lines right when you're hitting tab One of my team members actually got the cool cursor tab award, which is great.
And so it sort of breaks all this down.
And then what it really segmented around was like agent heavy users, which is folks who really lean into agent usage.
There's also tab heavy users.
This is like a different cohort.
They just lean into tab usage and they maybe want really just a bit more control and maybe haven't gotten yet used to like how to let go with an agent.
You have balance users that try both.
And then you have sort of like maybe cursor curious or maybe not cursor pilled or, you know, LLM pilled right now.
And so I generated this whole script.
It's great.
And now let me show you sort of a bit more analysis I want to do here.
So let's do this.
Run the analysis on, I have a sample user set and generate the HTML as well.
And let's We're actually like this is sort of the output of the analysis script that was generated in Python, which is already cooking in parallel.
Got it.
So what you've done here is you've taken some raw data from cursor.
You've asked one kind of agent to do a cohort based analysis and generate a enriched CSV essentially with some data.
And then you're kicking off another agent.
to actually do the analysis on that and generate sort of an HTML view of it so you can visualize the data.
That's right.
That's right.
What it did was the Python script that was generated, right?
It found these natural cohorts, these natural cohorts of super user, regular user, power user, light inactive.
Again, this is just honestly sample data, but based on like real information, real schema, real cursor.
data fields.
And it came up with like 70% are an agent heavy in the sample data, 20% are minimal, 4% are balanced.
We have some room to improve here on the sample, right?
Like not enough people are using it.
And so it does a bit of a breakdown, which I kind of like, you know, kind of a recap of metrics.
Yeah, we have a lot of lines of code in this data.
We have 520 power users.
Again, made up names, but like this person is crushing it.
I want to know what this meta person, Gabriel Diaz, is doing, right?
Awesome thing here.
It generated a little visual dashboard.
Nothing fancy, something just really simple to look at, right?
Total lines, composer lines, tap completion, a little bit of breakdown, some structuring on the tiers and usage, right?
But what I really kind of want to understand is like, what is...
Gabriel Diaz doing right this made-up user was just like crushing it yep how about based on the data generate guidance for each user cohort what you know they should do to advance and graduate to super user I'm looking for explicit guidance effectively like I want to turn this into some type of playbook right so let's let this cook and then in parallel what I also want to do is I like visuals and there's something intuitive here where like as we look at the data itself right we we know that the like the path to this super user over here it's it's not like you go inactive to light to regular to power to super we know it's not linear like that right right there may be like forks from light to straight to power user regular user seems to be like balanced on the tearing but what i want to know is like what are the special things these folks are doing and how do i sort of shift the curve right And so I'm also going to throw another question in parallel, like create a mermaid diagram for all the different sort of paths a user can take from light to power.
And I'm assuming it's not linear.
And let's just see what this cooks up to.
Okay, this is really working hard.
Really working hard.
Opus or five.
Yeah, Opus is really working hard on this.
But yeah, let's see where it goes.
Well, you know, it's really interesting.
I'll give you a shorter hack on this one.
So I think what this is generating is like an HTML playbook that you could share out that has things.
I will tell you what I would do in this use case, and I've done this a couple of times with customer QBRs, is I say write a Slack post that I can put in my engineering channel on a couple of these stats and how we can get people to move from A to B.
And it'll write me like a...
a short little Slack post.
So I love this idea of going from something like a CSV to a really deep analysis to an HTML-like visualization to like three bullet points I can send in Slack.
And as a manager, each one of those steps would have taken just forever to do.
And now you can get them all done in Cursor.
Yeah.
You know, that's like kind of the awesome thing is the power of something like a workflow markdown file is huge.
It's absolutely huge, and it's exactly like the thing you're describing here.
Meet Rovo, your AI teammate, connecting knowledge, people, and workflows so teams can work smarter and move faster.
It helps people find answers, make decisions, and automate work securely and with context through search, chat, agents, and studio.
Rovo runs on the Teamwork Graph, Atlassian's intelligent layer.
that unifies data across your first- and third-party apps so no knowledge gets left behind.
And you always get personalized AI insights from day one.
And the best news?
It's already built into Jira, Confluence, and Jira Service Management paid subscriptions, so the power of Rovo is already at your fingertips.
Know the feeling when AI turns from tool to teammate?
If you Rovo, you know.
Discover Rovo, AI that knows your business, powered by Atlassian.
Get started at rovo.com.
That's R-O-V as in victory, O.com.
Let's see.
Let's see what it came up with, right?
And like, you know, the thing is like, no one should expect all this information is going to be perfect.
Like if anyone is thinking, oh, wow, what is going to be my job as a leader if Cursor can do all of this?
I was like, well, your job as a leader is to lead.
Right.
And to make change and impact.
And this accelerates.
So inactive users, like, yeah, kind of true.
You have it installed.
You haven't really used AI features yet.
The hardest part is getting started.
So I kind of like this.
It gives like just some very simple prompts.
Try the agent mode for your next task.
Something very, very simple.
Something like, wait, try it.
Tab completion flow.
I kind of feel like.
The LLM really wanted to just turn this into a game, like a little quest or something.
Yeah, it's gamified a little bit.
Yeah, it is a bit gamified and it's kind of fun.
All right, so this is cool.
It's kind of given me like, this would be my Slack post TLDR.
16x more AI lines, super users versus other users.
Let me zoom in just a bit more.
More agent requests for super users.
I love this.
Stop typing, start shipping.
It's dark mode, so the engineers will just love it.
Yes, right.
It's kind of perfect.
And then you installed Cursor, but you haven't used AI yet.
We talked about this.
That's cool.
Lightmob.
Okay.
You know what?
This resonates.
Stop saying fix this bug.
Actually talk to it like you would maybe a junior engineer, right?
Cursor just did release BugBot.
I love BugBot.
It's awesome.
I love BugBot.
Agent isn't for hard stuff.
It's for everything.
These are like motivational quotes now.
But I think, like, we should just make posters for and put them up on the wall.
Write unit tests.
Actually read the comments.
Okay, cool.
Now, power users, you're good to be great, think bigger, and tab harder.
Tab harder.
If Cursor is listening, I think this is, like, going to be your new merch line, guys.
I need a hat that says tab harder.
Yes.
Okay, so just to recap again, we're doing free product work for Cursor here.
Your ultimate problem was like, how do I drive up adoption in these tools?
And you're like, of course, I'm going to use the tool to understand adoption and then figure out ways to drive adoption.
We did analysis.
We created a visualization of the data itself.
You identified cohorts and power users, which would have been very tedious to do if you were going to do manually.
And then you created a hosted playbook as well as a series of motivational statements, which we can either give to our friends at Cursor for free or trademark right now and make a little money.
Agent everything.
Tab without thinking.
Bugbot always on.
Iterate prompts.
Love it.
And this, you know, again.
What I think is fun, let me talk about what I think is fun about this.
One, everybody who has been in engineering leadership knows this is the kind of stuff you get asked to put in a board meeting.
You get asked by your boss, like, what percentage of our engineers are using cursor?
Do we have power users?
Are we actually getting value?
And we're talking about an AI use case right now.
But again, across management, there are actually measurable things you can do about the performance and efficiency of your team.
Yes.
I think it's been so impossible to get before.
Two, it would be no fun if you didn't get to do it with code, which you get to do with code.
Actually, that is the thing.
You can solve problems with just code now, right?
You can just do things.
You know, you're so right.
I think this, I underappreciated exactly what you're saying right now.
And I just want to repeat it because normally you would be asked this and then you would have to go pull an IC.
to do that and like what what yeah come on like no you can just do things right now and and again it's like not that i i think people under appreciate the velocity creation of a fun task yeah which is like at the end of the day like this is silly but also the like little fun bits of it you're like great i want to go to the next level because i got like a little dopamine hit from this dark mode playbook that's kind of funny and i think people underappreciate like that iteration speed that can just come with like a fast feedback loop yeah when you're building something and the fast feedback loop when you're building something that has high quality against it which like something designed like this does so much more fun to look at than a google doc yeah or a spreadsheet or a dashboard so we we did it we did it we again you and i are twin stars I think here and so we probably go all day on the things that we find fun but let's go to a second use case that I think people are going to see and let's see how fast we can do this use case which is you're talking about the speed of feedback to feature and you you said some fighting words out there you're like we're really compressing the time from feedback to feature so how does that actually work those were those were some fighting words um and you know I think You know this, right?
You want to build this for your users, right?
And you want to create the best damn product out there as fast as possible.
And the way to make that cycle work really well is genuinely how fast you can move on feedback.
Okay, but I want to start from how does feedback even normally come in, right?
So, you know...
Normal teams and culturally, you'll have dogfooding or bug bash sessions, right?
You'll get on a meet or get in a room, keep using the product, blah, blah, blah, all that jazz.
And then someone has to collect the bugs in a Google Doc and then take those bugs in a Google Doc and put them into a ticket system, right?
Okay, and then there's a whole discussion around...
Is this important?
Is this not important?
Okay, should we pick it up in this sprint?
Should we wait for another sprint?
And by that time, your user has turned out.
They're like, you guys didn't fix this.
I kind of hate it.
Moving on, right?
Everyone's attention is like so, so, so short.
And right now, like the whole team, we're all preparing for a big launch.
And we wanted to get together and do this thing called a surge.
And this is where we like just bring the team together.
And we do very, very long days using all this AI and just shipping like massive amounts of code.
And fun fact, like during these surges, we end up shipping like more than three to four X more PR volume in the same time.
But the other thing we wanted to do was bring people into the office and we set up this thing called like a feedback cafe.
And so we'd invite externals, internals, et cetera.
and we dog food with them and we'd show them the app and like here's just like a couple seconds of you know what it looks like we're just standing there collecting information doing all this like live dog fooding and the hard part though is especially in real life how do you actually capture that information because it's voice it's video how do you translate it into a system okay so i just spent like half a weekend and built a tool to capture feedback live let's just pick something i'm gonna pick i'm gonna i'm gonna pick a new thing how i ai testing with claire awesome so let's do that it's gonna create a little session perfect very simple and we have two modes you can like you can use this on your mobile phone that's what the team did when they were in real life but for this i'm just gonna like capture some audio And let's see, what's what's actually maybe I can just hear from you like a fun little bug or something of a product that you you think you want to fix.
So we're going to start capturing audio.
There is a chatbot that I use where my account, when switched to business account, forces me to clear all my chats.
And I think we should fix that bug so that I can access my existing chats.
We're going to start capturing audio.
Okay, cool.
We captured it.
It's basically taking the audio.
I did a system prompt, sent it to an LLM.
And then what we do is the prompt is basically saying go and identify the bugs.
And then I'll create it.
I'm going to do one while it's processing.
Right now I'm using the app.
I'm on the trade tab and I'm clicking the from field and I'm typing in numbers, but the numbers are not showing up.
So that's not letting me make a trade.
So I think in our first example, the audio is a little hard to capture.
But let's look at the second example.
It calls it out really clearly.
On trade tab, typing into from field does not display enter numbers.
User cannot initiate a trade.
Cool.
Really, really clean.
Yep.
I hit create linear ticket.
It even gives like a suggested title.
The user journey I care about for this is trade.
Boom.
I create the ticket itself.
Awesome.
I pop over.
The ticket is all here.
The file is there.
Linear is an incredible tool.
It's doing some triaging.
But the thing I want to now hop over to is we're going to just create the PR.
So we have this tool we built in-house.
We call it CloudBot.
It's actually like using all sorts of underlying models.
It's not something that is specific to Cloud.
So CloudBot create PR.
I know the repo for this is Wallet Mobile.
And here's the ticket.
Oh, that's not the ticket.
The ticket is boom here.
Great.
Cool.
So I just went from a bug report to a ticket.
To a PR.
To the PR is cooking.
Okay.
So I have to pause because if you are new to how I, you have not seen my signature move when I really love something, which is this.
And I was doing this because I was just thinking about.
This little micro app that you have on the left side, which is, you know, live user feedback, totally unstructured, right?
Video or audio.
Run a little baby LLM on it.
Get not only a summary of the issue, but a good recommendation on how you might fix it.
Very quick beep boop to Linear.
We love our friends at Linear.
I think it's a great platform for agents.
And then a little custom agent in your Slack that can read those linear tickets and just execute on them.
And again, so traumatized by the past, maybe, which is like this process would have been, you know, somebody manually summarizing what came out of a research session.
Some document being written.
Somebody actually making explicit decisions about what to include and not include.
The decision making is gone.
Yeah.
Like no filter anymore.
You don't get that like, well, you know, if I make this five pages long, no one's going to read it.
So I'm really going to focus on the top 10 things.
It's like, let's capture everything and then just burn through it.
And then I have to ask you, why did you all build your own little bot to do this?
What was the advantage of building the bot?
So this is like in-house and we built it.
You know, it all started.
Around middle of this year, I was just obsessing so much about AI.
And I was like, how do I create better tooling for the team, for the company, so everyone can be accelerated?
So I put a call out on Twitter.
I invented this role called Super Builder.
And the single most important job of a Super Builder is to create more Super Builders.
So we hired our first Super Builder.
We talked about some ideas.
And one of the biggest things, because most of our company uses Slack, we're all in Slack.
And Slack, you know, I'm a strong believer, it's just a bunch of humans pretending to be systems, right?
And the cost of writing something in Slack is zero, but the cost of answering something in Slack is enormous.
And most of it is noise, right?
And so one of the things was just like, how do we bring the workflows that we are all so used to?
And how do we like sort of capture that and then add AI on top of it?
So we had like various reasons.
We know like lots of companies have background agents, cursor, et cetera, et cetera.
We just have like different sort of security requirements right now that we just couldn't launch with it.
And that's fine.
So we built this in-house and we have these like feedback channels, right?
Hey, there's a bug here.
There's a bug here.
And so now all we just do is like CloudBot go and do something with that.
Or if someone is like, hey, we just got out of this meeting.
Here's a summarized transcript.
We're like, awesome.
At linear agent, go break this down into tickets.
And then just like, you know the look you showed, right?
Like everyone is just doing that emoji of like the head exploding, right?
Because then now we have like 20 tickets and then we do fun things like this, which is just go like bonkers where...
We just fire off tons and tons of calls, right?
And so we built this plan mode.
So this bot has a create PR, which it's cooking.
And also the cool thing about create PR is when it's done, it will respond back.
It will show you a link to the cursor branch using cursor's deep link.
And when then the one-off build is ready, it will show the QR code.
So you can just scan and start playing with the fix, right?
There's a plan mode, which is very much like cursor's plan mode.
It just comes up with like a plan.
And then we also have explain as well, where it's like, oh, I want to debug something.
Chintan's app not working right now.
Chintan.base.eth as an example, right?
And it has like all the skills, all the MCPs.
And so the thing I realized is context is the most important thing.
So the place where we capture all of our context is linear.
And then this agent that we built um we added skills and mcps so if we can capture context through linear then we can trigger the agent using all the context from linear and then it goes off into all the mcps like datadog sentry amplitude our internal snowflake databases etc and it has the ability to pull context from the rest of the company and it can work across multiple code bases and then boom like it's it's like this it's a it's it's a super builder This is awesome.
And so before we move on, I think what I want to call it here are a couple of things that I hope people didn't miss.
One is right now, if I can give people career advice, you want to be like the top three most AI-pilled people in your engineering organization.
I'm sorry.
I just have to say it.
Whenever I pulled an engineering leader aside or someone aside who's like maybe a little AI skeptical, and I said like, I want you.
to lead this.
I wasn't doing it.
Yes, of course, I want to do it because I think it has high impact on the company.
But I felt like I was doing people a career favor by giving them this role.
And so if you can find companies that are hiring super builders that will put you in the role of driving AI across an organization where you can learn these skills, I tell you, it is an incredible benefit to your overall career.
And I don't think people appreciate how much that is pretty still rare right now.
So if you can find it, I would just beeline directly to it.
I think the other thing, and we've seen this a couple of times, we saw this Amplitude actually did it.
Building your own agents is not impossible for organizations.
And so if you do have security compliance, data access restrictions, you can't use cloud agents, you can't use these things.
It is not impossible to build these things yourself.
And there are lots of like really great SDKs out there too that you can use.
um to do so and then you know three like i do think some of these platforms linear and slack are just friction reducers to access to ai and so if you are thinking about driving ai adoption in your organization like figure out how you can get the right platforms in place that can unlock access to agents because if you ask somebody to open or learn a new tool it's just going to create too much friction um to to move forward i think there's like one super important thing like this this is a channel where we call cloudbot playground and i'm scrolling through fast just to show you like how much people are using this was one night i was up at like 1 a.m just pushing this we got like 200 bucks right from this tool i showed you and i just kicked them all off in like one solid go just to get things cooking and like it was great uh let's see if a plan came out here yeah so like there's a there's a plan that comes it actually creates the plan in the linear ticket yep this the trick here why slack is because slack is how things go viral within your company totally if you have pulled out the magic into some separate tool that others can't see yep it doesn't happen and so by getting things into slack People just like, holy shit, this is possible.
Let's go.
And it's like, it's really cool.
I completely agree.
Okay, so we have just seen about everything I wanted to see from the engineering side.
But before we get out of here, I want you to spend just a couple minutes on a personal use case.
Okay, let's go.
I think the one that resonates probably for everyone is getting, if you have kids, getting the school emails.
That it's like, oh, here are 50 events that are about to land.
Here are the dates.
I've just started taking a picture of it and then throw it into chat.
You can say, create the calendar invites.
100%.
Right?
It's like, it's the dumbest thing, but oh my God.
And then the shared calendar dance happens.
And it's like, it's so great.
Another thing though, like I love food and wine.
I really do.
And like, I've done like sommelier training, et cetera, et cetera.
And I realized like, you know, I went to New York recently with one of my buddies.
And he's learning about AI, but he's like, what are some of the real use cases that would resonate with me?
And I was like, well, like one of the biggest sort of anxieties people have is when they go to a restaurant, they're handed the wine menu, right?
And they're like, what do I pick?
What if I pick the wrong thing?
So with my friend in New York, we went to some like champagne tasting.
And so like, I just took notes.
There's like this whole notebook, right?
I just did this like an hour ago.
And I was like, oh, here's a great producer.
Single star means like, Yeah, it's good.
And then here's another one.
Oh, see, I wrote amazing by like, this is someone I've actually never tried before, but I loved, loved their champagne.
It was just super yummy.
Here's another one.
Right.
Effectively, then I just like pop this right in.
And I said, here are a bunch of champagnes that I tasted.
Figure out from my notes, like, what are my taste preferences?
Really simple.
Because, you know, like when I did like Somali classes, the biggest thing that it teaches you is the vocabulary to describe the stuff you like.
Right.
And then so I just took the images.
It figured out the producers.
And this is actually like spot on.
The fun thing I did with my friend while I was in New York was like we were just he was he's he actually is the real life version of ChatGPT.
And it's it's what inspired me to do this, which is he's always trying to figure out my taste preferences.
And so, you know.
This is like my strongest signal.
I love like these wines that have very little sugar that are like really rip-roaring acidic.
I love some aging.
I love growers, right?
Grower champagne, not like the big houses that are like very sweet.
It even went into like a certain subcategory of like, you know, the chalky style, this specific producer that I wrote amazing buy for.
And it also called out something I learned in real life, which is like I do like Pinot Meunier, but only like with this sort of characteristic.
Right.
Kind of crazy.
All right.
Fine.
And so then it came up with like a little bit of like a champagne profile.
Cool.
And if I'm buying stuff, you know, here's here's what I would buy.
All of that's fine.
OK.
Like why on earth would anyone do this?
Right.
Like like people must be listening and be like, OK, maybe just drink a little less champagne, dude.
But like.
The fun thing is, let's say you took, you went to a restaurant, right?
And I just did this for this like example here.
And you just like dropped in, took a picture of the wine menu, right?
And it's like a big old menu.
Some of them are like size of a dictionary.
Some of them are simple, but like you don't want to make a choice, especially you just want to be with like talking to the company that's in front of you and not like staring at the wine Bible.
You drop it in and boom.
What it actually comes out with, and I think the prompt I asked is, what would I like from this list?
What are good values?
And it kind of just went through this really fast based on my preferences.
And it's right.
I would love this.
I have had it.
And it's great.
And it's fun.
It shares the price.
Absolute no-brainer.
Another example.
Another example.
And then it kind of gets into a bit more detail categorically.
Like, look, if you want to value one.
And just like want a bunch of bottles, go for this.
Like everyone's going to love it.
If you want something a bit like more splurgy, try these.
Right.
And very much like it kind of talks about what why you'll like it.
What I love the most always says this is the stuff just to stay away from.
Right.
And, you know, if it's a big night, then just go get these six bottles and call it a day.
And so, like, that's the fun thing here for me.
So what I have to call out for folks is we've actually seen.
not this particular use case, but this flow before, which is like, how do you reverse engineer your own taste?
So we saw Hillary at Whoop show how to reverse engineer her own taste on slides.
We saw, I forget, somebody else reverse engineered photographic styles.
Ravi, reverse engineered photographic styles and said, like, here's a photo.
Like, tell me, explain to me how to how to describe this.
But you are the first person that has reverse engineered their own taste in wines.
And I love this.
And now you can pick yummy stuff to get for it.
You know what?
Six bottle cart.
I'm going out with you next time.
I know.
We'll celebrate AI adoption or something like that.
This has been so great.
I have one, two lightning round questions for you.
We'll keep them very short and then we'll get you out of here.
My first one is, if you look back two years ago to now at work, how are you spending your time differently?
Like, how has all this changed how you personally spend your time?
My calendar's empty.
Like, almost empty.
We love it.
And the reason why is because the...
coordination overhead of like hey let's prioritize this let's change this let's change the roadmap no you just do things that's one two i'm writing way more code the team knows like uh if their contributions fall below mine like that's that's we gotta like help on the ai but like look like i'm also jumping and the team is doing incredibly hard work i am spending way more time in the code base fixing bugs trying things coming up with like technical approaches i am not a replacement for like the insane amount of talented, cracked engineers on my team, but I'm able to move things forward much faster and cut through the bullshit.
If AI has done anything for us, canceling meetings would be the gift that I want.
Okay, my last question is, when AI is not listening to you, when it gives you a really dumb playbook for your engineers, what is your prompting technique?
It depends on how many tries.
times i've tried to convince it but generally it's like okay one you're clearly not listening to me this is what i said two yeah i know i'm absolutely right but like stop being stupid i need your help and three i i like the nuclear option is i threaten it and i say um claude if i'm using like claude opus for 4.5 high like okay i'm gonna stop using you claude i'm gonna switch to gemini and then it gets a chip together I love it.
I don't know what that says about either parenting or management style, but I think it is effective.
Well, this has been great.
Where can we find you, your team, and how can we be helpful?
Yes.
So I'm on Twitter, at Chinthan Therakia.
We are building the base app.
It used to be known as Coinbase Wallet.
And I think by the time that when this episode airs, it will be live to the general public.
Use it.
It is a consumer social app that happens to use crypto and it's enabling creators to earn and be valued.
And we're excited to launch it.
And we think it's like a real big paradigm shift in crypto consumer apps.
So give us a feedback.
Give it a shot.
Post.
See the magic happen.
And we are hiring to cracked front end, back end design engineers, ML engineers.
Super builders.
I have two super builders.
Happy to bring in a third one.
But it is really, really fun to work here on this team.
And it'll be awesome.
So come join us.
Well, thanks for joining us.
Thank you.
This was such a great way to cap off the week.
Thanks so much for watching.
If you enjoyed the show, please like and subscribe here on YouTube.
Or even better, leave us a comment with your thoughts.
You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app.
Please consider leaving us a rating and review, which will help others find the show.
You can see all our episodes and learn more about the show at howiaipod.com.
See you next time.