Software Engineering + AI = ?

[upbeat music] Gergely.

All right. I, I gonna assume most of you... Uh, show of hands who subscribes to The Pragmatic Engineer? [audience member cheering] Oh, my God.

Wow.

Uh, he is, uh, he needs no introduction then. Let's get right into it. Um, what is token maxing, and should everyone here be doing it? [laughs] [laughing]

So I, I heard about token maxing a week ago, or like week and a half ago first, and you know, some people have been doing it for longer, and I tweeted about it, I think three days ago saying, "Oh, there's this to- token maxing."

And again, you, you see it on social media, and my DMs were blowing up from, from people at large companies. I don't wanna name names, but like, you know, Meta- [laughing] ...

Microsoft, uh, some, some, some other ones as well like, uh, the likes of IDN and, and, and so, so many more. And the story is a little bit different every, at every company on why people are doing it and whether they like it or whether they think it's good, but there's a few, few common themes.

One is token output at these larger companies is measured in, in some way. There's like either a leaderboard or there's a way to look up your, your peers. Salesforce, for example, you can check the spend, the, the money spent that every, every person at the company did.

You can like search in a tool that someone built, and it shows how many dollars they spent on, on AI-related tokens. And, you know, first there's this number, then there's this uncertainty on in the tech industry, right?

We're kind of hearing layoffs, like massive cuts at the likes of Block, and, uh, I mean, they're like, no matter how much tokens people spend, they were let go independent of this.

But people start to think like, "Does-- is it part of performance evaluations or promotions or all that?" And the answer is, mm, kind of. [laughs] So inside of Meta, uh, I talk with managers, and in the performance evaluation, they have this data point, which is one of many data points, right?

The same way as, as like diffs or impact or, or code reviews of how helpful this person is. But they do, just like with any data point, they sometimes pull it and use it.

So typically, and just like any data point, it can be weaponized. So like a low performer with low impact and a low token count, clearly not even trying. So...

And a high performer with high impact and high token count, clear that's innovating and this must be doing good. So inside of these companies specifically, I talk with a lot of people at, at, at Meta, and again, this is not representative of one hundred percent of Meta, but they have this leaderboard where people showed up and they

have like massive amounts of tokens and a lot of engineers got just scared, worried, so they start to token max to try to generate tokens. Stories that I've heard first or well, secondhand from these people who, who, who told me s- firsthand is, for example, instead of reading the documentation, I will ask the agent to summarize it

for me and ask questions even though it doesn't do a good job answering it, but my token count goes up. People just want to not be in the bottom twenty-five percent or bottom fifty percent for token count where these things are measured.

Inside of Microsoft, again, there's a leaderboard and I'm talking with people, they're like, "It's ridiculous like how some people are just running autonomous agents to build junk, honestly, for the sake of having that number go up."

And, and sometimes it gets ridiculous 'cause like inside of Meta, uh, they had this leaderboard. They got rid of it after an article came out and it looked, um, stupid, honestly.

So whoever built it, like just, just like closed it down. But people are still token maxing, by the way, because there's this, this thinking that it might have gone, but you know, we're engineers.

And don't forget, these are high-paying jobs, right? Like, like you don't really wanna lose a job over something stupid as like you didn't have a high enough token count, and that's how it feels.

But inside Salesforce, there's a target of minimum spend per month. Like I think it's like a hundred and seventy-five dollars between things. So like people are like, again, you kind of like, you know, beginning of the month, like just token max to get there.

So it's, it's, it's weird and it started as a joke earlier. Like a few months ago, token maxing was really just people like going crazy and enjoying this thing and building cool stuff, but it's kind of turned into, in a lot of companies, I, I think it's just a culturally weird thing.

So it's a weird time to be in 'cause I remember lines of code used to be when, when early, uh, developer productivity tools came out like Velocity and Pluralsight Flow, they kinda measured lines of code and, and number of QPRs.

And we know that was stupid and people kind of optimized for that at companies that did it. But it's, it's almost like w- now it's the top running companies like, uh, Meta or Microsoft who are incentivizing people just to do just stupid sh- stuff, honestly.

Yeah. Those are wild stories. And one of the things-- You're clapping for that. [laughs] [laughs] [laughing]

That deserves another full conversation. [laughs] Uh, one of the things I liked about talking with you and subscribing to your newsletter is that you basically kind of anonymize all these stories from, from real, uh, incidents and real examples.

Um, why is it that, um... Is, is this still worth it, right? With all the flaws, uh, you know, when you have Goodhart's law, like what, what, whatever gets measured, it gets, uh, sort of abused.

With all the flaws, is it still worth it? Uh, you know, uh, is, is, is AI basically still making us faster overall? Like the, the cost of token maxing is still-- With all these like really ridiculous examples, is this still net worth it?

Yeah, so don't forget, like the reason token maxing is probably a thing is like let's just go back to six months ago where

I, I, I was at a, I was at a CTO like dinner conference, whatever, like a bunch of CTOs gather, CTO-level people. Th- this, this was in Amsterdam, and we had like, like a bunch of people, and there we were talking and, and one of the CTOs, like the, the, the Amazon of the Netherlands, uh, there, there's

a, an e-commerce company, was saying like, "Hey, like e- everyone, like I have a problem. Like engineers on my team are really skeptical of AI, and they're not really using it, the AI tools."

Don't forget this was before Opus four point five and those models were, were out. They were not as, as productive. We had, uh, we already had a Cursor and, and the like, and they subscribed.

They're like, "They're just not using it that much on existing code bases," right? And, and next to them, uh- The head of the Dutch National Bank said, like, "Oh, we don't have that problem.

Our engineers are using it 'cause our, our mission is to regulate this thing, so we need to understand it," and they're kinda motivated. And there was this time where experienced engineers were kind of holding on because if you had an existing code base and used AI Cursor, whatever, on it, it was mildly useful, if that even.

And these engineers were like, "Why should I use a tool if it doesn't help me refactor, it doesn't find the bug, it doesn't do what I need to do?"

And leadership saw they're not really using it, and they kept hearing, you know, the likes of Anthropic, for example, was already saying how they're writing a lot of their code with, with Claude code.

Uh, and it just keeps increasing. And Anthropic's, you know, like, revenue is going up like this. So those leaders are kind of... They might be confusing correlation and, and, and you know, like, which one comes first, but they're like, "Well, we should be using it more because probably good things will happen than just bad things will happen

if we don't use it." So the whole targeting and measuring things, it actually came from leadership wanting, "We want our engineers to use frigging AI. I don't care what it is."

And it, it was a bit of a push. Like, we know this is bad, but it's, it's better than them using it. The best example is Coinbase, where, uh, Brian Armstrong, the CEO, just, like, fired an engineer, or he sent an email saying, "Everyone, like, needs to get on board and use AI tools, and whoever doesn't use

it in a week, I'll have a conversation with them." And then I think a week later, Saturday, he fired an engineer. And you know, like this, again, high-paying job, like, we're talking base salary of like 3, 400K, thousand dollars per, per year.

Uh, and then both s-s-equity and everything on, on top of it. Like, they got the message. Everyone just started to just, you know, like, use it. And you know, back to your question.

So on, on one end, there, there's a push, and look,

I feel it's a little bit like this is gonna be controversial, but have you ever worr- wondered why big tech loves to do LeetCode-style interviews, algorithmical interviews, which have nothing to do with the job, and, and we know it's the case.

And there's a lot of criticism for this, and they've been doing this since, since, like, 20 years. But here's the thing. It selects for a specific type of person.

It selects for the person who's smart and willing to put, put up with absolute bullshit to get the job.

And this person, you know, they will study two months pre-AI, two months or three months of LeetCode, which again, makes no sense on the job, but you do it.

You get in there, and this person will be putting to, to put up with bullshit that makes absolute no sense to keep the job. So token maxing happens at large companies, and people are putting up with this BS.

And look, a lot of them are smart, and they will make the most of it. Some of them will build cool stuff. Um, it's, it's the reality, I think, of big tech.

So we're in this weird place where big tech is a bit weirder than startups where, you know, no one cares about token maxing. They care about, like, just building stuff and, you know, use whatever makes sense.

Uh, don't-- People will care about the cost.

Yeah.

But, but going back to your question, like, like, you know, like, is, is it making us productive a-as, as a whole? Uh, like, individually, it's, it certainly is, and as teams, we're kind of like a big question mark as we should be moving faster.

And there are a few companies that do. Anthropic is a good example, but a bunch of companies are, like, not. It's, it's, it's... It seems it's hard to retrofit all this AI into, like, the way we have been working.

Yeah. Uh, one of my favorite studies from last year was the meter study where they, uh, did a blind test of, uh, people and, and their expectations of productivity, right?

And, uh, basically, the, the end result was they felt 20% more productive, but their demonstrated results was actually they were 20% less productive on average.

Yes, but that, that study was very interesting 'cause they-

It was a very small sample size.

It was 30 people, and there- [laughs] ... one outlier, uh, who actually was way more productive.

Quentin Anthony. We, we interviewed him on the pod, yeah.

Yeah.

Yeah. So he was the one productive AI engineer. [laughs]

Uh, but anyway, so, uh, actually, my theory is that, uh, something that I've seen on my team is that I've been enabling coding agents for the rest of my team who are non-technical, right?

And, uh, you as the engineer may not be more, much, that much more productive because... And, and you can be more productive if you, uh, attend AIE. But, uh, [laughs] if you actually enable your non-coding, uh, your, your non-coding co-collaborators to code, actually, they are more productive 'cause they don't have to wait for you, right?

And, and that's that, like, unlock of like, oh, suddenly you have serverless developers, basically. [laughs] Uh, and I think, I think that's, that organizational coding thing is different than studying pull request level productivity for the individual developer.

Yeah, and, and the thing that still, I still remember to this date, I, I talked with Simon Willison, I think in 2024, so two years after ChatGPT came out, and he was Simon Willison, top commenter on Hacker News, or he's, he's, he's-

That's his-- That's not his title, man. Top commenter on Hacker News. [laughs] What the fuck? [laughs]

No, he's, he's-

Creator of Django, top blogger, yeah. Uh, prompt injections. Tr- uh, yeah.

Yeah, he's actually not a top commenter. He's the most submitted blog 'cause he blogs so much.

Yeah, yeah.

Like, like, and he's... But he told me back then, he said, like, "This thing, AI, is, is just so hard to, to get good at." He's like, "There's no manual."

And he's like, "I've been doing it back then for two years, and I'm still, I'm still figuring out what works and what doesn't. I keep changing my workflows." And I think that's something that is a bit hard for us.

Two things about AI that for any of us engineers is hard to understand. One is it just takes a long time to get good at it, and you need to keep doing it.

And the second thing is understanding the theory will not make you better at using the tools, which is an absolute mind fuck, honestly, because we're so used to, you know, you understand how the compiler works, how assembly works.

Okay, you will now be more efficient if you wanna write low-level code 'cause you know how it works. But with, with these things, I mean, you, you can-- Of course, it's, it's helpful to understand how, uh, how the, the architecture under-underlying works, attention, uh, the different, the, the different probability sets, et cetera, et cetera.

But it will not help you get a sense for how you can use it. And then once you figure out how you can be more productive if you're s- if, if you're inside of a team, again, it kind of breaks, and you have to re-learn again.

But, but the more effort you put into it, it, like, it's clear that it's, it's working, it's helpful. And I think it, it's-- The teams I'm seeing getting more value out of it, low ego, open to learning, open to leaving your priors behind.

The word priors I have not- ... use forever, and I fear we're in the stage where, like, just, just leave your pyres behind. Just have an open mind and, like, don't leave your experience behind, but, you know, be open to it.

Yeah. Zooming out a little bit, how is the role of the software engineer changing?

I think it's always-- This was always coming, but, uh, AI is just, just speeding it up. Uh, even before AI, a few s--

It, it's interesting how you see, like, startups in, in many ways, venture-funded startups are kind of front-running what the industry will be cashing up 'cause venture-funded startups are about fast growth, uh, doing th- mo- moving fast with smaller teams because smaller teams m- mean smaller costs e- even pre-AI.

So a lot, a lot of these venture-funded startups started to expect a lot wider range of roles from engineers. For example, DevOps as a whole, uh, inside VC-funded companies from the mid-2010s, every engineer was kind of, like, responsible for the code they deployed.

But, like, more traditional companies, they had more money, more-- sorry, more-- less pressure. They kind of have dedicated DevOps teams and some of those things. So in, in the industry, like the software engineer is now becoming, like, the kind of-- The tester role has collapsed into software engineer.

We-- Most companies don't have dedicated testers. Very, very few do. DevOps collapsed into here. Uh, and now we're starting to have the product role also starting to come. So a lot of companies, even, like, in twenty twenty-two before AI, started to hire for product engineers.

That's happening faster. And I think the, the last push that AI is doing is even for early career engineers, there's a lot more seniority expected or, or senior-like things, planning about things, knowing about the business.

So I, I, uh, I, I think the role is-- expectations are, are higher. Teams are also getting smaller everywhere. I talked with someone at John Deere, two hundred person, uh, two hundred-year-old company, sorry.

Uh, you know, like, they do tractors and, and all, all, all that stuff. And, and inside of that company, one of their, their VP of Engineerings was telling me how they're actually seeing that their two-pizza teams are now just one-pizza teams inside of that company.

It's the reality partially because of these tools.

My-

So-

My joke used to be I am a one-pizza team because I eat a lot of pizza. [laughs] But, uh, depends how much pizza you eat. Uh, there's-- Uh, so I'm sorry to interrupt.

I don't know if I cut you off in some, uh, critical point. Uh, there's a comment saying, I've heard it twice even among this audience, where a lot of people are saying that, "Oh, uh, you're no longer engineer.

Everyone's an engineering manager now." And you've been an engineering manager, and I wonder if you agree with that or if you have a different take. You know, because basically you're-- The, the, the common analogy is that you're no longer a software engineer, you're just managing engineering agents, right?

Yeah. If you've been a manager before, that is absolute bullshit. [laughs]

So, so here, here's the thing. The, like, yes, you are a manager without all the things that no one wants to become a manager for. The, the-- When you become an engineering manager, hands up if you are or have been an engineering manager.

Right. Hands up if you actually-- if you've not been and you wanna be one.

Yeah, it's about fifteen, twenty percent.

Good. [laughs] All right, you, you come and talk to me afterwards. I'll, I'll, I'll tell there's a hand up there. I'll talk you out of it. So- [laughing]

So what you think you become an eng- engineering manager to, like, help people's career, maybe have higher salary, higher impact, all, you know, there can be a lot of dynamics.

But the reality is, is, is you, you become more removed from the product, and you have to deal with people problems. And the thing with, with agents is you don't have to deal with people drama, people problems, conflict between your team.

I mean, unless the next generation of agents starts to fight with each other, I think that'll be something. But y- you actually, you, you do have to orchestrate, but it's more like a tech lead role or, or, or, or experienced engineer where, where you're, like, mentoring, uh, mentoring engineers, but you don't have the people management.

You don't need to worry about the personal problems. So it's actually a lot more kind of empowering. And I was talking with, uh, the podcast was, was just out, uh, yesterday with, with DHH, uh, creator of Ruby on Rails, who said, you know, people tell-- told him like, "Okay, it's, it's like managing things," and he's not excited

about managing agents, but he feels it's more like a mech suit where you have, like, you, you can do seven things at once. You can do it a lot faster, and you're in control, and that's more what it feels like.

So there's orchestration, yes, but it's very different to management. And also, the, the really, really bad thing or honestly shitty thing about management if, if you make it into management, which makes this hard, also rewarding later when you, you tell yourself at least this thing- [laughing]

... is you start a project with all these people under you. You know, congratulations, you've got ten people. Wonderful. And you start a project, and in six months, you will see some results of the decision that you made.

With agents, it's just so much faster. So the, the feedback loop is faster. So I, I think it's, it's not much of it except for the orchestration. And, and, and for that, everyone's gonna have their own flavor.

Some people will, will have the tendency to, like, run multiple agents, and they're good at this or be good at it. Some people just do, like, two agents. Michelle Hashimoto, I interviewed him.

He has two agents. He always has one agent running, the, the, the, uh-- No, he has one background agent that he does, and that's it. He's like, "Two is enough for me."

Great.

Yeah. Yeah. Uh, we're figuring out the patterns. Um, uh, I wanna pi-- hit you on large tech infra. [clears throat]

Uh, this is something that, uh, I think both of us are very excited by, by, uh, good infra, which is a very niche, uh, interest. What are you seeing?

It's wild to see how much of the-- So I, I said that from externally, a lot of companies, a lot of big tech companies, especially the ones that are spending a bunch on AI and have platforms using all that, you're not seeing too much, like, more come out.

Like Uber is a good example. I'm not seeing too many more features come out of Uber or a new product launch, and they're like, "But what's going on?" They are really investing in AI.

But when you look inside, there's a whole lot of buzz. They are rebuilding their complete infra. You know, they're-- And I'm not talking about they're buying Cursor or, or Cloud Code or all that.

They're doing that as well, but they're completely, they're building their own own custom background coding agents that is integrated into their monorepo. They are, are having, uh, their own MCP gateway that is, is now integrated into service discovery.

Their on-call tooling is being retooled. Their internal code review system is, like, like categorizing based on risk. They are, like... And U- Uber is one example, but all everyone else Airbnb, Intercom, Meta, Microsoft, even mid-sized companies are just building so much internal infra.

And I was asking to myself, like, why? Uh, it, on one end, this feels like such a waste, but when I worked at Uber for four years, I realized, uh, Uber, they spent so much on, on the internal platform, there's two reasons.

One is honestly, it's a, it's a low-risk way to get good with AI, uh, to be hands-on, and these companies want to be hands-on, but maybe you shouldn't start with shipping AI features no one wants into your code base.

Second of all, because these, these companies have such, uh, so much code that never fit in a context window, by building custom solutions and just basic, basic RAGs, that kind of stuff, they will have better results than off-the-shelf vendors, so they already have a win.

And number three, honestly, is, uh, anything that has AI in it gets funded. So there's this joke of, if you're in developer platform team and you're asking for more headcount, like good luck with that.

Oh, developer platform. Oh, but say that you want to get two extra headcount for agent experience, done. [laughs] Uh, so, so there's that part as well. But, but all of-

And agent experience is just a CLI.

Yeah.

Like [laughs]

Pretty much. But all of this com- in- inside, there's so much buzz and so much work. Everyone's building their own custom system. So I'm kind of wondering how long this will take, but I think for next year, this is gonna happen.

So if you either have friends or if you're work- if you're working at a company, you'll see. But talk with, with friends at other large companies, and you will probably see you are all building the same thing.

If you're at a large company and you're not already building an MCP gateway, what are you even doing? [laughs]

Yeah. Um, actually, a lot of these topics are exactly the things I curated for tomorrow. Uh, so just, uh, fantastic to have you as the closing keynote for today because, uh, it's, it's like a appetizer for tomorrow.

We have talks about MCP gateway and, uh, all these sort of AI architecture and infra things. And I do think like, uh, infra, like,

y- taking AI infra seriously as a company is, uh, very misun- not, not that well underst- understood, and right now, you just kinda learn by example from people because there's not really, like, a, a textbook or anything like about it.

So the way I think about this, because again, from, if you just kind of step out, and we love to criticize big tech of how they're wasting money here and there, and by the way, we love to criticize Google, and I'm kind of thinking to myself like, "Hang on, what if Google ex- actually executed well?" [laughs]

Like, uh, like do we want that? And you know, that would kill all the startups. But, but, but what they're doing makes, makes sense. And Shopify is an example where I'm like, "Huh, I'm starting to get why it makes sense to do all this stuff."

So Shopify in twenty twenty-one, they were the first company to have access to a GitHub Copilot. What happened is the, the head of engineering, Farhan Thawar, heard about GitHub Copilot being developed internally inside of GitHub, and he pinged Thomas Dohmke, the CEO of GitHub at the time, and said, "Hey, Thomas, I heard you guys are doing Copilot."

And he's like, "Yeah, we are. It's internal." He's like, "I, I'd like to get access to it." He's like, "Yeah, but it's not for sale." He's like, "No, no, no, you don't understand.

I, I didn't ask if it's for sale. We would like to roll it out to all of Shopify, and in return, we will give you feedback for three thousand people for, you know, as, as honest feedback all the time."

And so they got it a year before it was out anywhere, and they incurred a lot of churn. It wasn't that great initially. And, and they went through all of this stuff.

And then Shopify was the first company to onboard to like a bunch of other tools, and they gave unlimited budget. And they're spending so much time k- ironing out bugs.

But the reason they're doing it, this is what like made me click, is they are trading off churn and expense and spending a lot more money to be at the forefront of this.

They are a few months ahead or six months ahead of their competition, and for them, it's worth it. It's not worth it for anyone else, right? If you're, if you're in a company where your business is like something, something physical and you don't care, like, yeah, just, just wait out.

It, it'll come. But for a lot of us in the tech industry, this churn is worth it. Plus, what Farhan told me is like, 'cause he, he actually told me he's kinda worried about the cost now, but he was like, "Look, like it's still worth it because if I-- it will look silly if I said you cannot

have these tools. How would I hire the best?"

Yeah.

So it's, it's innovation, recruitment, and it kind of makes sense when you think about it, and the weird thing, everyone's doing it at the same time. So it looks silly, but it, it's rational.

Uh, my next podcast is with Michal Pardé, again, the CTO of Shopify, and, uh, the sheer amount of machine learning that they do and infra that they set up for their customers makes me want to be a customer.

You know? That's, that's, that's like the best, uh, endorsement I can give. Um, I'm gonna get meta little bit and talk about Pragmatic Engineer. Uh, you and I kinda started-ish in COVID.

Uh, you'd just left Uber. Uh, how has it been growing? What, what are the main stats that you're proud of that, uh, you'd like to share with the world?

Yeah. So I, I started Pragmatic Engineer. I, I, um, a joke that if it wasn't for COVID, I, I would probably never have started the, this thing, because what happened with COVID is, uh, Uber had layoffs, and most of the tech industry was doing great, but Uber was not, and my team, uh, was hit by layoffs, and

then we, we had to disperse the remaining people at other teams that our mission no longer made sense. And it was just like a-- the mo- morale was low, my morale was low, so I was like, "Let me take a break."

I wanted to write some books. swyx was writing his book, The, The Coding Career.

Yeah. Some of you have read it. I've met some of you.

Yeah, and that, that's how we met there. And then, uh, my plan was to write a book and then start sort of some startup, something, something platform engineer, Control C, Control V from what Uber was doing inside, and that's actually almost all Uber succe-- U- Uber startups.

It's, it's amazing. Temporal is, is, is from there.

Yeah.

Chronosphere. There's-

If I-- By the way, if I did not start AI Engineer, I would've started Platform Engineer.

Yeah.

That, that would've been the industry conference. Yeah [laughs]

Love it. Uh, and then I star- I started The Pragmatic Engineer, uh, a, a year after I left Uber. Uh, it was just an experiment. Um, I figured no one...

Substack was taking off. No one was writing about software engineering in depth, and I just acted all confidence, saying, pretended that I, I knew what I was doing. The first article was about Uber's platform and program split that no one had wr- written about publicly before, and it's a, it's a free article.

You can, you can now check it out. Um, and it was like when you feel product market fit, that's what I felt almost immediately. The first week before I published anything, just to A confident Twitter post.

I had 100 people pay upfront $100 for the whole year. So I was like, "Whoa, I haven't published anything." In six weeks, I was at 1,000 people paying for this thing that didn't exist before, uh, which was my old Uber base salary back, back in Amsterdam, and it just kept going up.

So like I, I figured, like when you find product-market fit, this is like outside of... Like, there's this rule, like if you find product-market fit, just keep doing what you're doing.

So for me, I just kept writing that one article. I got all these interview requests, collaborations, podcasts. I just said no to all of them 'cause I knew [laughs] the most important thing was to do what makes it successful, which is that one article.

And later, it turned into two articles, and for two years, this is all I did, just two articles. And after two years I looked up and I was like, "Huh," like, "this is actually working.

People like doing it. I like doing it. There's a future in that." And that's when I decided I actually wanna turn this into a business that I don't burn out, because for two years, every vacation I went to, I was working 50, 60 hours.

Uh, I was always thinking, I was writing, I, I couldn't really let go, so I started to grow the team a, a little bit. Uh, uh, I, I... Ellen Bird, the first tech industry researcher.

Ellen, she's a ex, ex, uh-

She's here, right?

Uh, uh, Ellen's not here. Um, Jessica is, who, who just joined, uh, later.

Yeah.

And then, uh, s- so now it was two of us, uh, and I started a podcast a year and a half ago because I talk with so many people, I figured it, it was a bit of a shame to, to, to not have it.

So The Pragmatic Engineer became the number one paid technology newsletter about four months after starting. It stayed there for three years. Now Semi Analysis has-

Dylan versus, uh, you guys. Um, yeah, no, congrats on your success. Uh, I think you, you're also a, a leading v- tech voice in Europe, which I think you're sort of proudly sort of, uh, upholding that over here, which I really wanted to feature.

So thank you for your support for AEI and, uh, everyone thank you too.

Awesome.

Great. [audience applauding]

Thanks, man. [upbeat music]