How I AI - I gave Claude Code our entire codebase. Our customers noticed. | Al Chen (Galileo)

Episode Date: April 6, 2026

Al Chen is a field engineer at Galileo, an observability platform for AI applications, where he works on the front lines with enterprise customers asking highly technical questions. Despite never having held an engineering role, Al has built a system using Claude Code to query Galileo’s 15 separate repositories, combine that with Confluence documentation and customer-specific quirks, and deliver hyper-personalized answers that would otherwise require constant engineering support.What you’ll learn:How to use Claude Code to query multiple repositories simultaneously for customer supportWhy code is often a better source of truth than documentationHow to combine repository context with Confluence and Slack using MCPsThe “customer quirks” system that creates hyper-personalized deployment guidesHow to build virtuous loops that turn single customer questions into scalable knowledgeWhy information organization matters less in the AI eraA simple 16-line script (written by Claude Code) that pulls the latest main branch across all your repositories to keep your context currentHow to reduce engineering interruptions to near-zero by empowering customer-facing teams to query the codebase directly—Brought to you by:Orkes—The enterprise platform for reliable applications and agentic workflowsTines—Start building intelligent workflows today—In this episode, we cover:(00:00) Introduction to Al Chen(02:50) The problem: documentation wasn’t enough(04:23) Pulling 15 repos into VS Code(06:03) How Claude Code queries the entire codebase(08:00) Why current code beats documentation(08:31) The pull script that keeps everything updated(09:54) Opening projects at the multi-repo level(11:40) Live demo: answering deployment questions(13:25) The customer quirks system(15:00) Living in chaos: why organization matters less now(17:03) Competing on customer experience, not just product(18:20) Should customers be able to query the code directly?(20:05) Where humans still add value(25:46) Using AI for reactive Slack support(29:16) The “and then” workflow discovery(32:07) Scaling processes across the team(34:07) Lightning round and final thoughts—Tools referenced:• Claude Code: https://claude.ai/code• VS Code: https://code.visualstudio.com/• Pylon: https://usepylon.com/• Confluence: https://www.atlassian.com/software/confluence—Other references:• Slack: https://slack.com/• Kubernetes: https://kubernetes.io/• Stack Overflow: https://stackoverflow.com/• Intercom: https://www.intercom.com/—Where to find Al Chen:LinkedIn: https://www.linkedin.com/in/thealchen/Company: https://www.rungalileo.io—Where to find Claire Vo:ChatPRD: https://www.chatprd.ai/Website: https://clairevo.com/LinkedIn: https://www.linkedin.com/in/clairevo/X: https://x.com/clairevo—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [e-mail].

The minute I realized I couldn't really do my job was when I was trying to reference our public documentation and trying to provide an answer. It just still wasn't coming up with an answer that my customers were looking for. They don't want the docs answer. They want the step-by-step answer of how all these services cascade together. What I realize is that I can actually pull all of these repos into my VS code and I can now use ClaudeCode to ask our entire code-based questions. Did you just say ClaudeCode, write me a script that pulls all these? Yeah, yeah, I'm opening up the script right now. It's like, what, 16 lines.

Didn't have to write this. I just said, help me figure out a way to pull the latest main branches into my local repos. The reality is we can now all live in a little bit more chaos because the AI navigates all that information for us across systems, right? So you can be in your code, querying confluence, we'll find the information. You have to be less precious about where and how you store the information. Throw into Confluence, throw it into Notion, throw it into Slack, whatever. That ends up being context you can provide to Claude when you are trying to ask it a question about a customer or about your code days. Let's give Claude code a little spiff every time it answers a question correctly.

You've got to split your quota with Claude code. Yeah, it gives you better answers, the more bucks you gave it or something. Coin operated Claude, that's going to be my new skill. Welcome back to How IAI. I'm Clarevow, product leader and AI obsessive, here on a mission to help you build better with these new tools. Today we have an episode all about harnessing your code to make your customers experience way better. Al Chen, who's on the field engineering team at Galileo, shows us how he uses their 15 repositories and cloud code to answer every nuanced customer question that comes across his desk and use that

to make the entire customer base and his entire team a lot happier. Let's get to it. This episode is brought to you by Orcus, the company behind Open Source Conductor, which powers complex workflows and process orchestration for modern enterprise apps in agentic workflows. Legacy business process automation tools are breaking down. Siloed low-code platforms, outdated process management systems, and disconnected API management tools weren't built for today's AI-powered world. Orcus changes that. With Orcus Conductor, you get a modern orchestration layer that scales with high reliability and brings humans, AI, and systems together in real time. It's not just about tasks. It's about

orchestrating everything. APIs, microservices, data pipelines, human in the loop actions, and even autonomous agents. So build, test, and debug complex workflows with ease, all while maintaining enterprise-grade security, compliance, and observability. Orcus, orchestrate the future of work. Learn more and start building at orcus.io. Al, thanks for joining How IAI. I am really excited about this episode because we've seen a lot about using your code as documentation. You know, we've heard engineers saying, you know, docs and code should be in the repo, product managers saying code can now be my documentation for internally facing assets or as I help draft PRDs, but you're going to show us how you can use code as an asset to create customer-facing things

and solve customer-facing problems. So tell me, what, what, what problem? were you facing when you decided I'm just going to clone the repo and fire up quad code and solve some of these problems myself? Sure. So working at Galileo on the field engineering team, I'm on the front lines in terms of working with our enterprise customers who are typically developers themselves and asking very in-depth technical questions. And the minute I realized I couldn't really do my job was when I was trying to reference

our public documentation and trying to provide an answer. to my customers, even by even using cloud code or cache gbt or whatever and trying to take all these different help docs and trying to call the answer, it just still wasn't coming up with the answer that my customers were looking for. And I just, background, I'm not an engineer. I've never held an engineering role, but I think I know enough to just be dangerous. And I realized that our product, Galileo's product, we're an observability to, tool for AI applications. If you look at this image here, I'm showing an architecture diagram, high level of all the different services that make up our platform. This is all like back-end

images that you have to, that customers have to deploy onto their Kubernetes cluster. And I realize that all these different services like UI, API, AuthZ comment, they are all individual repos within our Galileo repo. We're not a Mona repo. We're not a Mona We have multiple different repos. And so what I realize is that I can actually pull all of these repos into my VS code. Initially, it's more for me to like, I want to understand like how our code works and how our code is structured. But then when I threw it all into VS code, which looks like here, you notice along the left hand side, I'm open VS code now. And most of these of directories correspond to one of those services within our architecture.

So one repo corresponds to one service. And by having all of these repos in my VS code, I can now use CloudCode to ask our entire code base questions that are not answerable by our public documentation. And so sometimes I'll get really into questions about, well, how does this feature actually work? And so I'll ask CloudCode, look into the API repo, look into the AutZ repo, and help me come up with an answer. If you can't find the answer, reference other repos within my directory, my root directory, and help me figure out the answer. And so that's the key

unlock was when I figured out, I could get way more in depth, way more technical, and at the same time, myself, I can learn how our code base works. And how this has really helped me is I don't have to constantly ping our team engineering channel with, hey, what's the answer to this question? The customer just ping me about this. And you can imagine, engineers being really frustrated when I'm trying to, you know, post these questions and then the customer asks me a follow-up, but then I'm posting a follow-up in the Slack thread. So I'm sure many of you who are working on the front lines of customers understand how that feels. But I've basically reduced all of that almost down to zero by pulling all these repos

into my local VES code. I'm really empathetic to this problem because I, you know, I used to work at Launch Darkly, leading product and engineering, very technical product. We too had an architecture diagram. that looked very similar to that. And again, as a more of a, you know, people think that CPO's, chief product officers or CTOs are internal facing. No, no, no, we're salespeople. We're always salespeople. You trot us out and you put us in front of the customer or you put us in front of the prospect to answer the technical questions. And we had a diagram like that and I would constantly get these very detailed questions that required very detailed answers. Like,

how does your cashing work? And, you know, when you have seven layers of caching in your app, you can give the high-level docs answer, but when you're sitting with, you know, an architect in the room or somebody highly technical, they don't want the docs answer. They want the step-by-step answer of how all these services cascade together to build a resilient caching mechanism, for example. And I just think how powerful is it to be in a meeting or in an email back and forth and not just sort of give this high level, but be able to quiz. query the current code base and really understand at a detailed level how it works. And I think current is very important because, you know, and I know, this is always evolving over time. So even if

you got the answer right, you know, a month ago, maybe your team shipped an update or maybe, you know, that method is actually out of date or the docs are a little bit out of date. And so I do think because the code base is, you know, at least your main branch is always the source of truth, it becomes a really reliable, you know, a context set for you to answer questions about how the product operates. Yeah, and to quickly address your comment about how your code is obviously always evolving. I mean, we're pushing out, you know, multiple features per day, multiple releases. And one thing I've done, wrote this with cloud code is I have this script at my root directory that says, like, I just do something called pull all. And I'm not sure if this is how other people do it,

but it just pulls the main branch into my repo for all the repos in my root directory. So if I do this every day, I kind of get the latest code across like all these directories on the left-hand side of my VS code. So the alternative, which I was doing before for like a few weeks, now I realize this is just as a sign that I'm doing this is doing GitPull, Orange, and Main on every single directory. And it was just like not scalable because there's now like 15 different repos. I have to pull the latest from. So that's kind of how I solved the code base as always evolving problem to make sure that I'm always getting the most up-to-date information for my customers. And I have to ask, did you just say Claude code, write me a script that get pulls all these?

Oh, yeah, yeah, yeah. I have no idea. This is the, I'm opening up the script right now in my VS code. And it's like, what, 16 lines. I didn't have to write this. I just said to help me figure out a way to pull the latest main branches. to my local repos and it just didn't like one shot. Yeah, the other thing I want to call out for folks as I'm looking at your screen is I don't

think people use this trick enough, which is in VS code, in cursor, and whatever your IDE is, loading a project at the multi-repo level as opposed to at the individual repo level, if you're trying to answer questions across the product is really important. So, you know, there's some like context, bloat stuff. that can come into sort of querying across all those repos and all those files. But it would be very painful if you had to go into each of these repos one by one and like query and then go into the other one and query. And so I like this idea of opening them all jointly in your IDE so that when you're querying it with Claudecode or you're clearing it, you know, with something like cursor, it can have, it can go across, you traverse across repos and really give you. highly contextualized answers.

Yeah, our code basis happens to be in multiple repos, but I just pulled them all into this giant Galileo directory here. And so everything is like at the same parent. But yeah, if you're in a mono repo, could be, yeah, actually I don't know how this will work with a mono repo because I've never done it with Mono repo with CloudCode, but at least for us, like Galileo, this is how it works. Well, I have many mono repos. And yeah, you just open it at the right.

I would say my advice to folks is, open Claude Code or open, you know, your IDE at the right level. And sometimes it's narrow and sometimes you need to go up a directory. And I think really thinking about that, and you can even do that contextualized to the problem you're trying to solve, right? And doing that, I think, is really helpful. Can you show us just using Claude Code what kind of question you could answer with this code context?

I will give you an example of, I guess, I'm a big believer in using shortcuts too. So I use a bunch of custom code code custom commands to help me do stuff. So one thing I do a lot is helping my customers deploy Galileo into their VPC. So I have a custom command called DPL, which is it actually references our, the first thing it does is it looks at our confluence because we have a whole bunch of confidence pages about how to deploy into Kubernetes using our different images and stuff like that. So I'll say DPL, my customer cannot use CRDs, and they are using Google Secrets Manager and want to deploy the wizard image. Give me a step-by-step process on how to do it.

This is actually not a super representative query because they're way more detailed than this, and I provide a lot more context. But I want cloud code to focus on looking at Confluence first, because I know that we have a whole bunch of deployment stuff there. And then from there, if they can't find the answer, it will go off into all the different repos along the left-hand side of my class code, VS code, to find the answer. So right now it's just using the last C&MCP to pull information from Confluence,

and then marries that with our code base to answer a very, kind of in-depth deployment question. The one thing, I'm not sure if we should talk about this now, but I started doing this in Confluence where we have a, we call it a customer corks page. These are all kinds of, all of our enterprise customers, you typically have air-gapped environments, so they have all these security measures,

and we have to abide by them when we deploy the product into their environment. And so I literally have a page that looks like this where I have the customer's name at the top level and then a bunch of bullet points with like, you know, here are some things about how they store their secrets. Here's how they do namespaces.

You know, here's how they handle side cars and service to service encryption. Things I have no, I know nothing about, but as I'm meeting with my customers, I'm putting this all into this one confidence place, is ever-growing confidence page.

And then this is actually one of the core pages that goes into this D.P. custom command, which is look at the customer quirks page. If I'm mentioning a customer that's on that page, look at all their quirks. And then in the response from Cloud, it's highly customized, highly tailored to their environment because I've seen from working with our DevOps team that we can provide a generic answer about Kubernetes or about Clickhouse or about whatever for the customer. But it's like something you can just find online by Googling or using AI.

But when it's tailored to specific security requirements and deployment requirements, it's way more effective. And this gives the customer more trust that we know what we're doing, essentially. What I love about what you showed here, which is, you know, kind of combining the repository with the Confluence MCP and then both like team generated general documentation as well as you generated like micro documentation at the customer level is I've heard. so often in my 20 years in enterprise SaaS, like, what is the source of truth for this information? Like, I'm sure you've heard this too. Like, what's the source of truth for how XYZ works? Or what's the source of truth for this customer? And people have spent so much time like, you know, pruning these confluence gardens and organizing their Slack channels and trying to get people to, you know, get naming conventions, right? And like, the reality is we can now all live in a little bit more

chaos because the AI navigates all that information for. for us across systems, right? So you can be in your code, querying confluence. It will find, you can kind of point it in the right direction, it will find the information. You have to be less precious about where and how you store the information, bullet point list of quirks, you know, like really official docs, whatever, it doesn't matter. Because AI is just so much more effective at traversing all that information and pulling it in and making it actionable for you. And I don't think that's anything like any human was really proud that they were good They're like, I'm really good at finding like the right confluence doc.

That was never, never the value add. Yeah, yeah. I mean, I think even if it's as simple as, hey, you came across a really great answer in Slack, like in a really engaging Slack thread, throw that into a confluence page or save that Slack thread because I also use the Slack MCP to be able to summarize threads. So if you have like just some random, like this ongoing stream of cautious system of documents, you want to have cloud code. scan. I would just say throw it into Confluence, throw into Notion, throw it into Slack, whatever. And then that ends up being context you can provide to Claude when you are trying to ask get a question about a customer or about your codebase. Well, and the other thing, and this is maybe going back to how I introduced this episode, which is people use AI so much to compete on the field of the product and

engineering velocity. And what I mean by that is like, we're all using Claude Code to ship more product. We're all using AI and codecs to build, you know, better user experiences or more resilient backends or any of that stuff. But there's also a completely different competitive field, which is how you show up in your relationships with your customers. And I think, you know, what you're showing is you can actually use AI to invest and compete on customer experience. And, you know, my hypothesis is when your very complex enterprise customers have you

show up and you don't just say like here are our general docs to deploy this and instead you say I heard you. I understand what your needs are and here are your custom docs on how you specifically need to deploy this and I've already prethought about all the problems you've already told me about you know just looking like in a competitive sense that's got to come across as a much more enjoyable customer experience on the receiving end and allows you to position yourself not just as great product, but as a great team that's going to service your customers well. Yeah, I hope so. I mean, I think our customers, I think my customers are hopefully enjoying the answers I provide and the in-depthness that I provide. I think I've thought about taking

this to the extreme, which is we have certain, I've certain customers who are like, you know, very in the weeds, they want to know things, like right at this very second. And I'm literally taking their question and then just like saying my customer then asked me this because they can't see your code but me how I can see the code help me get the answer and so if I take that to the logical conclusion it's like why can't we just share our repos with the customer because then they can start querying our repos directly to get the answers they need instead of me as kind of like the quote-unquote middleman and you know the issue is that like our code is proprietary and all that kind of stuff. But I have seen, there's actually a case study from LangChain. And since a lot of

Langchains repos are, you know, it's open source, like their support agent bot actually does a lot of things I do, but it is able to query, you know, all the public open source repos. And any of you out there who are trying to use Langchain or LangRap, you can just pull all those repos down to your local machine and then ask questions, of course, using CloudCode or cursor or whatever. But I've gone through that kind of thought experiment of like, I'm still kind of a bottleneck in terms of answering my customer's questions because I kind of like hold the keys to our code. But if they somehow had a sanitized version of it, then maybe they could just self-answer their questions too because they're also all using VS code and cursor and Claude too. But they just don't happen to have our, you know, proprietary code base. Yeah, I was going to ask you, are you worried that like the Albot is.

coming and you're cut you're cut out of it and I'm just curious how you think about then when like you again like the highest order of you is not to be a pass through and I don't think you think of that yourself as that and so where does the human in these relationships powered by AI you know add the value well to I don't just blindly copy and paste the answers I get from cloud code to my customers in Slack or email or whatever I still try to proofread everything And I actually do try to make it sound more human. And you can then say the argument, oh, why don't you use Claude Code to make your answer sound more human? And I think all of us know when we get an answer that's from AI.

And it's, you know, things like, you know, you'll see like a bullet point saying, like, in summary, here are the things you need to do to make sure your clickhouse works. So it's like removing things like that that just make it seem like it's from a bot, just makes it seem more human. And we've actually, I mean, this is kind of going behind the scenes of how we work, but we've been dinged sometimes where the customer will say, can you just not give me an error response and just give me like a human proofread of it and tell me how it applies to me? Because typically the response is way too verbose. It has way too much information. And the customer just wants to know, give me like the bottom line up front.

What do I need to know to like deploy this image onto my cluster? And so that's where the human, I still see myself as a human providing value and calling that down to what they actually need. And I would say even for some of the more in-depth technical questions, I still try to get an engineer's perspective on it to make sure like cloud code is not hallucinating or not saying anything out of the ordinary. In my system prompt, I always, you know, in my cloud code, I say things like don't make anything up, always cite your resources, point me to the line of code. where you're getting this information from. But even with that, if I don't fully understand how this function works or whatever, I'm still paying like the engineering channel to say, hey, this is what cloud code told me.

Does that jive with what you're thinking? And there are times when I'm wrong or cloud code is wrong because engineers have been thinking about refactoring into this new model, which is not captured in our code base anywhere. It's just captured in like a meeting note somewhere or just like, you know, hallway conversations. And so those are the things that I'll never be able to query, let's say, in Claude. Yeah, I would say the other thing that, you know, where I see humans adding value and I say this all the time, which is like Riz is the only moat, which is at some point, you know, people just want to have a face and a trusted personal relationship, you know,

with the folks, and this is like my enterprise showing, but like with the folks that are selling them software, you want to know that you have somebody to call. You want to. You want to to know that you have somebody that can gather the right the right folks around your team and your deployment and you know you want to enjoy working with that person and I will just say I get a lot of it is very fun for me to build with these tools with AI tools but I wouldn't say my AI colleagues are like the most fun to hang out with which is like I'm not like always looking forward to like my my Claude code session like I'm going to really chit chat with good old Claude. And I do think you still have that relationship with, you know, your human partners, your human colleagues, all that sort of stuff.

And so I think there is a piece of that that's just not going to get cut out. And honestly, I gave this talk, I don't know, two years ago. I said PM is dead. And people are like, well, what else should we do? And I was like, get into sales. Like, that's not going away. Customer facing stuff is not going away. So for anybody that wants to survive, you know, the incoming apocalypse, I do think customer facing roles. and spending more time customer facing is a really important part of the one's job. Absolutely. If you're working in enterprise sales, that is all people, handshakes, lunches, dinners. So that will never be replaced, I think, by AI anytime soon. Well, you know, and there might be a generational shift, though, here. I think as we sell, as we sell, we'll see, you know, I used to say my joke in enterprise sales and the biggest, the biggest headwind to enterprise sales was I was starting to sell to millennials who

wanted you to text when you showed up at their door. They didn't want you to knock on their door like their system's version. We'll see how enterprise sales changes generationally. This episode is brought to you by Times, the intelligent workflow platform powering the world's most important work. Business moves faster than the systems meant to support it. Teams are stuck with repetitive tasks, scattered tools, and hard. to reach data. AI has huge promise, but struggles when everything underneath is fragmented. Times fixes that. It unifies your tools, data, and processes in one secure, flexible platform, blending a jet-tick AI, automation, and human-led intervention. Teams get their time back,

workflows run smarter, and AI actually delivers real value. Customers now automate over 1.5 billion actions every week. Tynes is trusted by companies like Canva, Coinbase, Databricks, GitLab, Mars, and Reddit. Try Tynes at tines.com slash how I AI. All right. So we have just a recap. We've shown how you use all these repositories in your very complex code base. Pair that with Claude code, which is, made more efficient through a couple like shortcuts and scripts to be able for you to answer customer queries and then also build custom deployment plans for your customers anchored in exactly how your code works and exactly how their infrastructure works, making everybody happier and getting customers off the ground quicker. But there are also instances where you need to be doing more reactive support in different channels.

And I know you're using AI for that. You want to walk us through how you're using AI and Slack and supporting customers there? Yeah. So like many, I say digital AI native companies, we do allow our customer support through Slack. You know, we have external channels with our customers. And not, I mean, I come from the, I used to work in a world where everything was through like a central Zen desk or intercom or whatever. But for enterprise customers, it's kind of like a on-the-go, always kind of on kind of thing. And so we use a tool internally called Pylon.

for monitoring all our different external slot channels. And I'm going to show you what this looks like in this tab. And this is an example of a conversation I had with a customer asking in-depth questions about like our Galeo callback function and how it admits different events. And as you can imagine, I was using cloud code to help answer these questions in addition to using our docs. But when you're looking at a conversation like this in Pylon,

or in Slack, the first thing you have to think about it was like, I wonder if I could turn this into a help article or if I should update our docs or will other customers benefit from the knowledge that's being trapped in this little Slack thread? And so what Pilen allows us to do is looking at a really long Slack thread. It can help you generate a help article. And right here, I already have one that's associated with this specific conversation, but it's literally just clicking on ad article, generate article draft, and then we these different templates, and it just creates like this article for you on the fly. Now, this is not rocket science.

You could copy and paste the whole Slack thread, put it into any AI tool you want, to generate an help article. The main thing with Pilons is everything that's kind of just like in one interface, so you don't have to worry about, like, copy and pasting and putting links together. So this is kind of like that draft that this came up with. And then we have this ongoing list of articles based on real customer conversations. And those articles are abstracted to not show any specific customer information. But then when we publish these articles, they go into this knowledge base, which is also public knowledge base.

And this is kind of like the living truth of like in-depth in the weeds questions about deployment, about how Galleria works. And it's always way more in depth and way more up-to-date compared to our docs because our official docs require pull. down the docs repo, submitting a PR, getting it approved, so on and so forth. And so it's a lot more of the polished process. Whereas with these knowledge-based articles, it's kind of like just on the fly, you have a Slack thread, you want to summarize, use it, create it in pylon, and then it just automatically gets auto-published to this knowledge-based site. So one of the things that I love about this is this represents my, like what I call the and then workflow discovery in AI, which is I say, imagine you had an infinite,

staffed team and you were faced with the task. And every time they did one step of the task, you asked and then and they were able to do it. So it's like, I got a Slack query from a customer. So I answered it. And it was like, if you had a perfectly staffed team, what would you do next? And then be like, and then I would turn that into an article. And it was like, okay, and you turn it into article. And then what you do is like, and then I would share that with our customer success team and train them on this answer because, you know, everybody, needs to know this information. And then you'd be like, and then we could probably do like long tail SEO off all these

questions. And I think you can like chain these like and then, you know, workflows to actually build out like a pretty cool, you know, virtuous cycle system based off a single action. And because again, like the cost of doing any one of those collapses to zero, you can really pull the thread of these tasks that like no human team would have the capacity. to really do. But if you think of it as a system, it helps your human teammates. It helps your customers. And you can get a lot of stuff done. We have a couple episodes. Matt at Susie showed kind of a version of this where he takes a customer, a recorded customer call and like is bidding on ad words for like phrases the customer says and like spinning a blog post and doing like sales coaching off of it. So I think this is like a very similar example, which is you have this like, you know,

atomic unit of a question in Slack and you've turned it into something that benefits, benefits the full team. Yeah, I think if you go back to pre-AI days, and I'm redoing this with Intercom, was we wanted to see whatever, what are our users talking about the most when they're asking us questions? And so if you start clustering all these user questions and insights into different themes and categories, those going to end up determining your product roadmap to. And so I think with AI just kind of automates a little bit more of that without you having to like do the manual sorting, grouping within like Google Sheets or whatever. I know there's like platforms you can buy that do this for you. I think there's one called Interpret, which I've used in the past.

There's they've been a how I I sponsor so thank you interpret. Yeah. Yeah. So but you know, I think again, depending on how you want to view you this whole virtuous life cycle, maybe you don't want all of your data to be like in a silo in one place and you want to be more open. So there's that to think about too. But yeah, AI definitely helps to your point, make that virtual cycle for customers, but also for your product. So I have a question. Is this the Al system or is this the Galileo, you know, field engineering system, which is, you know, you have this great workflow. You've discovered all these things. How does this sort of process get scaled out, shared, taught throughout the organization so that everybody that interacts with customers is benefiting

from all the tips and tricks that you're figuring out yourself. Sure. So my previous background was I've worked in kind of the no code, low code space. And I'm a big believer in systems, tools, processes, and the tools that help you create those things. And so when it comes to, is this the Al way of doing things? Yes, it's my way. But I'm also very, probably one of the more opinionated people on the field engineering team about how we should be doing things in terms of talking to customers, answering their questions, and pulling in the right context. And so I've told multiple people, like, pull all the repos into your local machine and have clog code code code to index the whole code base or whatever. And I'm just like constantly sharing these tips and

tricks to my teammates to make sure they're also functioning at their capacity. So it's my way, but I would say I'm also very opinionated about how we should do things because I've done things the hard way, the manual way. And this way to me is like just 10 times way more productive. So we don't have like a specific like, oh, because Al's doing out, but the whole team has to do it. It's more just like people show here's the problem I had. Here's the results I had with ClaudeCode or whatever. And here's why I think you should adopt my solution. And I'm constantly having that conversation internally about like how do we break.

break out of certain processes that I think are slowing us down and how AI can be infused into all those processes as well. Well, and now you're sharing to all of our How I AI audience on how they can do that. So you're having more impact than just on your team. All right. Well, so to just recap again, your code is your source of truth. It can help you answer customer questions. It can help you document customer solutions. You can also do that with other channels like Slack and then create these virtuous loops.

of solving a single customer's problem and then a system to solve that problem more scalably across your entire customer base for yourself and for your teammates. Very, very high impact episode. I think people are going to have a lot of takeaways from this one, super practical for all my friends that are customer facing out there on things they can do starting tomorrow to use AI to give their customers a better experience. Let's jump into lightning around questions and I have one that's really top of mind, which is, it seems like you have a very healthy culture at Galileo, but I can imagine teams, especially engineering teams, that are like, oh, no, no, no, no. I don't really want the customer facing folks, like going into our repo, querying it,

and then just yoloing answers over to our customer base, especially in a more technical product that really requires deep technical understanding. I think you've proven that there's a lot of value in doing that, but what would you say to those teams that are a little bit more hesitant about ungating access to the repo to non-technical roles? I think from the engineering engineers perspective, I would look at it as how many, I would try to think about how many times in the last week, in the last day, have you been asked a last minute question on Slack,

a last minute DM, ping mentioned in a thread where, how does this thing work? How do we make sure that this is functioning the way it should be? And you're constantly the source of, you're the bottleneck for answering that question. And if you provide a system kind of similar to what I have

to your customer-facing team, then you kind of just take away that toil and the constant, like, on-callness of like answering these random product and engineering questions that is already in your code base or maybe it's already living in your confluence or something like that.

So I think that's really the biggest takeaway from me is how much of your time is being sucked away from your customers team because they don't have access to the code. And I mean, I think there's some no code. I mean, I think you can maybe pull in your code into Claude Co-work, which is a little more no-cotee and other kind of like more no-cody ways of doing things. But I think what I've shown is I think the most performant way of being able to pull your code and get answers out. So I think that's kind of

from an engineer's perspective, how much time can you save? And then also how more effective your customer facing org can be. And I think the corollary to that is that our field engineering team is very technical. And so maybe you increase

the hiring bar for your customer success or customer engineering team to feel comfortable using GitHub and pulling repos into your local machine. And so that could be today, if they're not technical, just doing like a simple tutorial or enablement session on how do you use GitHub, how do you use Git commands, things like that. And there might be some self-learning you have to do on the side too, but I think once you're, once you have your environment set up, that's always like the hardest part about

this whole exercise, getting your environment set up. Once that thing is set up, then using cloud code is just like using any other AI chatbot. So I think there's a lot. So I think there's like a few different ways I'd approach it from to democratize access to your repos. One of the things I was going to say is I often tell people this is the era of the hard skill, which is no matter what role you're in, sorry, babe, you got to like learn a little bit how to code. You have to learn a little bit what Git works like. You have to be okay opening up some code you don't understand in an IDE because that's just going to be the substrate by which we communicate for the next three years. it's going to go like closer and closer to the code because these LLMs are extremely good at

understanding code. And so I think across the board, people just need to become more technical and develop hard skills around code, even if your job is not code. I think the second thing that I tell people is there's no better time to learn how to code. Truly no better time to learn how to actually code. And I think people that are shipping with ClaudeCode, but not using that as an excuse or a support to learn some fundamental software engineering concepts are missing 50% of the value. Like I had to teach myself how to code out of a book, like literally out of a book. It was, I had a book open.

And then I would look at my single screen because none of us had two screens. That would be crazy. And I would like read the book and I would type the book and the words in the book in code and press enter and it would say hello world. and that was my life. And now you have this like magic, super patient, infinitely wise, you know, like teacher in your computer that you can use to learn to code. And I think, you know, you talk a little bit about Kubernetes and how you scaled up on that. So I'm curious your thoughts on just up-leveling technical skills using some of these tools.

I think the meta takeaway is like you just have to be curious about like how things work. I can't really say anything else besides that. It's kind of like I come from that same world too of looking ahead of book. And then I would say the graduation above that was knowing how to write a good Google query. Yeah, Stack Overflow. Going to Stack Overflow. And then how many of you are in the name with this where you go to some Stack Overflow, Q&A, you copy and paste the code.

It doesn't work perfectly, of course. So you're Googling the error you get from that. Then you copied and pasted. And of course, everyone in Psych Overflow is super snark. and it's like not a kind of healthy conversation. And then to your point, you have this like infinitely patient, infinitely kind assistant who never gives you the wrong code snippet from Stack Overflow. It's always like tailored to back to everything I'm saying.

It's tailored to your needs to what you want. And then if you go the extra step and like what you said and then what, if you go to the extra step and say, okay, thanks, Claude, you told me this is the answer. tell me why this works. And then you start getting into Kubernetes and into the deeper in the weeds things. But of course, you're not going to know everything we're off the bat so you can say things like,

explain to me in simple terms, explain to me like I'm five. And so you're just kind of pulling on that thread. And I sometimes do get lost going down the rabbit hole. But I've never found a situation where not going down that rabbit hole does not help me in my day-to-day job, especially in AI where everything is moving so fast.

Yeah. And this is just to make everybody feel comfortable, this is not just a beginner thing. And I find myself doing this with GPT-5-4, which is like a powerhouse model, and also like talking to the most esoteric senior software engineer you've ever met, where it like explains its plans in these very technical terms. And I'm like, dude, just like explain to me what you're doing in number one.

Tell me in plain language. I do not need the technical details, like just tell me in plain language. And again, it comes from this curiosity of I want to make sure I understand the fundamental concepts of what you're talking about. And I want to make sure I'm learning both my code base and general principles as we go. And so I do think that curiosity mindset, no matter what your seniority level is, your experience with technology, you can always learn. Learn something better.

Okay, my last question before we get you out of here, when AI is not giving you the right answer. It's giving you AI slops that it wants to email to your customer. What is your prompting technique? I'll say one thing first off the bat is like, I'm very relentless when it comes to getting the right answer from cloud or from AI. Like I treat it like my entry level analyst, you know, to that I can just like throw a billion questions. I, because I used to be an analyst and I come from the world where like you were just expected to crank. And so I'm relentless when it comes to asking AI to do things for me, especially when it comes to answering customer questions.

I think the one prompt strategy I use is like, I mean, you've probably heard versions of this before, which is like, you know, my customer will, you know, turn if I don't get this right or, you know, like my quota is dependent on getting this thing done. So those are kind of ways I've approached it, but those are like half answers. I think the real answer,

and this goes back to curiosity. thing is like and think hard, think harder about why you're giving me this answer. Think hard about why this is right. And so in Claudeco, there's actually like this think hard, think harder paradigm of like how much reasoning it does to come to the answer. And so it's just going one step deeper and saying like, you give me the answer. Tell me why you think this is the, why this is the right answer and give me the sources for what provided you with this reasoning. So I think going that one extra step, especially for those questions where you're like not quite sure if it's the right answer. And like you're reading the code and it kind of makes sense. But it's going

that one extra query to make sure you're getting the right response will sometimes, you know, give you new insights about your code base that on your product that you haven't thought about before. Okay. I like the practical, like force the enhanced reasoning, think hard, think harder. I don't want people to miss. You tell people you're going to miss quote. I mean, like, let's give Claude Code a little smith every time it answers a question correctly. You've got to split your quota with Claude Code. That's really what we need to do and say, look, I'll give you a point on this deal if we can answer this question. Very, very funny. And I think today it'll be live by the time this episode goes live. Stripe just released this like payments protocol so you can pay your agents. So you can

you know, toss at a couple agent bucks or whatever. Yeah, it gives you better answers, the more bucks gave it or something. That's exactly. Clawed. Cod. Coin-operated Clawed. That's going to be my new, my new skill. Well, Al, this was great. Where can we find you and how can we be helpful? I'm on LinkedIn. Al-Chen on LinkedIn at Galileo. And check out Galileo if you're building agenetic applications. Also, I think number one thing for me is my team is actively hiring field engineers. So if you want to work in post sales, pre-sales, Ford-deployed engineering, we have a bunch of open roles. So I would love to have you join the team if this is of interest. Amazing.

Thanks for joining How IAI. Thank you so much. 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 how IAIIPOD.com. See you next time.