Successfully coding with AI in large enterprises: Centralized rules, workflows for tech debt, and training your team | Zach Davis (Director of Engineering at LaunchDarkly)

Vibe coding is not an acceptable enterprise development strategy. I love it. I can do 100 commits a week by myself on my side project, on my startup. But when you're working on a codebase and a platform like LaunchDarkly that powers trillions and trillions of experiences every day, you can't take the same strategies and tactics that a vibe coder could take.

One of the things that I realized is what's good for humans is also good for LLMs. And so I really started with how do we make sure that the repo is well set up for humans to know how to work in it. So we have frontend organization, we have accessibility, we have a JS style guide. So all is this very detailed documentation that we've put into the repo itself rather than have it in other places. And this way LLMs can access it, humans can access it, et cetera.

I think all the engineers out there are like crossing their fingers and hoping that there's one rules protocol to rule them all that shows up. And I think what you've shown is you can just create that yourself and then that makes it much more scalable. Welcome back to How I AI. I'm Claire Vo, product leader and AI obsessive here on a mission to help you build better with these new tools. Today we have a great episode for anybody trying to deploy AI agents in a real engineering team with a real codebase, not just vibe coding. We have Zach Davis, director of engineering at LaunchDarkly, who's going to show us How he sets up centralized rules and docs for all his AI agents, uses AI to burn down tech debt, and keep his hiring bar high. 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 codebase. 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 upmarket 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. Zach, I'm so excited to have you here because I feel like I maybe turned you. into an AI fiend at this point. Before the show, we were talking about how many tools you are now using. So before we dive in, can you just tell us a quick list, maybe not so quick list, of all the AI tools the technology team at LaunchDarkly are now using?

Yeah, absolutely. Let's see. So on the design side, uh, we're, again, we're exploring a bunch of things, so there's gonna be a bunch of tools. So. Lovable, v0, Figma Make. We're using on the product side, obviously we're using ChatPRD. And then on the engineering side for code, heavy Cursor users, heavy Devin users. We're also using now Cursor's background agent. I personally use Windsurf because I like Windsurf, but most of the rest of the org does not. We are using, we're trialing Augment. We are looking into Cloud Code. We're doing all the things. We're also looking into PR review. So we use Copilot for code review and we use Cursor for code review as well.

Okay. And I feel like 18 months ago we were using maybe a little GitHub Copilot, but not, not much. Yeah, not much more. And one of the things that I really liked that you and I did together, and you were, you were a champ in coming along this journey, is we really decided that in order for AI to be really effectively adopted by a team like LaunchDarkly's engineering organization, which is over 100 people, we really needed to put some concerted effort behind it and put a person in charge. And lucky you, you drew the either short or long straw, however that works. You know, what do you think about teams approaching this kind of engineering-wide transformation and what kind of organizational and cultural things you need to do to make it possible?

I do think having a person who's kind of, I don't know if in charge is the right word, but whose responsibility it is to drive that kind of change. And I think that having someone who's close to the code helps a lot because you don't really know what's working and what's not working unless you're in the code, at least on some basis. And so that can be a manager, that can be a director or someone, but it has to be someone who's actually trying these things, I think matters a lot. And yeah, I think you were looking for someone to take that role. And I was, I think, skeptical, right, of how well things were working really well for you over on your side job on ChatPRD. But when I tried to do the same things in our codebase, I was struggling. And so I really came at it from a standpoint of, I want to understand what works and what doesn't, and either be able to push back on you and say, hey, it's great over there, but on this larger codebase, it's not working, or be able to actually drive change. And now I'm at the, like, I'm on board, let's drive change. I think that matters a lot.

Yeah, and one of the things that I think is really important for our listeners, especially ones that are at growth stage or larger companies, is vibe coding is not an acceptable enterprise development strategy. Like, I love it, right? I can do 100 commits a week. By myself on my side project, on my startup. And, you know, I can recover from quality issues, you know, the maintainability of the code, the issue right now, that's not my big business issue. But when you're, you know, working on a codebase in a platform like LaunchDarkly that powers trillions and trillions of experiences every day, you can't take the same strategies and tactics that a Vibe coder could take And bring those into not just an individual developer's workflow, but an entire team's workflow. And so what have you kind of discovered as you try to figure out how to make these tools work for a larger team?

With smaller teams, you have more flexibility in terms of how you approach these things. With larger teams, you have more enablement and stuff like that. We're kind of in the messy middle, and it's, I found it more difficult to operationalize that, make everyone successful? And what I found was everyone was on their own journey to try to be successful with AI, and that just doesn't scale very well. So yeah, you really need to come up with a system in order to make everyone more successful. What I want is when those skeptical engineers jump in and they try Cursor, they try whatever for the first time, or they try it for the first time in a while, I want them to be successful so that they get that aha moment. And if you just leave them on their own, then, then you're not gonna get there.

Totally. And we had, I think you and I had mutually had the experience of developers having their first experience actually be negative, whether it was with Cursor or with Devin. It was like, see, I, I knew this was never gonna work and here's my first pass proof that it didn't work. And so. You really did a lot of— what I appreciate about you is you did a lot of technical work to make sure people were successful. We'll definitely talk a little bit more about some of the kind of culture and operations piece, but I actually want to get dive into what you did in the codebase to make it easier to work with Cursor and Devin. So can you walk us through some of those things that you did?

Yeah, absolutely. So in my IDE here, uh, you can see one of the things that I realized is what's good for humans is also good for LLMs. And so I really started with how do we make sure that the repo is well set up for humans to know how to work in it? And so we have this docs directory and I pulled a bunch of stuff from Confluence, from Google Docs, from other places in the repo, and I put it all in here, right? So we have frontend organization, we have accessibility, we have a JS style guide. So all is this very detailed documentation that we've put Into the repo itself rather than have it in other places. And this way, LLMs can access it, humans can access it, etc. In addition, we had these, we had cursor rules before, we had a CloudMD file, and I wanted to consolidate that. And so, uh, instead of a .cursor rules, I have this .agents rules. And the idea is to kind of centralize all of this knowledge in one place. And so you can see here, uh, I have something like TypeScript Essentials, which has a really kind of like quick, like the quick hits of what's really important. And then it also links off to like the comprehensive docs and says, hey, go, if you want to find out more, you know, go look at the JS style guide. And so then our cursor rules actually just point to that, right? So with our cursor rules say, hey, if you want TypeScript guidelines, go find this file in .agents. And then Uh, I talked about Augment earlier. We were trialing Augment. I set this up yesterday and I had, I asked the Augment, uh, agent to just create this. I pointed it at the cursor rules and I, uh, pointed it at our agent's rules and I said, can you just create this file? And so it, uh, it did the same thing. And this way we don't have to duplicate everything across multiple tools or tool files. And it's much easier to get stuff working. Well, by default. And the whole idea with this is, again, I want people to be successful, uh, out of the gate. Uh, and having this kind of centralized place, having all this documentation in the repo just makes it way easier for, for tools to be successful by default.

Yeah. One thing that I hear a lot is people are really frustrated with the tool-specific rules. They're like, why do I have a Claude.md? Why do I have a Cursor rules? Why do I have these GitHub rules? Especially if you're experimenting with the number of tools that you're trying, each tool has isolated their rule set in an individual file structure. And I think all the engineers out there are like crossing their fingers and hoping that there's like one rules protocol to rule them all that shows up. And I think what you've shown is you can just create that yourself, create a directory in your repo, put a consolidated set of rules. Make your sub-rules for each of those tools point to those rules. So say when you're looking, you know, when you're working on frontend, reference these rules, and then that makes it much more scalable. The other thing that I wanna call out for you is I think what you said at the beginning, you're using, I don't know, a dozen tools, probably like 3 to 5 IDEs across the engineering organization, probably within any individual engineer, You're testing like, I want Cursor today and Devin tomorrow. And if you don't have your rules set up for all those tools, then you're starting from scratch every time. And so I really like this idea of, of, of rules setup and then consolidation. I'm curious, do you feel like the rules have improved the quality of the outputs significantly?

Yeah. Yeah, absolutely. So here I'm looking at, at our feature flagging rules. And it's interesting because we are a feature flagging. We have a lot of feature flagging code in the codebase. And one thing we noticed was that some of the models, some of the tools would get confused about whether we were asking it to create feature flags on the like launch Darkly product or whether we were actually trying to get it to do stuff in the code. And so there's a bunch of stuff that I did to just be really specific about how to be successful when creating feature flags. I want you to return a link, that kind of stuff. And it really has, it has made a difference. Yesterday, literally, uh, one of our product managers was doing a task with Devin, uh, and was able to tell it to put a flag, put the feature behind a flag. And, uh, Devin went and used the MCP and, and hit the flag and, and everything worked.

So I have another question about rules because LaunchDarkly's giant monorepo. 10 years old or something like that. It's got a lot of code in it, frontend, backend, tests, all this stuff. What do you think if you had to give some advice to peer engineering leaders who are approaching the same problem, what are the must-have rules from your point of view in the code? You know, I saw like a lot of frontend stuff, but what, you know, what are the quick hits of what you think should belong in a kind of cursor rules or a rule set?

I would say the best tip is ask the agents. to get you started. And so Devin actually has a great wiki that for each repo that Devin works on, it creates a wiki and it has a ton of really good information in it. And so I actually started with Devin and I said, hey, this is what I'm trying to do. Can you create basically the human-readable docs for this? And so Devin did a pass and created a bunch of docs, suggested some structure. We went back and forth and I tweaked things, and then I took that output, And I went through it with kind of like a fine-tooth comb because I think it matters, right? It matters to get those details right. And then once I had the human-readable docs, I went to Cursor and I said, hey, can you take these docs and can you take your existing Cursor rules and can you turn those into a .agents file? And so it was a combination where you can kind of lean on the agents a little bit to help you get unstuck and get started, and then also use your knowledge of what's important in the repo. And the other thing is that I was looking at where are people getting stuck. I knew that people on the frontend would struggle with getting like testing, basically writing unit tests. It would write Jest tests and we use Vitest and stuff like that. And so putting in specific rules to make sure where people get stuck, We have rules to help the agents be more successful.

Would you mind pulling up Devin and actually giving an example of generating a rule? And I have an idea for you.

Sure.

Which is like rules around generating data visualizations since we've done so much and just, you know, see what it comes up with.

Yeah. Here's an example of both asking Devin Wiki a question and then also using Devin to create a rule. So we can say, to the Devin wiki, we can say, um, what are the libraries used for charting on the front end?

I'm curious while this is loading, how long did it take you to set up Devin's environment? It's something that, you know, everything's easier with a little Vibe Code and greenfield app, except for setting up Devin's environment. It's just as hard. I'm curious what your experience has been configuring Devin to work in a large repo.

Yeah, I would say to get up and running with Devin, I got started pretty quickly. And we have kind of, we have a separate flow for frontend and backend. We have a concept of sort of like frontend-only mode, which proxies against another backend. And so I was able to get Devin's machine up and running pretty quickly in just frontend-only mode. And then I was able to take on frontend tasks using Devin. One of our other engineering managers, actually came in and saved the day on the backend to get the full, like, running our whole end-to-end up and running with Devin. And that took him, I think, a little bit more time than it took me. But the nice thing is you can do that sort of incremental, you know, you do what works. You don't have to have Devin running your full app locally in order to get value out of it. And so it's just about kind of like doing it piece by piece. And again, If it's hard to get Devin up and running, it's probably hard for your human developers to get up and running. So there's always incentive to make those things better.

Yeah, I will give, just 'cause you said it, and you said, you know, Devin's environment doesn't have to be running for you to get value. My number one Devin prompting trick is don't run this locally, just gimme the code and I'll test it for you. So sometimes I bypass that process entirely. Okay, so you asked this question of Devin Wiki, what do libraries use for charting on the front end? And it gave answer Recharts. Um, some other things. And so what would you, one, is this information pretty accurate? And, and 2, what would you do with it?

Yes, it is accurate. We are using multiple libraries. And so that was one of the things I was curious about is, is we've brought in several libraries and, and we're kind of trying to figure out how to consolidate. And so it picked out that we're using Recharts, we're using VizX. Um, it lists Echarts as a secondary library. I don't know if that's strictly true, but generally this seems very correct. And so I like to use Devin Wiki to just sort of ask basic questions about the repo, make sure I understand what we're doing. But if I actually wanted to create a rule, so you can't take action from Devin Wiki. So I, what I want to do is I want to create a new document, a human-readable, you know, human-centered document in our docs/frontend about how to use charting libraries. And then I want to also add a rule to .agent/rules. So I'm just going to give this to Devin and I am going to see how it goes. So Devin's going to spin up a new session here.

And one thing I want to call out for folks listening on the prompt is you specifically said you wanted to create a Markdown document. Markdown is every engineering agent's favorite file type. So that's a good way just to give a little bit of structure to your code. It also tends to pretty print and, and be human readable and easy, easy to view in, in GitHub and all that stuff.

Yeah.

And so what you're doing here is just asking Devin to make those docs for you. And this is one of my favorite use cases of Devin. I think you know this. Um, it's my favorite Devin hack, which is I have a GitHub Action on every PR that writes docs for the PR and adds to a changelog programmatically with Devin. I found that it's a very good technical writer. You know, sometimes the code is okay, but the technical writing is, is very clear and very good.

Yeah, I think that's exactly right. The, the Devin wiki is very good. It knows a lot about your codebase. It has this very explicit way of learning and, and understanding your codebase. And so it is very good about kind of describing that back and, and as you said, doing it in a, in a solid technical writing way.

Yeah. And then one of the other things that I wanna call out for people that are maybe listening and not watching is We are chit-chatting because we're waiting for Devin to spin up a virtual machine. So for those that don't understand kind of how Devin works, it actually spins up a virtual environment that reflects a development environment. It's gonna open it up, it's gonna read your codebase, it's gonna do all this stuff. And so, you know, it takes a minute to actually boot into an environment a little different than running something like Cursor locally.

Yeah, that's exactly right. Where, where these other tools. are just using whatever you have locally. Devin is running its own machine, which has a lot of upside. Um, it can run a browser and, and see a browser. It can do a lot of things that don't come outta the box with these other tools. Uh, with the downside that it takes a little time depending on, on your repo, it, it takes a little bit of time to actually set that machine up and, and get it running.

But like you said before, if your machine is slow to cold boot for Devin, it's probably Slow to set up locally for an engineer. So again, aligned incentives on getting your repo to work well for both your agent coworkers as well as your human, your human colleagues.

That is, that is my favorite thing is all the things that have been hard for humans forever, and we have just kind of swallowed it and said, well, that's the way this works, become even more important, uh, today with, with these LLM tools. To solve and improve?

Well, I think it becomes more important to solve and improve. And then I also think it becomes easier to solve and improve them. If I said, you know, 2 or 3 or 4 years ago, Zach, go document everything in the repo, high-quality human-readable docs, you just go do it by yourself. It would take forever to generate high-quality docs that, you know, really reference our code and understand the nits and details and I think the fact that even you can spin up docs so quickly is so transformational to how you can, and I know we'll see this in a little bit, like burn down tech debt, make your engineers happier. And so I do think, you know, a lot of engineers have this skepticism that adoption of AI tools is really about moving faster, shoving more junk in the code, like just getting feature bloat. And I actually do think for mature engineering organizations, It is also an opportunity if you approach it correctly to take care of some of the things that you have just hated forever in either how you run your software, how your team operates, or the code itself. And so that's one of the advantages I think people underestimate in larger organizations because they blur the line in their mind of AI-assisted engineering with vibe coding, which is not what we're talking about right now.

No, not at all. Technical debt is my favorite use case for AI to supercharge like a medium-sized organization.

What we're seeing here is Devin's looking through your repository, accessing its knowledge. Actually, I'll take a pause here. Have you set up the knowledge in Devin explicitly, which is for folks that don't know, little snippets of rule. It's almost like Devin's rules in some ways, little snippets of knowledge and rules. Have you set those explicitly? Or have you simply accepted and approved the ones that Devin suggests?

Yeah, so as, as you mentioned, one of the things that I really liked about Devin, especially as we were, were first getting started, is it builds up this knowledge on its own in some ways. So as you're interacting with Devin, it will make suggestions for additions to its knowledge so that it gets sort of like quote unquote smarter every time. Um, where some of these other tools have memories, uh, because Devin's starting a fresh session every time across different users, it, it has this centralized knowledge, um, kind of like repository. And so it's been a mix. We've sort of let it build up over time and people, various people have accepted knowledge. I added some knowledge very early on. I will intentionally add stuff when I run into problems. But then again, when I moved all this documentation into the repo, And I was trying to centralize everything. Devin's knowledge now primarily points to that same .agents directory because I don't wanna have the duplication. I want it to work for all of the tools. I don't want just Devin to be, to be effective. I want all tools to be effective.

Got it. So you've really taken all your tools, whether locally hosted in the repo or cloud hosted like Devin, and just made this agents folder.

Yes.

The source of truth.

That is it. That is exactly right.

How I AI is now on Lenny's list with my personal selection of the best AI engineering courses on Maven. You can spend months thinking and playing with AI before really integrating it into your workflow or shipping an actual AI feature. If you wanna start building, then these hands-on Maven courses are for you. Learn directly from Aishwarya Naresh Raganti, MIT instructor and AI scientist at AWS, or Sandra Schulhof, who has authored research with OpenAI, Hugging Face, and Stanford. To pivot into an AI role or successfully lead your company's next AI initiative, visit maven.com/lenny to enroll now. Use code LENNYSLIST for $100 off. That's maven.com/lenny to get ahead in the AI era and start building.

So Devin has a plan now. One of the things I like about Devin is it, it gives us confidence now, like how, how confident is it in the task at hand? Uh, which is nice because sometimes it's not confident and, uh, you, it's, it's better not to proceed. This is, this is something that, as we mentioned, Devin should be really good at. And so I feel good about its ability to execute this, but it will give you sort of an overview. If I thought, if I read through this and I didn't like, like what it was doing, it's gonna run Prettier on the markdown files, which actually I think is a good idea. But if I didn't think that was a good idea, I could update its plan while it's deciding what to do next.

Yeah. The, the other thing that I enjoy about Devin is 9 times out of 10, its confidence gets higher as it goes. So it always starts like medium confidence, but I have to investigate. And then it's like high confidence, I know what to do. But occasionally it fails me deeply and I have bullied it so much that it like starts to progressively lose, lose confidence. And then it's like low confidence, I haven't been successful so far. So I find the confidence assessment pretty, pretty accurate.

Yeah. Okay, so now it is creating it. created multiple Markdown files. So it's created a charting-libraries.md file. And we can actually, if we want, we can jump over. So there's a shell. There's also the code. So I can actually go look at what it's creating while it's creating it. So charting libraries guideline, it's creating that in our .agent/rules/frontend. It looks like I think it also created one in docs. So this is the human readable version. Um, which I'm not gonna go through in detail, but looks, it has examples, it, uh, you know, has the different libraries. I like all of that. And then in the agent's rules, it's sort of a consolidated, you know, must, must use this when. I like seeing that. I would go through here and really make sure it's accurate in what we want. And then it's a little long, I think, you know, for, for me, I want to keep the The agent's rules pretty concise, so you're not including the context and, and just so it's not too much. And I would also wanna make sure that it links out to the full documentation is another trick that I like to do so that a tool can decide to pull in that additional context if it wants.

Well, one little trick that I learned from another How I AI guest is that if you notice, Cursor reads long files in chunks of 200 lines. And so his goal was to keep these files under 200 lines so that it's not chunking the content. And so I saw yours is just like a little bit over 200. So one of the things you might add to your rules for rules is try to keep your rules files under 200 lines, for example.

Yeah.

Now again, I don't, I don't know if that's actually helpful or true, but it is a tip somebody gave me, so I'm passing it along. With no personal context.

Yeah. No, I mean, that, that, that's actually, again, that's a good tip for humans, just like it's a good tip for LLMs.

Yeah.

And you, you said something that I think is really interesting, which is I actually, I have a README. I have a human README about the rules so that people understand how to create new rules, but I should actually probably have something geared towards LLMs so that when LLMs are adding new rules, they're doing a better job of it.

Yep. Okay, so I see this, it looks great. So it's created a human-readable docs, um, in your docs folder, a, um, rules for your LLMs. You're gonna review this, you're gonna do a PR and merge those docs into, to the repo, maybe take a look at them, edit them. And you've used, you know, Devin Wiki, Devin Agent, um, and then it's spun up this, this codebase to write, write those docs. And so I think this is a really great flow. I think people are gonna learn a lot from this. You know, one of the things you said earlier was that tech debt is your favorite use case for these AI tools. I love to hear it because this is how I try to pitch senior engineers and senior engineering leaders like you to really adopt these tools when they're really skeptical. Can you walk us through how you actually approach burning down tech debt using these tools, where it's made it easier maybe?

Yeah, absolutely. So here we are in Cursor and, uh, I'm gonna show you that same agents directory. There's, so I showed you agents rules before. We also have agents/migrations. And so this has a couple files in it. Um, it has a CSS module conversion file, which I created to, to help us, um, convert CSS files to, to modules, CSS modules. And then it also has, I just added this one the other day, which is the one that I would like to show. And so, uh, what it is, is basically it's a combination of instructions for agents and a checklist, basically like a task list of, of what to burn down. And so the problem that I was running into is that our frontend unit tests, when you run yarn test, it just, there's so much noise in the console that It's really distracting. There's some actual legitimate problems in there that are just kind of being warned about and ignored. And I wanted to pay that down, but it's, it's one of those things that is annoying, but it's not quite annoying enough for someone to own it. And also it's such a big problem. It's really hard for one person to just kind of like take that and pay that down.

And so, well, and, and I'll say, imagine as an engineer, you go to your product counterpart and you're like, hey, I just wanna spend like a week or two just making our test logs just a little less noisy. So my life's just a tiny bit easier. Like, it's such a hard pitch to make for work like this. It's super important and like the pitch can work on the right leader, but again, like this is the kind of thing that's hard to justify in a fast-moving org. Yeah.

So I'm actually, I think what I'm gonna do is I'm gonna ask, uh, I, I will talk, I will talk through kind of how this works. Mm-hmm. And in, in the background, I will have Cursor, uh, take the next stab. So, uh, I'm actually gonna say, so it has this context, it knows I'm in this file, and I'm just gonna say, can you take the next tier of tasks? I can see here there's a tier 1, tier 2, there's 3 files. I think that's reasonable. And, uh, fix them. And I'm just gonna say, click go and we're gonna see what happens.

Um, okay.

So in, in the meantime, What I did to actually produce this is I ran yarn test and I piped the output to a log file, which I'm not like a super techie tech person. And so I actually asked Cursor how to do that effectively. And then I had a log file and I gave that to Claude, to Claude Code. And I asked Claude to basically create this file. And so what it did is it went through all It, it actually had trouble with how big that file was, but it was smart about, uh, working around that. And so it found out that we have something like 1,200 extra lines in a, in a test run that we don't need to be there, that we don't really want there. And, and then it quantified this, or it sort of grouped this into different types of warnings. And then which files are, are the worst offenders. And so then once we had this file, I said, great, like, go, can you go fix like the worst of the, the tier 1 worst offenders? And so it actually went and has, has done that successfully. That's been merged in, reviewed and merged in. And then I can do stuff like this where I just say like, for any, the thing that I like about this is you can just give this to any agent now. I can Slack Devin and say, @Devin, can you pick up the next task in the frontend test noise cleanup? Uh, I can do it here in Cursor, uh, and watch it go. I could give it to Cursor background agent. It sort of like makes it easy to pick these things up as, as individual tasks, uh, and, and make progress on them.

What I like about this approach as well is it's very, there's a lot of parallels to how you would approach something like this with an engineering team of, of human partners, right? You're gonna take a problem, somebody's gonna go investigate it and identify priority tasks to do. You're going to put those tasks in some sort of task tracking system, and you and I both know all of our beloved task tracking and project management systems. And I am starting to see cursor markdown files become the new task tracking system. So I'm seeing this this trend of these check checkmarked files in cursor just being the source of truth for progress on initiatives. So you created basically a list of epics. And tasks here, if that's what we call it, and they're prioritized by how severe they are. And then what I like about how you're approaching this, instead of saying like rip through all 1,300 noisy lines, you're saying prioritize them, do them one by one. And then what I'm presuming you're doing is the work happens, whatever agent you decide to do the next task, closes it out. You review the PR, you make sure any changes work. You merge it, it gets marked off. The other thing I wanna call out is while you are probably running this yourself, you could probably also get more people on the team to be aware that this test exists and just say, hey, if you have a few minutes and you're able to review a next set of noisy tests, like tell Devin to pluck off one and do the, do the code review for me. And it's all set up and it's ready to go. So, you know, I think this multiplayer aspect is very important when how, how you approach, um, some of these tools when you're working in a larger team.

Yeah. I just today, I had a PR up to fix a few stray errors on this one file. And one of the people from the team that works primarily on that, I included them in the review and he said, hey, if there's any more stuff like this, feel free to kind of like throw it over the wall to us. You don't have to be the one that does all of this. He didn't know that I was just using, you know, Claude or whoever. And so now I can actually just point them at this file. I said, hey, you know, take a look at this file, and if there's any ones you want to pick off in your ownership area, then, then just go ahead. Uh, and, and you're exactly right, doing that, democratizing that. This is great for— again, I, I'm saying the same things, but it's great for bots. It's also great for humans. Humans can come in here and understand this and, and work against it.

Yeah. And if you're feeling like, you know, crafting your farm-to-table code and you want to pluck one of these off yourself and you want to fix it, you can approach it the same way, right? Just open the file, mark the thing as done, do the PR. And so I really do think it's important that folks think of kind of these tools as an extension of the team. And the more the tools can operate the way the team would operate, and the more the team can operate in the same way the tools, can operate, then, then we can kind of all collaborate together and be, be much more efficient. So I think this is a great, super great example. I'm not going to make all of us watch Cursor go through tests and lint errors because I have lost enough of my life to doing that. But I think it was a really, really great example of tech debt. And then just to ask the question, you know, what's the end payoff for frontend developers? Like the actual issues bubble up in your tests and, and these tests get less noisy?

Yeah, I, I think one is it's easier to find stuff when stuff is going wrong. Two is you, I think it said that the biggest problem was actually accessibility warnings. So that's, that's like a real problem that, that exists. But when there's 1,200 lines of, of that, and a lot of that's coming from like the same component, if it's tested a bunch of times, will will spam the logs. And, but being able to sort of surface the actual signal through the noise, I think is, is one of the key benefits.

Okay. And then for our last workflow, I know that, Zach, you're gonna impress everybody and everybody's gonna think you are just an AI-enabled, you know, cutting-edge engineering leader who only works with his army of bot friends, but You're actually hiring at LaunchDarkly. We expand the team. Um, you're always bringing in great talent and you've actually used AI, um, to solve another problem, which is making sure that you're doing a great job hiring. So do you mind spending a couple minutes on what that little workflow looks like?

Yeah, absolutely. So I am, you know me, I'm, I'm a, I'm a little bit of a conflict avoidant person. I don't love giving people tough feedback. You know, it's something I've, I've grown to do over my career. but especially when it's someone I don't have a strong relationship with, it's not a direct report. I don't love just dropping in and being like, hey, this isn't great. But we were trying to improve, make our hiring more consistent. And I created a rubric for all of the panels that we have. So there was really clear guidelines about how to score a candidate. But the other piece of it was we needed people to follow those guidelines, and I wanted to be able to give people feedback about whether basically I wanted to raise the bar of the actual scorecards that we were creating. So I created this custom GPT, I gave it the rubrics, and I gave it examples of good scorecards, bad scorecards, and gave it as much kind of like, you helped me write the prompt, so thank you very much for that. And so what I'm going to do is I'm actually just going to paste in a scorecard. And so this is, you know, a scorecard that we got, and I'm gonna click, click go, and it's going to do a few things. One, the rating that it's giving me is, is the rating of the scorecard itself. So it's a little meta, but I wanna know it basically. I, one of the things I did in the prompt is I said, give it a rating. Is it excellent, good, fair, or poor in terms of scorecard? And then I want you to list out strengths, And potential improvements. And so, and then the last thing that I had it do, which I also think you helped me with, so thank you very much, is what I, the format I wanted to give this to people in was to send it to them over Slack, right? Like, hey, like, thanks for doing this. But also I had a little bit of feedback. And so it actually, it gives me the detailed feedback, but then it also crafts a short Slack message that I can If I want, just copy and paste and send to the person who created the scorecard.

I love this because so many managers and hiring managers can empathize with this because if you're running an interview panel, you're having everyone from your boss to your direct reports to people you've never really worked with directly interview candidates, right? Because you have these cross-functional interviews. And while you can have all the rubrics in the world, Interviewers sometimes write terrible notes and, you know, say, you know, assess the wrong things or don't give you the right details or really using the rubric incorrectly. And you're not sitting in every single one of those interviews to give live coaching. And so this is a really nice way to make sure that you're holding the kind of standards very high and then giving you some leverage as a manager to give your team coaching. And then as they get this coaching, they get better at doing The interview feedback, and then you can be more confident in your hiring decisions.

Yeah, and honestly, this helped me. In order to test this out, I was doing a bunch of interviewing and I was writing scorecards and I would paste it in and see what kind of feedback it gave me. And it was giving me very good feedback. And I learned very quickly the kinds of things, be more specific, avoid certain kinds of things. And so it actually made me write better scorecards just through trying to create this tool for other people.

Okay, Zach, you have given a masterclass in how engineering leaders at larger companies can really approach integrating AI into not just their individual workflows, but their team workflows. So just to cover what we talked about, one, let the team experiment. Like every tool, just let's see what works. So you seem pretty kind of generous with your experimentation mindset around what tools can use, can bring value to the team. I think 2, context is king. And so you are loading up your actual repository with docs and rules. 3, those rules are centralized, so you don't use agent or tool-specific rules. You create a central agent repo and then point all your specific tools toward that. You use your AI tools to actually create those rules. You, um, use, uh, Cursor and other tools to create plans to burn down tech debt and then have those AI tools burn down that tech debt. And then, since you have all this free time now, you're coaching yourself and your team to be better interviewers and better hirers. So, just that, no big deal. That's all you have to do.

A few things, yeah.

And this is all, I mean, truly from a personal professional development perspective, these skills were developed, what, in the last 12 months, right?

Oh, I think January is when I really started, like, took on the mantle and playing with Devin and really going down this path full heartedly.

So, 6 months and we didn't give you, I mean, We, I think we offered, but like formal L&D, none of that. We just pushed you into it and said, and said, go. Yeah. Okay. I'm going to wrap with 2 quick lightning round questions and I'll get you back to all your AI-assisted code. Question number 1, you listed so many AI tools. Which one is your favorite or which one has been most transformational?

Ooh, that's really hard. I would say Windsurf, actually everyone was. Hot on Cursor and I, it just wasn't the UX at the time was not clicking for me. And I saw a video for Windsurf and I was just like, whatever, I'll give it a try. And I had the free trial and within an hour I think I was paying for it because I just, it really clicked for me and the agent workflow just really quick clicked and I was hooked.

Amazing. And then when AI is not listening to you, you're such a, you're conflict avoidant. So I'm actually very interested in your answer here. AI's not listening to you. Um, you need to give it harsh feedback. What are your tactics? I know you don't yell. I know you're very polite, but what do you do?

I mean, some, sometimes I lose it, but I have to, I, I, the thing that I actually do is sometimes I just feel like it's not the right task, right? So it depends if I, if I think it's something that AI should be good at, then I, I, I get a little snippy with it. Maybe I don't yell, but I'm definitely getting a little annoyed. But I also think that sometimes it's okay, right? Sometimes it's not going to work and you don't have to keep banging your head against it. And I think developing that sense of where it works and where it doesn't has been really powerful for me. And also sometimes I just like getting in there and getting dirty, getting my hands in the code. And so, yeah, I think my technique is actually Either I do it myself or I go back and try and fix it. You know, am I providing the right context? You know, what, what, what is missing that it can't accomplish this effectively?

Yeah, you're, you're a very good manager, so I think it's from those skills. All right, Zach, this has been super informative. Where can we find you, and is there anything we can do to be helpful?

I'm on LinkedIn. Um, we are hiring at LaunchDarkly, and also if If you are a Launch Circle user and you have any feedback, I love user feedback, so please send it, send it my way.

Amazing. Well, thank you so much, Zach.

Thank you.

Thanks so much for watching. If you enjoyed this 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.