# How to build an agent that builds the culture

Source: https://www.youtube.com/watch?v=ZZ19zhYnDKY

Machine-generated transcript; recognition errors remain. Source-recording timestamps. Boundary-crossing subtitle ends are clipped to this session.

[07:48:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28134s) second here.

[07:48:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28136s) Any 49ers fans?

[07:48:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28139s) >> Okay. You know, that's a better reaction

[07:49:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28140s) I've gotten to other events this year

[07:49:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28141s) when I've asked, you know, about their

[07:49:03](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28143s) local sports team because I've gotten a

[07:49:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28144s) lot of just like muted signs. I have to

[07:49:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28145s) hit the, you know, well, wrong audience

[07:49:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28147s) for that type of joke. But glad at least

[07:49:09](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28149s) it can hit this time.

[07:49:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28155s) Continue

[07:49:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28169s) help.

[07:49:46](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28186s) current slide.

[07:49:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28191s) That works.

[07:49:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28199s) >> Perfect.

[07:50:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28201s) >> All right. Good. Well, thanks so much

[07:50:03](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28203s) for waiting everyone. My name is Zach

[07:50:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28205s) and I'm an engineer at RAMP. I'm just

[07:50:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28207s) really excited to tell you all a bit

[07:50:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28208s) about how Ramp has evolved its

[07:50:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28210s) engineering culture this year through

[07:50:11](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28211s) the help of our robotic friend Inspect.

[07:50:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28214s) As a quick introduction, Inspect is

[07:50:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28216s) Ramp's collaborative coding agent. About

[07:50:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28218s) a year ago, we decided to take a bet on

[07:50:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28220s) building our own coding agent with every

[07:50:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28222s) session running and being fully

[07:50:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28224s) multiplayer. Inspect can work alongside

[07:50:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28226s) you and your team, whether that be an

[07:50:28](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28228s) Inspect itself, Slack, Linear, or any of

[07:50:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28231s) our of our integrations. And now it goes

[07:50:34](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28234s) far beyond just writing the code with

[07:50:36](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28236s) the built-in design primitives, review

[07:50:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28238s) agents, and verification flows that let

[07:50:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28240s) any builder go from prompt to shipping

[07:50:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28243s) all inside inspect. Inspect is also

[07:50:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28245s) connected with all of our integrations

[07:50:46](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28246s) companywide. So everyone's automatically

[07:50:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28248s) connected the to the data and tools that

[07:50:50](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28250s) matter most, whether that be telemetry,

[07:50:52](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28252s) databases, or any of the other tooling

[07:50:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28254s) available.

[07:50:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28257s) Through this, we now see around 75% of

[07:50:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28259s) all of RAMP's code uh being being

[07:51:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28262s) written and shipped by inspect.

[07:51:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28265s) When we started sharing Inspect publicly

[07:51:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28267s) at the start of the year, the technology

[07:51:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28268s) itself was the more novel part. Spinning

[07:51:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28270s) up sandboxes in under 5 seconds, wiring

[07:51:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28273s) up all that internal context, having

[07:51:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28275s) agents work together in a multiplayer

[07:51:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28276s) setting. People had a lot of questions

[07:51:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28278s) about the plumbing. But now with much

[07:51:21](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28281s) broader adoption of these concepts and

[07:51:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28282s) Inspect itself now being a product on

[07:51:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28284s) the market, the technology isn't nearly

[07:51:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28286s) the barrier that it once was. Instead, I

[07:51:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28289s) want to talk about the other angle, the

[07:51:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28291s) lessons we've learned around building a

[07:51:32](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28292s) culture around Inspect and what you can

[07:51:34](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28294s) take away to inspire the people and

[07:51:36](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28296s) teams that you work with.

[07:51:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28299s) Uh I'm not going to talk as much about

[07:51:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28300s) those technical aspects of Inspect

[07:51:42](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28302s) today, but if you are curious about

[07:51:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28303s) that, you can read our blog posts or

[07:51:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28305s) take a look at pragmatic engineers deep

[07:51:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28307s) dive that they did with us a few months

[07:51:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28308s) ago. You can also follow my boy Dylan

[07:51:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28311s) Garcia on Twitter. He's on his social

[07:51:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28313s) media grind, but he's also been posting

[07:51:55](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28315s) a ton of really great inspect insights

[07:51:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28317s) uh since we've launched it. So, shout

[07:51:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28319s) out Dylan. Please give him a follow.

[07:52:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28322s) One thing about working at RAMP is that

[07:52:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28324s) it really makes you start thinking about

[07:52:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28326s) everything through the lens of saving

[07:52:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28328s) time and money. And although I think it

[07:52:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28330s) is important to understand the systems

[07:52:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28332s) that you work with and understand how

[07:52:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28333s) your tooling works, if you're a multiund

[07:52:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28336s) or multi-,000 person organization and

[07:52:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28338s) everyone has to go through say 15

[07:52:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28340s) minutes of setup, once you start

[07:52:23](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28343s) multiplying that across an organization,

[07:52:25](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28345s) this is days lost for what is very w.

[07:52:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28349s) Then if you consider how fast the

[07:52:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28351s) frontier moves here on best practices

[07:52:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28353s) and new ways to set up an agent, you

[07:52:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28355s) realize this setup cost isn't just one

[07:52:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28358s) time. Not to mention these advancements

[07:52:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28360s) won't always spread equally. So now you

[07:52:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28363s) have an indeterminate amount of time and

[07:52:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28365s) effort spent on this maintenance without

[07:52:46](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28366s) an equal spread of knowledge leading to

[07:52:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28368s) a disparate outcomes across an

[07:52:50](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28370s) organization. While you can perceive

[07:52:52](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28372s) this as an advantage on individual

[07:52:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28374s) level, when you're trying to win, you

[07:52:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28376s) need everyone on your agame.

[07:52:58](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28378s) So this was our first lesson. Build

[07:53:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28381s) tools that kill information silos. When

[07:53:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28384s) we found patterns that worked well or

[07:53:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28386s) tools that benefited everyone, we could

[07:53:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28388s) push it to our entire organization

[07:53:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28390s) immediately. If you want to spend time

[07:53:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28392s) tweaking your own setup, that's fine.

[07:53:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28394s) But inspect is always available as a

[07:53:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28395s) very solid baseline. And what we found

[07:53:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28398s) is that we've never needed to mandate

[07:53:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28400s) usage of inspect because it existing as

[07:53:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28402s) this baseline reduced the need for

[07:53:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28404s) people to reach for their own setups all

[07:53:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28406s) the time.

[07:53:28](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28408s) Part of what I think makes this powerful

[07:53:30](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28410s) as well is that the reality of this

[07:53:32](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28412s) industry is that it's unlikely that you

[07:53:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28415s) as an individual always know the

[07:53:37](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28417s) absolute best way to work with agents

[07:53:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28419s) across everything. Even if keeping up

[07:53:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28421s) with this is your full-time job, we all

[07:53:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28423s) miss things, hold biases, and have blind

[07:53:46](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28426s) spots. So, part of the design of Inspect

[07:53:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28428s) is that there's just one single Inspect

[07:53:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28431s) for the whole company. When people

[07:53:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28433s) figure out better ways to use it or have

[07:53:55](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28435s) ideas for what would make it better for

[07:53:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28436s) the work they do, we're able to bring it

[07:53:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28439s) to the entire company. The best part of

[07:54:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28441s) this is that for most changes, this is

[07:54:03](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28443s) invisible to everyone else. You just

[07:54:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28445s) keep using Inspect as you normally would

[07:54:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28447s) and benefit from the improvements that

[07:54:09](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28449s) everyone's making over time.

[07:54:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28452s) And what we found is that we really

[07:54:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28454s) don't have to run these formal sitdown

[07:54:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28456s) here's how you use AI effectively

[07:54:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28458s) training sessions for Inspect. With

[07:54:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28460s) every inspect session being public

[07:54:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28462s) within the company by default, it's

[07:54:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28464s) actually easier to work in public than

[07:54:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28466s) in private. As such, you default to

[07:54:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28469s) working in public. And you can learn how

[07:54:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28471s) to use it by watching how your teammates

[07:54:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28473s) use it in the channels that you're

[07:54:34](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28474s) already in. And your teammates can learn

[07:54:37](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28477s) from you. You can literally ask inspect

[07:54:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28479s) to go through their recent sessions and

[07:54:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28481s) tell you about how they work, how they

[07:54:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28483s) structure prompts, or how they break

[07:54:44](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28484s) down gnarly problems.

[07:54:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28487s) I I think this has not just been helpful

[07:54:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28489s) for the builders at ramp, but also for

[07:54:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28491s) the inspect team itself. We frequently

[07:54:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28494s) see the way that people use inspect in

[07:54:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28496s) ways that we didn't originally imagine.

[07:54:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28499s) This then informs what we should build

[07:55:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28500s) towards, whether that should be more

[07:55:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28502s) native primitives for common patterns or

[07:55:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28505s) where tools and data are missing. All in

[07:55:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28507s) all, it creates this self-sustaining

[07:55:09](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28509s) loop where we're able to build towards

[07:55:11](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28511s) what makes Inspect the most successful

[07:55:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28513s) by seeing what people are already

[07:55:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28515s) achieving with Inspect.

[07:55:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28518s) This feeds into the second lesson that

[07:55:19](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28519s) we've learned. It's all about building

[07:55:21](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28521s) trust. I think it's fair to say that

[07:55:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28524s) adopting agentic driven coding has been

[07:55:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28526s) a massive trust building exercise for

[07:55:28](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28528s) every engineer this year. It's helped

[07:55:30](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28530s) that the models have become more

[07:55:32](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28532s) competent at writing high-quality code.

[07:55:34](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28534s) But there's a large part of this that's

[07:55:36](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28536s) just learning to trust what an agent

[07:55:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28538s) builds.

[07:55:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28539s) So much of building trust in tools comes

[07:55:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28541s) from learning from other people. After

[07:55:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28543s) all, that's why most of us are here,

[07:55:44](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28544s) right? You wanted to listen to people

[07:55:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28547s) you respect, or at least I hope you

[07:55:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28549s) respect, uh, teach you about the things

[07:55:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28551s) that they learned. But if we limit our

[07:55:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28553s) corpus of knowledge to just those who

[07:55:55](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28555s) find the perverse enjoyment in public

[07:55:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28557s) speaking, we're still not getting the

[07:55:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28559s) full picture. This democratization of

[07:56:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28562s) knowledge sharing is just fascinating to

[07:56:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28564s) me as a concept. Instead of grouping

[07:56:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28566s) around a select few leaders, can we

[07:56:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28568s) build systems that inherently share the

[07:56:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28570s) knowledge of everyone? This is what

[07:56:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28573s) Inspect has uh built towards.

[07:56:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28576s) Every time someone ships something with

[07:56:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28578s) Inspect, people can see it right there

[07:56:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28580s) on the work you've done. The session

[07:56:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28582s) itself is an easy to share. It's a

[07:56:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28584s) living artifact of how that change came

[07:56:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28586s) to be. When a poll request goes up,

[07:56:28](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28588s) anyone reviewing it doesn't just see the

[07:56:30](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28590s) 400line diff dropped over the wall and

[07:56:32](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28592s) hope for the best. They can see the

[07:56:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28595s) exact conversation that you had, all the

[07:56:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28598s) tools that Inspect used, before and

[07:56:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28600s) after screenshots, or even a video

[07:56:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28603s) recording of the verification agent

[07:56:44](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28604s) clicking through the app in the browser

[07:56:46](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28606s) to prove its work holds up. It makes it

[07:56:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28609s) effortless to show not just what

[07:56:50](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28610s) changed, but why you can trust it.

[07:56:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28614s) It also just makes it easier to bring

[07:56:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28616s) people you don't work with all the time

[07:56:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28617s) into the fold. A fun moment on this one.

[07:57:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28620s) It was back in February. One of our

[07:57:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28622s) engineers, Andrew, reported a bug in

[07:57:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28624s) Inspect. So, naturally, I reached for

[07:57:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28627s) Inspect and asked to investigate. What's

[07:57:09](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28629s) funny here is that although Inspect had

[07:57:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28632s) access to data dog for a while, we'd

[07:57:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28634s) only just finished instrumenting inspect

[07:57:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28635s) itself. I mean, inspect was primarily

[07:57:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28638s) built by front-end e- product engineers.

[07:57:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28640s) So, tracing is a little bit of a foreign

[07:57:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28642s) concept for us. But in any case, it was

[07:57:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28644s) a great time for us to put it to the

[07:57:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28646s) test for inspect. And inspect says

[07:57:30](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28650s) the instrumentation was causing the

[07:57:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28651s) error. Yes, the very instrumentation

[07:57:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28653s) that was letting us debug this error was

[07:57:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28655s) actually causing this error. So, Dylan

[07:57:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28658s) and I were not exactly convinced by the

[07:57:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28660s) robot here. And Andrew is just like,

[07:57:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28663s) whatever, I'll use cloud code. And and

[07:57:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28665s) while we don't have a mandate to use

[07:57:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28667s) inspect, I mean, personally, these were

[07:57:50](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28670s) not the words I wanted to hear.

[07:57:52](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28672s) So, nobody here is really trusting

[07:57:55](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28675s) anybody. Dylan and I don't trust the

[07:57:58](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28678s) robots explanation. Andrew doesn't trust

[07:58:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28680s) us to build something that works. And

[07:58:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28682s) inspect, well, I I I don't know if

[07:58:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28685s) Inspect trusts anyone, but that's okay.

[07:58:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28686s) That's okay. But because this is

[07:58:09](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28689s) happening together in public, we keep

[07:58:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28692s) proddding at it. Dylan asks inspect to

[07:58:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28694s) look through the code of the telemetry

[07:58:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28696s) library using and see if this was just

[07:58:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28698s) something that was happening before

[07:58:19](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28699s) without visibility because surely by now

[07:58:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28702s) coding has been solved and there can't

[07:58:23](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28703s) be bugs that we introduced and this time

[07:58:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28706s) it comes back with something a bit more

[07:58:27](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28707s) specific. The hotel library calls fetch

[07:58:30](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28710s) but it never reads or cancels the

[07:58:32](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28712s) response body. This was just a

[07:58:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28713s) cloudflare platform limitation at the

[07:58:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28715s) time albeit happening in a library

[07:58:37](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28717s) specifically made for cloudflare workers

[07:58:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28719s) but that happens. This library was

[07:58:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28721s) written pre-agi after all. At this

[07:58:44](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28724s) point, we ask inspect to make a patch.

[07:58:46](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28726s) It updates the exporter to explicitly

[07:58:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28728s) cancel the response body. We grumbled in

[07:58:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28731s) the thread a bit while it's deploying.

[07:58:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28733s) But we see after it deployed, there

[07:58:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28734s) haven't been any errors since. So great,

[07:58:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28737s) inspect fixed the bug, which at this

[07:58:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28739s) point it's nothing special in itself.

[07:59:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28741s) But there was a much more important

[07:59:03](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28743s) story playing out in this thread.

[07:59:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28746s) Before inspect, a report like this might

[07:59:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28748s) have been acknowledged. a ticket filed

[07:59:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28750s) and then one of us would have gone away

[07:59:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28752s) to debug it. Andrew might have received

[07:59:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28754s) a message later saying it was fixed, but

[07:59:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28756s) the interesting work would have been

[07:59:17](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28757s) done in private. Now though, it's easier

[07:59:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28760s) to do all of this in public.

[07:59:23](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28763s) And as such, Andrew naturally starts

[07:59:25](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28765s) becoming engaged, wanting to chime in

[07:59:27](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28767s) with his thoughts and experiences. And

[07:59:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28769s) then in that same thread, this leads to

[07:59:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28771s) ideas coming up about how Inspect could

[07:59:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28773s) power other work. And none of this

[07:59:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28775s) required any proddding or pressure to

[07:59:37](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28777s) work together. instead it was just like

[07:59:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28779s) oh these guys are doing something cool

[07:59:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28781s) and we could work on it together.

[07:59:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28785s) So in the span of an hour we go from a

[07:59:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28787s) skeptical user with a broken user

[07:59:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28789s) experience to an engaged colleague

[07:59:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28791s) wanting to build together and a more

[07:59:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28793s) stable inspect.

[07:59:55](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28795s) So once you have a tool that gives

[07:59:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28797s) everyone the best setup on day one with

[07:59:59](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28799s) no information silos and you've built a

[08:00:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28802s) system of trust that brings innovation

[08:00:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28804s) together, what happens next? This is the

[08:00:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28807s) last lesson I want to share. I think the

[08:00:09](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28809s) only thing left is to think bigger

[08:00:11](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28811s) together.

[08:00:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28813s) Something that's pained me this year uh

[08:00:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28815s) is how much reverence has been built for

[08:00:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28816s) the lone wolf operator. It's great that

[08:00:19](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28819s) we can all do more individually with the

[08:00:21](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28821s) help of AI, but this can't be the

[08:00:23](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28823s) endgame in my opinion. If we don't build

[08:00:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28826s) outwards, collaborate with other people,

[08:00:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28829s) and continue to share the progress and

[08:00:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28831s) learnings we make, I think this is all

[08:00:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28833s) going to collapse in on itself. We'll

[08:00:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28835s) only consider ourselves as our target

[08:00:37](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28837s) audience and we won't grow through the

[08:00:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28839s) consideration of others perspectives and

[08:00:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28841s) experiences.

[08:00:42](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28842s) This is not to say I'm all doom and

[08:00:44](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28844s) gloom about this. The fact we're all

[08:00:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28845s) here hopefully is a testament to the

[08:00:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28847s) value of connection. More importantly

[08:00:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28849s) though, I think we can shape our tools

[08:00:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28851s) to enable these connections to flourish

[08:00:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28853s) even stronger than before.

[08:00:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28856s) That story I told about Andrew has

[08:00:58](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28858s) played out so many times within ramp.

[08:01:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28860s) It's probably the most inspiring thing

[08:01:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28861s) about Inspect to me, honestly. Sure,

[08:01:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28864s) it's a coding agent, but remarkably,

[08:01:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28866s) it's become part of the culture.

[08:01:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28868s) Everyone at RAMP knows its face. We

[08:01:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28870s) dress it up on holidays. We throw in

[08:01:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28873s) Easter eggs over time. And we evolve it

[08:01:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28875s) as RMP itself has evolved. Not all

[08:01:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28878s) iterations have been perfect, as any

[08:01:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28880s) RAMP engineer could tell you. But I do

[08:01:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28882s) think every iteration has been together.

[08:01:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28886s) Going back to earlier this year, Inspect

[08:01:28](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28888s) didn't have nearly the amount of

[08:01:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28889s) functionality it has today. A great

[08:01:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28891s) example is its code review agent. Before

[08:01:34](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28894s) this, we were using various

[08:01:36](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28896s) off-the-shelf code review products,

[08:01:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28898s) frequently rotating between them to find

[08:01:39](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28899s) a good fit. At some point though, a

[08:01:42](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28902s) couple engineers, Daniel and Franel,

[08:01:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28903s) realized that we could probably build it

[08:01:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28905s) ourselves as Inspect already had

[08:01:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28908s) automation triggers that fired from a

[08:01:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28909s) variety of sources, including when a

[08:01:52](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28912s) pull request was opened. With just what

[08:01:54](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28914s) we built already, they got to work

[08:01:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28916s) building another beloved agent at RAMP,

[08:01:58](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28918s) review buddy. And what was so cool about

[08:02:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28920s) this is that much like Inspec's own

[08:02:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28922s) origins as a side project, these

[08:02:05](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28925s) engineers were working on this. They

[08:02:07](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28927s) didn't need to ask for permission to

[08:02:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28928s) build it. They just challenged

[08:02:10](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28930s) themselves to build something better,

[08:02:12](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28932s) used inspect to move faster, and quickly

[08:02:14](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28934s) built an agent that was better for all

[08:02:16](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28936s) of ramp.

[08:02:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28938s) This really did force us working on

[08:02:20](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28940s) Inspect to think about Inspect

[08:02:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28942s) differently. At that point in time, we

[08:02:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28944s) were pretty okay with Inspect quote

[08:02:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28946s) unquote just being a coding agent. But

[08:02:29](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28949s) once we saw what others were pushing it

[08:02:31](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28951s) to do, it got us thinking about how

[08:02:34](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28954s) Inspect could become full circle. If

[08:02:36](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28956s) this push didn't happen naturally, I

[08:02:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28958s) think it would have taken the Inspect

[08:02:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28960s) team a lot longer to get there.

[08:02:44](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28964s) This is what I mean about thinking

[08:02:45](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28965s) bigger together. Especially with the

[08:02:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28968s) continued improvements in model

[08:02:49](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28969s) performance, now is the time to push

[08:02:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28971s) yourself and the people around you to

[08:02:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28973s) think bigger. I encourage all of you to

[08:02:56](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28976s) take some time in this coming week to

[08:02:58](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28978s) ask everyone that you work with, what

[08:03:00](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28980s) have we been waiting to do that we

[08:03:02](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28982s) haven't done yet. And once you found

[08:03:04](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28984s) those things, try to build them

[08:03:06](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28986s) together. There's really not an excuse

[08:03:08](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28988s) to not just try anymore. You have access

[08:03:11](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28991s) to the same models as everyone else. But

[08:03:13](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28993s) you have to start somewhere. And I

[08:03:15](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28995s) believe that there is so much potential

[08:03:18](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28998s) in unlocking wins, not just for

[08:03:19](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=28999s) yourself, but for the people around you.

[08:03:22](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29002s) Inspect itself was born this way. not

[08:03:24](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29004s) only as something that I wanted to build

[08:03:26](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29006s) and Jason wanted to build, but out of a

[08:03:28](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29008s) want to build something for a team that

[08:03:30](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29010s) I truly love and truly respect that

[08:03:33](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29013s) would just make their jobs a little more

[08:03:35](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29015s) enjoyable.

[08:03:36](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29016s) Now, if you'd like to use a coding agent

[08:03:38](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29018s) that has embodied all these lessons that

[08:03:40](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29020s) we've learned, I'm happy to say that

[08:03:41](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29021s) Inspect is now available outside of

[08:03:43](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29023s) RAMP. If you go to inspect.com/ieie,

[08:03:47](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29027s) we'll prioritize you and your team on

[08:03:48](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29028s) the wait list. We're actually moving

[08:03:50](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29030s) through this weight list pretty quickly,

[08:03:51](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29031s) so expect to hear from us soon. But

[08:03:53](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29033s) otherwise, I hope you've enjoyed hearing

[08:03:55](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29035s) about our robotic friend, Inspect. If

[08:03:57](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29037s) these topics interest you, feel free to

[08:03:58](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29038s) reach out here or an X. But otherwise,

[08:04:01](https://www.youtube.com/watch?v=ZZ19zhYnDKY&t=29041s) thanks so much for listening.
