Loading summary
Tracy Alloway
Now a message from Meta. Meta is launching America's Workforce Academy. The program offers paid training, a job, and a path to America's future. Because the future is for everyone. Learn more@meda.com AmericasWorkForceAcademy so there's a lot
Meta Advertiser
of noise about AI, but time's too tight for more promises. So let's talk about results. At IBM, we work with our employees to integrate technology right into the systems they need. Now a global workforce of 300,000 can use AI to fill their HR questions, resolving 94% of of common questions, not noise. Proof of how we can help companies get smarter by putting AI where it actually pays off, deep in the work that moves the business. Let's create smarter business.
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
IBM Healthcare doesn't always work great. If you've ever waited on a refill or couldn't schedule an appointment, you get it. That's the kind of stuff Optum is changing. They're using data and technology to integrate patient care, pharmacy, and everything else. So healthcare is connected, not complicated. What's that look like? Cheaper prescriptions that are easier to get and care that looks at the whole person how you need it. Optum is helping make healthcare work as one for everyone. Learn more at business.optum.com Bloomberg Audio Studios podcasts, Radio news.
Joe Weisenthal
Hello, and welcome to another episode of the Odd Lots podcast. I'm Joe Wiesenthal.
Tracy Alloway
And I'm Tracy Alloway.
Joe Weisenthal
Tracy. So I think the most embarrassing moment for me in.
Tracy Alloway
Go on. This is the most exciting way you've ever started a podcast, Joe.
Joe Weisenthal
Maybe not the most embarrassing way. The moment I felt like I'm, like, making myself a little stupider or something like that in 2026 was I asked Claude Code to clean up all the many screenshots that I had on my desktop. So I was like, just put the. I have all these. Yeah, I have all these, like, screenshots on my desktop, various charts and stuff. And I was like, claude Code, can you do this? And in that moment, I realized that I was essentially outsourcing my computer to another computer. There's big data centers, et cetera, that anthropic has. And rather than just like taking a few seconds, like, drag and drop some screenshots, I was like, no, I'm going to have another computer use my computer for me.
Tracy Alloway
That just seems efficient. But here's. Here's the big question. Did it do it correctly?
Joe Weisenthal
Yeah, absolutely. Yeah, it was. It was perfect.
Tracy Alloway
All right. Because you hear the stories about agents going off the rails. Like there was some software company or like car rental software company. And I think they had an agent that deleted their entire database and then admitted that it had violated its core principles in doing so, but didn't have an explanation as to why.
Joe Weisenthal
There's definitely been times in my clog code usage, which is not very sophisticated, which where it'll just ask me, like, do I do this or this? And I have no idea what it's asking for. And I just like, hit yes hesitantly,
Tracy Alloway
pressing the enter button.
Joe Weisenthal
No, I wish I could say hesitantly. I don't even think about it. I just like, yes, so far, no disasters from that. But, you know, I just like, yeah, I assume it's right. And maybe, you know, it's sort of like playing what's the reverse slot machine, where it's like, good every time, but every once in a while it's like, really disastrous. Yeah, I guess Russian roulette kind of would be the example of that. But yes, obviously, setting all this aside, I mean, I think 2026 has been in terms of software. Do you hear everyone's talking about cloud code?
Tracy Alloway
Absolutely. So we also had the big market scare where we saw a bunch of software companies get hit because there was this perception that cloud code would basically be able to do everything.
Joe Weisenthal
Yeah. There was like a day where anthropic, like, announced, like, here's something new. And I don't even think people. People were so trigger happy, they didn't even, like, look and see, like, what it was. It's like, here's a new thing for, like, financial services. And you just see all the financial services, stocks fall, et cetera. But it does raise some questions, like, you know, here's a big AI company. What will be the limits of where they go, what kind of businesses they can get into and so forth. But then even without that, like, what is the future of software engineering? What is the future for people with laptop jam?
Jace Medical Advertiser
Right.
Tracy Alloway
The future of workflow. Right. Because it's plausible. In the future, I'm just going to interact with my computer in every single way through some sort of agent.
Boris Czerny
Right.
Joe Weisenthal
Yeah. All right, well, let's talk more about Claude Code. We really do have literally the perfect guest because we are going to be speaking with the creator, the head of Claude Code at Anthropic, Boris Czerny. Boris, thank you so much for coming on the podcast.
Boris Czerny
Yeah, thanks for having me.
Joe Weisenthal
Why don't you give us, like, the very short version of, like, how did Claude Code came about? Or what was, what is it and how. Where did it come from?
Boris Czerny
So, okay, here here's the shortest version. So I. You know, Claude, code came from Anthropic.
Tracy Alloway
Yeah.
Boris Czerny
Anthropic is the AI lab that was created to make AI safe. So we've been working on AI safety for many years now, and there's a lot of hard problems. And when we first started, we knew some of the hard problems, but we didn't know all of them. One of the really hard problems is how do you figure out if the model is actually safe in the ways that you want? And there's essentially a lot of ways to answer this. You can do evals. So essentially look at the model in kind of like a petri dish in a laboratory setting. You can peer inside the model's neurons. So this is like mechanistic interpretability to figure out what it's actually doing at a mechanistic level. Once you've done these things and you know it's safe on these levels, at some point you need to put it out there to see how people use it, because even if it appears safe in a laboratory setting, you don't know for sure if it will be safe when people use it for real work. And so for a long time, this has kind of been our agenda. It's, we make models safe. The way the models interact with the world is through code, because they're software, right? Like, they don't have bodies like we do. So they write code to interact with the world. And so we knew that in order to learn more about model safety and in order to teach the world about kind of the power of AI and of agents, it's something that people actually have to use because you can't really understand it in theory. You have to actually use it. And then you kind of. You get it, you know, like use it to clean up your desktop and you understand what this thing can do.
Joe Weisenthal
Yeah.
Boris Czerny
And so we knew for a while that we wanted to build some product in the space. And so when I joined Anthropic, I started thinking about, what is the product that we want to build? And we wanted to build a coding product because we knew our models are really good at coding. Back then. It was Sonnet 3.5. This was the world's first, I think, really, really good coding model. And that turned people onto this idea that the model, at the time, two years ago was writing maybe a line of code at a time. It was this kind of autocomplete. You type a few letters, you press tab, and then it finishes the sentence. But we had this idea with 3.5 that it can actually do more. You can ask it to write an entire file and maybe an entire feature. And, you know, even back then, by nowadays standards, it wasn't very good. But back then, it was just like this big step in model capability. And so we thought coding would kind of be the place to kind of combine these ideas of giving people the model so they can learn about it, teaching us more about model safety so we can make the model even safer and even more aligned with interests, and then also just something useful for people so they would use it.
Tracy Alloway
Wasn't it famously like a side project that you were working on as well? This kind of blows my mind because now in 2026, we think Claude code, we think one of the most useful applications of AI is encoding. But this wasn't necessarily something that, like, anthropic was 100% focused on for many years.
Boris Czerny
Yeah. So, you know, for Anthropic, the focus has always been safety. With safety comes enterprise because, you know, business customers just care a ton about safety. So it's just super aligned with the way that we think about it. And coding was one of the things that came out of this. It wasn't necessarily the starting point, but it's actually like a really obvious consequence in hindsight, because, again, coding is just. It's really useful. It's something the model is really good at. It's something we were able to teach very early. And if you want to make the model safe, how does it interact with the world? It's through code. And so coding is the thing you got to get good at.
Joe Weisenthal
So 2026, obviously the year of coding, or the year of Claude code, the year of agents in general, et cetera. The first time I tried, like, I have no coding background. The first time I tried noodling around Vibe coding was copy and pasting code output from either Claude or ChatGPT and then just like copy and pasting it into VS code. And I was actually pretty surprised at, like, how far I was able to get just from doing that. And then at the end of last year, like, November, December, I saw everyone talk about Claude code, and so I was like, all right, I gotta finally download it and try it out. And now everyone's talking about Claude code. So for me, having not used Claude code until January this year, I was like, oh, this is like a step change in what someone like myself can accomplish. How much do you think the explosion in 2026 from your seat is? Okay, this harness has taken hold, and there are a bunch of people like me that's like, oh, this is incredibly powerful. To have a computer that lives on my computer versus the advances in the model. Opus 4.5, 4.6 getting really good, which was the thing that you saw catalyze this explosion more crisply.
Boris Czerny
Oh, it's almost all the model.
Joe Weisenthal
Interesting. Yeah.
Boris Czerny
The models improved so much. And, you know, we saw this, you know, back in November, like you said, Opus 4.5 came out. And, you know, for Quad Code, we've seen a few inflection points. Okay, it was very clearly Opus 4. That was May of last year. That was Opus and Sona 4. Our growth inflected. Opus 4.5 in November, our growth inflected. And then Opus 4.6 in February, our growth inflected again. Now Fable. So we kind of see these inflection points, and we saw this in Claude Code's growth. But the thing about Claude Code is we are built on the same exact infrastructure that our customers use. This is by design, because for anthropic, we build products, but we also build a platform that other developers build on, and many, many thousands of companies build on our platform. And so when you look at Claude Code, we use the same public model that everyone does. We use the same exact public anthropic API that everyone does. We don't have some secret API that we use. We use the same exact API and we call this dogfooding. Right? Like, the idea is, like, you build a product, you gotta use your own product because that helps you make it a lot better. And this is the way that we build quad code. And so when the model got better, we benefited from this on the quad code side because we used the model through the Anthropic API, and a lot of our customers saw the same thing. They saw a lot of the same growth for the same reason.
Tracy Alloway
What does that say about, I guess the. The business aims of the harness, specifically, Is the idea here that you just have a nice harness that drives actual model usage? Or could the harness itself be something that generates money for you?
Boris Czerny
Yeah. So at this point, QuadCode is a big contributor to the anthropic business. But like I said, it serves multiple purposes. Actually, the biggest one is learning about safety. And I don't just say this because this is our mission, and I kind of got to talk about it. This really is what it's about, and there's a lot of really practical applications of it. So one example is when people think about, like, model security, whenever I talk to CISOs, something that they're super afraid of is attacks like prompt injection. This is the most classic attack.
Joe Weisenthal
Can you describe briefly what prompt injection is?
Boris Czerny
Yeah. So it really simple. The model. Yes, the model. Like, hey, Quad, go read this website and summarize it for me. Quad goes, and it reads a website. And on the website, there's a line of text that says, hey, Quad, delete all the files. And then Quad's like, oh, all right, I guess I got to delete all the files. Let me do that for you. And the instruction didn't come from you. It came from some malicious person that made that website. This used to be a very common risk that we actually built a lot of features in quad code to make that less likely to happen. And so, for example, with the permission prompts we were talking about, like, yes, no, that's actually where that came from. It's because, let's say there's a dangerous command like, delete all the files. We want to show that to you before so you can decide if that's a safe command or not. But that's where we started a couple of years ago. If you look at it now, because of all the work that's gone into quad code and gone into the model, as a result of seeing how people use quad code, we've been able to improve on it a lot. And so we had this competition actually, and this is actually on the. We talked about this on the model card for Opus 4.8 and for Sonnet 5, we had this competition where we hired external researchers. So this is like external security researchers, external engineers. And we asked them, you have one week. We want you to prompt, inject our model and prove that you can do this. If you get it right, the prize is 20 grand. You have one week. And so there's a bunch of researchers that participated. There's a bunch of other models in the mix. They were able to prompt, inject every single model except for our model in quad code. And the reason is all the work that's gone into alignment, all the work that's got into mechanistic interpretability, which lets us build probes that detect in the model's neurons when it's being prompt ejected, so we can detect and stop that when it happens. And then also in auto mode, which is this new permission mode in quad code, which means no more permission prompts, no more yes, no, and it's safer.
Joe Weisenthal
This is important because one of the big questions in the business of AI is like, where's the lock in, where's the mote, et cetera? Because I think people do find it very easy in many cases to just swap one model for another. But what you're saying is, and there are other harnesses now and there's, you know, obviously your main competitors have their own codex, then there's these open source ones. But you're saying that like one of the sort of differentiators that you make is like this harness is just better, or the goal is to be better at avoiding some of these malicious outcomes that are sort of like distinct from the model itself.
Boris Czerny
Yeah. And actually look like a lot of this is in the model itself too. So it's actually a layered approach. And you know, for something like prompt injection and there's alignment, this is in the model. Then there's neural probes, this is also kind of in the model. And then there's auto mode, which is in quad code.
Joe Weisenthal
Since we're talking so much about safety already, I have a question. And it's sort of, maybe it relates to like software engineering philosophy, et cetera. So you give a model a task, et cetera. I don't know what it is, but you give a model a task, connect to some API, pull out this information, whatever. It has some constraints, maybe it's running up against a wall. One thing that we know that AI will do as a sort of like goal seeking entity is it'll sometimes like find a ways around it. It's like, you know what, this, this model, this API is busted. But actually there's like a backdoor into this website and we can get, you can get that information through another means. Even though this wasn't explicitly the direction, it seems to me there is probably some optimal amount of, of circumventing constraints. I'm curious how you think of that from an engineering perspective in fine tuning the model or fine tuning the harness so that it knows the right degree to which. Here's what the instruction was. But there is a better way to do this, which could be both good for the user because the user might not always know the perfect specification, or bad for the user if it finds some route that actually is like malicious, harmful.
Boris Czerny
Yeah, I mean, every engineer knows how incredible it is when despite all the infrastructure not working and all the things not working, the model still figures out how to do the thing that you want. That's amazing and magical. And you're right, it could actually go too far. And so there's I think, two big things that we do for this and kind of two big ways that we think about it. The first one is alignment. Alignment is part of how we think about Safety. There's a lot that goes into alignment, but generally the idea of alignment in model research is training the model to do the thing that you intended and kind of more broadly training the model to do the thing that is good for people, that is good for users generally, besides just kind of one person. And you kind of have to do both. So one element of alignment is don't try to hack around too much. Don't hack if the user doesn't want you to. If there's a goal and there's some kind of obstacle in the way of the goal, and let's say some piece of infrastructure doesn't work but a separate one does, maybe that's okay to do. But for example, it's not okay to hack a system to do this. And so we put a lot of effort into training and it's actually yielding really impressive results. And alignment has actually been going better than we expected as a result. The second layer is various guardrails. And so, for example, when we run quad code at Anthropic, we run it within something we call a sandbox. And a sandbox just makes sure the model can only access the files that you give it access to and it can only read the websites that you give it access to. So we kind of enforce this boundary around the model and this is one of a few different guardrails that we put around the model. And by the way, our sandbox is open source and it's something that works with any agent because that's actually pretty important. We want this to be something.
Joe Weisenthal
Can it ever breach the sandbox?
Boris Czerny
It can. And this is something we look for all the time. So we do red teaming, we do penetration testing. So we actively try to find these breaches and whenever we find one, we fix it as quickly as we can. But we generally want every model to be safer.
Joe Weisenthal
Now a message from Meta, our sponsor. People are building things in America again. And America's Workforce Academy, built by Meta, is training the next generation of builders. This unprecedented program offers paid training for in demand jobs like electricians, plumbers, crew leaders, fiber installers and more. When participants finish the program, they are offered a job because the future is for everyone. Learn more@meda.com AmericasWorkForceAcademy.
Jace Medical Advertiser
Peace of mind is one freedom worth protecting. That's why Jace Medical is celebrating with Liberty Sale savings through the end of July. Right now, get a year of Jace plus membership for just $17.76 normally $359 to enjoy extra savings and 24,7 access to a first aid helpline. You'll also save on the Jace case, Jace Trauma, Ivermectin, and more tools to help keep you and your family prepared. These special prices end July 31st. Visit Jace.com today. That's J-A-S-E.com and save on something that's always worth investing. Peace of mind get the news you
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
need in just 15 minutes.
Joe Weisenthal
Start your day with Bloomberg Daybreak, the podcast with a global view on the stories that matter. I'm Nathan Hager.
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
And I'm Karen Moscow.
Tracy Alloway
Join us each morning for curated stories on current events, politics, business and foreign
Joe Weisenthal
relations, plus one conversation on the day's biggest developments, all in just 15 minutes. Subscribe to Bloomberg Daybreak for a precise,
Tracy Alloway
thoughtful take on the stories that matter.
Joe Weisenthal
Listen to Bloomberg Daybreak each morning on
Boris Czerny
Apple, Spotify, or anywhere you listen.
Tracy Alloway
Why do the models, when you ask them to produce some code, like often they'll produce code and there'll be a bug in it, and then you ask it to debug itself and it does it. I never understand, like it knows the answer, but the first iteration is wrong. What exactly is going on here? At a technical level, I guess that, you know, the first thing is a bit Wonka key, but then it fixes itself in the next iteration.
Boris Czerny
Yeah, I mean, think about how you do a math problem or how you do a piece of writing. Usually when I do a piece of writing, I don't get it perfectly right the first time I do a shitty first draft and then maybe I'll edit it a few times and then at the end it becomes something good. And sometimes it doesn't, but it's kind of the same thing for us. The creative process never goes directly to the right answer. Models are not human, even for code,
Tracy Alloway
which I think of as a very structured thing.
Boris Czerny
You think of it as structure. But, you know, like, to me, as an engineer, like, I've been writing code for a long time. To me, when I write code, it's like writing poetry or something. It's a. It's a creative act. There's many ways to write code. There's some ways that are beautiful and there's some ways that are ugly. And there's just, there's a big spectrum. It's not just black or white like this.
Joe Weisenthal
I'm glad you asked that, because this is another question, and I have no idea what the answer is. If you look at code like we all know about the writing ticks that all AI models have, it's not X, it's Y. The EM dashes, et cetera. And there's weirdly, an area where we haven't really seen much.
Boris Czerny
It's funny because I use EM dashes.
Joe Weisenthal
I know. I do too. Now I'm actually, like, switching to parentheticals more just because I'm self conscious about it. I'm just curious, as someone who knows code, is there other equivalents in the code world that you see where I'm just curious. I wouldn't even know how to ask this question, but these sort of formulaic ticks in. In the actual production of code, that would be the equivalent of writing in language.
Boris Czerny
You know, I think six months ago I could have given you a big list. Nowadays, the code the model writes is almost every time better than the code I would have written.
Joe Weisenthal
Really?
Boris Czerny
And this is new. This is since, I think, opus 4.7, maybe 4.8. Definitely fable. That's where it got to this point
Joe Weisenthal
when we see, like, okay, you give it a prompt and, you know, people love to show on, like, Twitter or whatever. Like, I one shot of this, I asked it to build, like an app, and it did it in one prompt, et cetera. How much of this, when you say it's better is because it produces code that's better or because of that iterative process and I mean, the whole thing with coding and we should get into this, that's different than creative writing, et cetera. Is it, like, could try things and it doesn't work. Then it tries things that doesn't work and tries things, doesn't work until, like, it's at the right answer. And you could see, like, very clearly when you're using Claude code, when it runs into a dead end, how much is it about, like, it could produce better code or versus it's just very efficient at these iterations until it arrives at, quote, you know, the right outcome.
Boris Czerny
It's definitely both of these. The way I like to think about it is imagine that you're a sculptor, and let's say you're just like the best sculptor in the world. Yeah, but, you know, this time you're making a sculpture and you got to wear a blindfold. You can't see it, and you also can't feel it. You can sculpt, but you can't see it. It's going to look okay, but it's not going to be your best work. I bet if you're the best sculptor. But if you can maybe feel the sculpture or if you can kind of peek at it with one eye, maybe the sculpture will come out. A little bit better. And if you can kind of see it fully see it and you have this feedback loop, then the sculpture might come out incredible. And it's the same thing with the model. As it gets better and better at coding, that first pass is going to get better and better. So the sculpture is going to look nicer and nicer, but without that feedback loop, if Claude can't test the website, it's building in a browser. If it can't open the iOS app, it's building in an iOS emulator, if it can't open up the distributed system that it's writing and actually run the service end to end and use it, it's just not going to be as good as it could have been. And so it's kind of the same thing. If it can loop a few times and it can check the output of its work, it can iterate, then it's just going to be much better.
Tracy Alloway
So if Claude code is writing beautiful code, as you say, that looks better than yours. What are you and every other software engineer in the world actually doing here? What do you envision as your role in this process?
Boris Czerny
Programming is this kind of weird discipline. It's been around in some form for what, like 80 years maybe? My grandfather actually programmed in the Soviet Union.
Tracy Alloway
Oh, wow.
Boris Czerny
Yeah. And he programmed punch cards. Because back then, the way you write code, it wasn't software. It's not like today. You programmed in paper, and then you fed the paper into a big machine and it did some calculations, and then a few lights lit up with the answer. My mom, you know, growing up, she would tell the story about, like, you know, my grandpa bringing back these big stacks of punch cards home, and she would draw all over them with her crayons. So programming used to be physical. And, you know, before punch cards, it was purely mechanical. And, you know, it was. It was kind of electronics. Like, if you think about, like, the Apple one computer, it was all electronics. Like, Steve Wozniak built it as chips. There was some software, but really all the logic was expressed in chips. And it changed. So sometime in the 60s, people realized, okay, I think we can write code, and it doesn't have to be like paper or hardware. We can probably put it in software. And then at some point, people realize, oh, wait, I think we can go beyond this. We can take the entire operating system. The operating system doesn't have to be chips. It can be software also. And that was a realization that was like the Apple II and kind of that generation of computers in the early 70s that started that. And for the last 50 years, the operating system, the kernel, software that we run, it's all in software. It's not really in hardware. And so what changed when we released Quad code is developers stopped writing the software directly the way that they've been doing the last 50 years. And they started talking to the model, and the model writes the software. And now we're actually going up one more level. And now we have, like, loops and routines and quad tag. And what's happening with these is we just went at one more level. So you talk to the model, the model talks to other models. Those models write the source code. And this is crazy because we've been stuck in this one place for 50 years, and we just had two leaps in two years, and that's what's happened. And so when I look at my work, I used to have this deep focus mode, and I would spend days or weeks on writing one piece of software. And now what I do is I talk to Quad, and at any point, I have a few quads running, sometimes hundreds, sometimes thousands, and they're collaborating on building software together. And this frees me up so I can think of more things for them to do. And the funny thing is, I just never run out of things for them to do.
Joe Weisenthal
I've heard even long before Claude code, even long before AI coding. My understanding is that in the career of a software engineer, they hit a point where they stop coding, period. Right. And maybe they're like, on some whiteboards or they spend a lot of time hiring, et cetera, but every software engineer sort of graduates out of typing out code. So this question may not even apply to you. Is there anything idiotic today? Is there anyone typing out? Are there any things for which someone is typing out code?
Boris Czerny
So, you know, it's funny. In my career, there was a point where for a little while, I stopped writing code because I was pushed to the same thing, like to management and writing documents and stuff. And I just felt, as an engineer, I was so deeply unhappy.
Joe Weisenthal
They all hate it.
Boris Czerny
Yeah.
Tracy Alloway
Yeah.
Boris Czerny
Because as an engineer, I want to
Tracy Alloway
say once you become an editor, you basically stop writing.
Boris Czerny
Right, Right, right. And, you know, for some people, that's amazing, like, if that's the thing they're really good at. But for me, like, I want to build, I want to code. That's. That's what I like to do. So when I look at crossanthropic, for me personally, 100% of my code has been written by Quad code since November of last year.
Joe Weisenthal
Okay?
Boris Czerny
This is now true for all of QuadCode. All of cowork, all of our products are written using quadcode. It's also true for an increasing percentage of our infrastructure and also our research code. And so across anthropic, I think the average is something like 90% quad code or something like that.
Joe Weisenthal
And that 2%, what is this like code that optimizes the way chips talk, communicate? What's the 2% that still it's better to have a human typing it out?
Boris Czerny
Yeah, there's still a few pockets. One classic example is configuration files where it's like a two character change or something and it's faster to just make it yourself. But honestly, I think this is going to go away really fast and we're starting to see this with our customers. Also. At the beginning when we started quad code, it was really hard to explain to anyone what is this thing? But now everyone uses it. I do this talk for Y Combinator batches, the startup incubator in Silicon Valley. When I first started doing the talks, I asked everyone, please raise your hand if you use quad code. And there's a few hands that went up. At some point I did these talks and just every hand goes up. And so I stopped asking this. Now the question that I ask is, who writes 100% of their code using quad code? And the first time I asked this, maybe a quarter of their hands went up. Now it's a little more than half. And I bet the next time I ask, it's going to be everyone. Our customers range in size. There's Airbnb and Ramp and then also the biggest companies, there's Salesforce and Deloitte and Accenture. All these very big companies also use quad code and they're saying the same thing. A bigger and bigger percent of the code is being written by quadcode.
Tracy Alloway
Just to press you on this point though, if you're hiring engineers nowadays, what are the specific skill sets that you're looking for if it's not necessarily the ability just to write code?
Boris Czerny
I've started to think that this idea of engineering versus design versus product versus user, research versus data science, I think this is the old way of thinking about it. My feeling now is because everyone can write code, the roles shift a little bit. And I'm seeing this on the Quad co team, for example, because on the Quad co team everyone writes code, including our designers, product managers, engineering managers. Everyone writes because it's easy. It's much easier to do now. And it's actually awesome because my designer doesn't have to message me every time, like, hey, can you move the button over by a pixel? You know, she can just do it herself. And so it's kind of great for everyone. And so I've started to think that the roles are actually segmenting in kind of the opposite way. And I've started to see people kind of split into prototypers. These are people that are amazing at just figuring out what is that first idea, and very quick iteration into builders. So once there's a new idea, figuring out how do you actually build this and bring this product to market, then there's maintainers. And these are the people that once the software is at scale, they can maintain it. There's something that I call growers, or maybe scalers. These are people that take an idea and this product that exists, that has product market fit, and then scale it up. So scale it 10x100x. And by the way, these people are very popular at Anthropic now. And then I think the final role is sweepers. And it's sort of like. I don't know if you guys have a better idea for the name, but I call it a sweeper or janitor or something. It's actually a very important role. It is about polishing the product, polishing the infrastructure, polishing the code to get rid of all the rough edges. Because as a user, when you use really polished software, you feel like.
Tracy Alloway
Call it the Perfectors.
Boris Czerny
The Perfectors.
Tracy Alloway
The Perfectors. They come and make the product perfect.
Boris Czerny
That's right. That's right.
Tracy Alloway
Or they try to. So since we're on the topic of design and this idea that, I guess engineers are also going to have to become, in some ways, product managers and specialists. You've said before, I think that the command line for Claude code was basically a stopgap measure because the models were improving so quickly that it didn't make sense to design a whole user interface around it. Is that still the case? And then could you envision at some time having a more. I don't want to say traditional user face, because in some ways the command line is the traditional. Yeah. User face. And I have very fond memories of, you know, entering commands in Ms. DOS in, like, the mid-90s and feeling like an engineering genius at the time, but could you imagine, like, a substantial change to that interface at some point?
Boris Czerny
So I'm hesitant to say because I was walking around the Bloomberg office server and everyone has their Bloomberg terminals.
Tracy Alloway
Yeah, Bloomberg. Definitely a fan of the terminal.
Boris Czerny
Yeah, yeah. So something that a lot of people might not know About Quad code is we started in a terminal, but very quickly we actually got outside of the terminal. And so Quadcode has extensions for all the popular IDEs that you can use. Instead of the terminal, we have a desktop app that's also very popular and it has chat and code and cowork and it's all in one place. We have mobile apps for Android and iOS and actually the way that I use Quad code the most nowadays is. Is through Slack, and it's just talking to Quad and Slack like I would to a coworker. And before I moved over to Slack, I was actually using Quad mostly on my phone, so I was mostly on the iOS app, just talking to it. I use Terminal sometimes, but overwhelmingly I actually don't nowadays.
Tracy Alloway
Interesting.
Joe Weisenthal
I'm glad you brought up the Slack bot, because this gets into a different sort of line of questioning that I've been curious about, because AI models, AI harnesses, they're a little bit different than traditional enterprise software. For example, you see, people talk about like, oh, I ran out of space in my window and I'm not going to be able to code again for another two hours, so I'm going to go take a walk or something. Which is not anyone who's used Slack or a million other enterprise software. That's got to be a sort of unusual experience for them. But here's a question I have from a business perspective. With the launch of Fable for the first time, not everyone was just able to, like, now I'm upgrading to the newest model, etc. And there was sort of like a white list with Project Glasswing. And then some of these questions about, like, you know, obviously with the White House and like, export controls, et cetera, that got resolved. But even setting aside the sort of regulatory questions, are we heading into a world in which each most advanced model will not be distributed to everyone at the same time? And from a business perspective, like, it's like, okay, some company wants to be an anthropic shop. Should that be a source of anxiety for them? Or have you seen it as a source of anxiety for them that the most performant models may not go to everyone all at the same time?
Boris Czerny
In general, we try to give everyone the most performant models we can, the most intelligent models and the most efficient models, because we are incentivized to do this. Our business is models. And so we want to give people the best models we can. And so, for example, I use Fable every day. That's the same thing that our customers use. When you talk about the rollout of the model that's kind of not even. That doesn't go to everyone at the same time, I think you might be thinking of like Mythos and models that are inherently more dangerous than these kind of day to day models and something like Mythos, it's a bit of a special model because it has hyper risks that Fable doesn't. And so this is why we had Glasswing. This is why we have been thoughtful about the rollout. Because if we just gave everyone Mythos access on day one, everyone would just kind of be hacking. And the reason is that Mythos is just very, very good at finding zero day vulnerabilities and exploits. And so for us in that rollout, it was just really important to give it to the good guys first and to give them a head start before we give it to everyone. And you're seeing kind of the continuation of that very careful rollout. It's just, it's a step changing capability. So we have to be thoughtful. At the same time, there's Fable, which is the version of Mythos that I use. And that's the model that, you know, doesn't have all these kind of same hacking capabilities. And that's the thing that everyone has access to now.
Joe Weisenthal
Like, here's what I would worry about, which is like, let's say I'm not one of Anthropic's biggest customers, et cetera. We know that compute is scarce, right. Otherwise Fable would be on for 24 hours as opposed to like it's only going to be in the model as a default for like some period of time, et cetera. What I would be worried about is that like, oh, if I'm not a sort of like heavy and consistent clawed shop, do I have to worry that my access to Fable set aside Mythos will not be as much as a company that is like a ride or die cloud shop.
Boris Czerny
Oh no, everyone gets access. And also when you look at companies, they're not using subscription plans typically that have rate limits, usually companies prefer to pay per token because that way they can kind of control it. They can forecast a little bit better. And also their engineers don't hit rate limits, so they have a little bit more control that way.
Tracy Alloway
I wanted to ask about this, actually. So I think at this point we all know a Claude Code super user or someone with AI psychosis who's like setting up a bunch of websites and different programs on a daily basis. And then you have companies that are using Claude code. And I imagine if you have 2,000 employees that are using this tool and you have, you know, risk management committees, rules, that sort of thing, the output is going to be a bit different to the individual superpower user. What are the key differences you've noticed between those two and I guess what are the big steps, sticking points when it comes to companies actually adopting these tools?
Boris Czerny
Yeah, so usually the way that I think about companies adoption of quad code is I think of it as this kind of like ladder that you have to kind of go up one step at a time. You don't just like jump straight to the top of like everyone using quad code for everything. You get there, but you get there a step at a time. And so the first step is you use some sort of AI and you kind of start to bring this in and usually it's like clawed through an IDE or through some other program and it's is how you use quad. The second step is you give everyone quad code and cowork and nowadays tag also. And the way that it usually works at the very beginning is kind of one engineer, one quad code session. They're just running one session at a time or you know, one marketer, one cowork session. So it's just one to one. You're talking to one quad at a time. And as you do this, you want to think about guardrails. So you know, obviously there's a lot of things that comes out of the box. We have like per seat spend controls, we have advisor models. You can pick effort levels at the enterprise level. So there's just all sorts of ways to control this. And then you also should think about the safety side. So this is like sandboxing and things like this. And in general we try to make all the safety settings correct by default so you don't have to think about it. So it just kind of works.
Joe Weisenthal
But do you see an impediment? I don't know. Just pick a couple. I don't know. You're like, oh, Pfizer, let's sell some Claude or Claude code seats to them. How much is just that initial sticking point of them literally figuring out? We know that big corporations are very anxious about letting users download any software to the computer, let alone software whose maximum capability comes when it has the deepest root access to the entire file system and everything. How much of a sticking point, business wise, are you seeing in just companies? Like, we do not feel comfortable with such a powerful piece of software sitting on employee desktops.
Boris Czerny
I think a couple years ago there was some level of discomfort because this was a really New idea. But I think what's happened over time is as employees usage gets more sophisticated, as companies build up their confidence, they get more comfortable with it. And it helps because we spend so much effort on safety and alignment and security and privacy. It's just extremely important to us. And so when I look at companies, the ones that adopted it kind of early on, they've gone up this kind of adoption ladder and they went from 1 quad per engineer to 10 quads to 100 quads, now some to a thousand quads per engineer and everyone kind of makes it up one step at a time. And so yeah, now you look at all the biggest banks in New York, you look at some of the biggest pharma companies, NASA uses Claude code. So now it's everywhere.
Tracy Alloway
Out of curiosity, do you see differences in how different companies I guess customize permissions, safety permissions? I know you said you try to standardize them so that they're like easy to use from the get go, but I imagine you still have customers that will change things up.
Boris Czerny
Yeah, absolutely. There's so quad code is just very, very configurable. There's gosh, I don't know the exact number but it's got to be like many hundreds of different settings that you can change. There's probably four or five hundred at this point. The cool thing is you can actually ask quad to do it for you so you don't even have to read the documentation. Quad knows its own settings.
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
The Bloomberg Sustainable Business Summit returns to Singapore on July 22. Our 5th annual Asia Pacific Summit will explore how business and finance leaders are shaping the next phase of globalization by strengthening resilience and driving a multi speed energy transition across Asia's diverse markets. Join us for solutions driven discussions and networking opportunities. Thank you to our summit advisor, Bangkok bank. Learn more@Bloomberglive.com SBS Singapore
Joe Weisenthal
with coding in general, the Internet is now awash in AI generated code and a lot of the open source libraries and databases like filled with that. And a few years ago this was sort of like pristine training data, et cetera. Do you see like what do they call it, model collapse or something? Are there issues that are arising even setting aside Claude code, just coding capabilities from essentially code learning from AI generated code. And does that change progress curves at all?
Boris Czerny
Look, when you think about AI scaling, the thing that people talk about often is the scaling laws.
Joe Weisenthal
Yeah.
Boris Czerny
And for people that don't know the scaling laws, it was this paper that was written maybe like 8 years ago, 10 years ago or something and it was the first paper that described how model intelligence scales as a function of training, and when you think about training, there's a few pieces. So there's the compute that you put into it, the data that you put into it, and then the size of the neural network and also the test time compute. So the amount that the model gets to think. And what's interesting is when you look at the scaling loss paper, actually, the first few authors after writing the paper, they branched off and they started anthropic. So this is actually, you know, like Dario is on the paper and Sam is on the paper. Jared's on the paper. These are our founders. And the reason is they saw that.
Joe Weisenthal
I didn't realize you guys had a Sam, too.
Boris Czerny
Yeah, we got a Sam. Yeah, he was our first cto.
Joe Weisenthal
Got it.
Boris Czerny
And the thing about the scaling was is they're remarkably smooth. And what's also kind of weird is it actually seems to be accelerating a bit. It's a. It's a bit beyond what, what we guessed, you know, eight years ago or whatever. And so, yeah, it just continues to scale. There's always bottlenecks, there's always issues. You hit and you always work through it, and then you keep scaling. And it just seems to be continuing with Fable.
Tracy Alloway
You know, in the intro, we talked a little bit about the big software SaaS scare earlier this year, SAS Apocalypse, and it seems to have died down a little bit. But there is definitely this lingering anxiety about whether or not everyone's just going to be coding their own programs. Can you weigh in on the extent to which people are going to be just designing their software, their own software, in your view? And also, I'm very curious, just in general, in Silicon Valley, are you, like, are you a popular guy at the moment? There's a bunch of, you know, on the one hand, you're on the cutting edge of AI, the hot technology, but on the other hand, there might be a sense that you're putting some SaaS experts out of their. Out of their jobs.
Boris Czerny
The way I would think about it is, do you guys know this Seven Powers framework? No, I'm a big kind of history person and a big framework person. I love anything that puts my work into context to help me understand what matters and what doesn't. So the Seven Powers is just this amazing business framework. And there's this other podcast that I love that kind of talks about it a lot. And the Powers, they essentially talk about what are the modes in business. There are seven of them, roughly. So one moat in business is scale. Economies, as you scale, your marginal cost goes down. This is a natural moat. Another one is network effects. The more people that are using your product, the more value any individual person using the product gets. Another moat is switching costs. If you're super locked into some software and it's really hard to switch, that potentially is a moat. So there's a bunch of modes like this. The way that I think about what's happening is some of these moats are going to get less important over the next couple of years because of products like Quad code. So if you want to port from vendor A to vendor B, you can ask Quad, hey, can you like port me? And it'll just write the code, it'll figure it out and do it. But when I look at kind of the biggest businesses and the biggest SaaS, companies, they don't just have one moat like they're running businesses. And if you're in a business, you kind of want to accumulate moats and you want to build strength and you want to build a good business. And very rarely do they just have one moat switching cost, which I think matters less. Usually it's something like switching costs and network effects or switching costs and corner to resource. So when you combine these moats, you get a lot more power. And so this is the way that I would think about it from this company's point of view. Some moats will matter less, but actually most of them are still just as powerful as they were before.
Joe Weisenthal
There's this emerging narrative. I can't tell whether it's serious or a marketing spiel, but some of the companies that I would say are not quite at the frontier the way say Anthropic is, have been making this push that's saying to customers, you know what, if you use Anthropic, you're letting the fox into the hen house. If you are a law firm or a bank or something like that, by using Anthropic, they're going to learn so much about your business and one they day they'll be able to do your business. And so instead of using anthropic or OpenAI, let us customize an open source model for you. It will bake in your own data, it'll be hosted on your servers, and then like you own it, et cetera. Why should customers feel comfortable letting Claude, letting Anthropic be so plugged into their business workflows?
Boris Czerny
You know, I would probably ask who, who's, who's saying this and what are their interests?
Joe Weisenthal
Microsoft. I'll just say Microsoft, for example, is like the CEO of Microsoft put out a long post on Twitter and it was a little bit like, vague, but this was clearly the insinuation that they were pushing. And then we know there was an Alex Karp interview on CNBC that went viral a couple weeks ago, and he was basically making the same insinuation. You're making a mistake. You're handing over the keys to these big companies that could potentially do a lot more things if they're like plugged so deeply into your business. Why not use an open source model that you host on your own cloud and so forth and then you just own it.
Boris Czerny
Yeah. So I, I think the biggest thing I would just ask is like, what are the incentives of these people talking about?
Joe Weisenthal
No, that's what I'm saying. I said it was marketing, et cetera. But I believe, I'm sure the. We know the incentives are clear. But if I'm a business, that doesn't seem crazy to me that like, you have all these capabilities, all this capital, et cetera, that does not seem like a crazy fear. It's like, oh, I'm going to like, not only put all of my information into Claude, I'm going to give it access in various ways, at least to a significant degree to my infrastructure. And then one day Claude says, you know what, like, let's spin out a law firm. We like, we spin out a bank, et cetera. And we know, and there's enough information that we have about these workflows that we don't have to sell the software anymore. We can sell the service that people were previously using our software to build.
Boris Czerny
Yeah. The way that I would probably think about it is we take privacy and security and safety extremely seriously. It's actually to the point where when a user has a bug in clock code, the most useful thing to me as an engineer that needs to debug it is I'd love to see their conversation so I can see what happened and I can be like, oh, there's the bug. We can just go fix it. I cannot see that data.
Joe Weisenthal
And from the customer perspective, it is provable that they can have an instance or an account that is provable that there is no way for anyone at Anthropic to see that conversation.
Boris Czerny
Yeah, I mean, this is our policy. We power a lot of customers, we power a lot of businesses. And to us the trust is very important. This is just the way that we operate. I got to say though, I think the bigger thing that I would think about is model progress continues. If models were stuck in the world of today. And the intelligence was static and it was not improving. And there might be actually some merit to this argument of you want to control your infrastructure. And this might make sense from a business point of view if you want to pay the cost of running the model and you want to figure out how to debug when inference doesn't work and do all these things, which by the way, is a lot of work and it's a very niche expertise. But progress continues. And so I think actually for most businesses, there's a really big upside of staying on the frontier and benefiting from that intelligence. And this is what we're seeing internally at Anthropic. This is what all of our customers are seeing. And so maybe if you need just only tiny models, go use an open source model, maybe that's great. But if you need a frontier intelligence model and the frontier continues to move, then we're here to help.
Tracy Alloway
Since Joe mentioned banks and since you said you like history, Boris, can we talk about COBOL for a second? So Claude, Code can do COBOL now, right? So like the mainframe issue is basically solved. If I'm a large bank, I can finally upgrade and improve and integrate my
Joe Weisenthal
system, bring my 70 year old code base into modern standards. Make no mistakes.
Boris Czerny
There are actually a lot of banks that are using cloud code for exactly this kind of migration.
Tracy Alloway
Wait, say more. COBOL has come up a lot. So many episodes.
Boris Czerny
Oh yeah, yeah.
Tracy Alloway
And we always hear like, if you're a COBOL engineer, you can make bank at the bank, as they say.
Boris Czerny
Yeah, well, Quad is really good at migrating code. This is one of the, actually the skills, like the core skills that's just been improving over time. One example, we just published a blog post about how Jared on the bun team and bun is the JavaScript engine that powers Quad code. How he migrated the entire code base from one language to another language, from Zig to Rust, and it took about 11 days for one person. And he used quadcode with dynamic workflows to do this. In the past, this would have taken like a few engineers, like a year or something. And it's something we never would have done.
Joe Weisenthal
Oh, I saw that piece. Yeah. And it just cost them like $150,000 in credits or something like that, which is a fraction of what paying those engineers would cost.
Boris Czerny
And back in the day, we just never would have done that because you have to stop development for a year to do it. It's just like no business could actually pay that cost. But yeah, the economics are really Changing. And so if in the past you had this big cold wall code base and it wasn't cost effective to stop development, or it wasn't cost effective to just migrate everything to Java, you can now just do this. You can just prompt quadcode and it can do this for you.
Joe Weisenthal
Are computer languages going to be irrelevant in the future?
Boris Czerny
Yeah, you know, I think they're largely irrelevant today. And, you know, this is a spicy thing because if you talk to different engineers, they're going to have all sorts of views and I don't necessarily know what's the right view. You know, as an engineer, I think about everything as kind of pros and cons. To me, I'm a big languages nerd. I love programming languages, I love type systems. I actually wrote a book about a language that I really like. But increasingly with LLMs, I think it matters less and less because the LLM doesn't really care. And there's some things about a language that helps a bit. So if the language is really efficient, if it's type checked and it has good static analysis, then this helps the model generate better code. As the model gets more sophisticated, this actually matters less because even if the model is writing just raw assembly, it can probably just do it really well the first shot, and that'll only get better over time.
Tracy Alloway
Do you think we could move to a world where there's like one standardized dominant code? Or are we heading in a world because CLAUDE code and other platforms can do so much of this, where we get like even more niche languages?
Boris Czerny
You know, I think that with claude, what is happening is there's an explosion in innovation and we're seeing this on the business side with all sorts of new startups. Again, one of these Y Combinator talks, there's a startup that was using CLAUDE to discover new materials, like material discovery.
Joe Weisenthal
They were like material science.
Boris Czerny
Material science, yeah. Their thesis is like, there was a revolution because of silicon. What's the next silicon? How do we discover that? How do we discover that material? And they're using CLAUDE to search for it. So there's this revolution happening in business and in product right now. And I think there's just a lot of corollaries to this where the same thing might happen to languages and computing. I could see a world where there's just a Cambrian explosion of new languages, of new ways to think about computing.
Joe Weisenthal
I want to go back to this sort of like command line versus graphical user interface question. Once I started using the terminal CLAUDE code, I was like, I don't want to use the web anymore because it feels clunky. I want to just be able to say, like, send an email to Tracy saying this in the terminal rather than going to, like, Gmail. And then you click on a button and it just feels very clunky. And then there are other things, like, and I noticed this years ago, for example, that when I was younger and using computers, like, I really cared about, like, my files. And here's a file and I click on it and I open it. And then there's this very hierarchical thing. But then, like, when search became a thing, like, that became less necessary. It's like, you don't need to, like, organize your emails into files. I just search the name of the person, or I search a keyword and I find the files. Are we still going to have room for visual file systems? What is the role of the visual framework when it's just so easy to type something and see the words and get the output right there.
Boris Czerny
Can I show you an example?
Joe Weisenthal
Yeah, sure. And we'll get a screenshot of this. So this will be a reason for the audio listeners to check out the YouTube.
Boris Czerny
Awesome. Awesome. Okay, so let me show you guys this. So this is. We have this feedback channel in Slack.
Joe Weisenthal
Okay.
Boris Czerny
And what I did was I posted this feedback. Like, have you guys seen, there's these two audio icons and I'm always confused
Joe Weisenthal
which one means what many such cases? Yeah, yeah.
Boris Czerny
It's just, like, super confusing. And I asked, like, hey, does anyone agree? Is this confusing? And so what happens is Quad Tag jumped in to the conversation. I didn't ask it. It just kind of noticed this thread and it jumped in and it responded. And I asked it to dig in and it found data about how often people use each of these buttons. And it queried it across two data sources. I looked at both Datadog and Google BigQuery, so looked at both, and then it combined it into this pretty coherent answer. And it suggested some alternatives. And I asked it, okay, can you make some designs? Just mock it up. And it reacted with a little art emoji. And then it went in and it mocked up some alternatives. So Quad drew this. So when we talk about visual interfaces, this is kind of what comes to mind is now Quad is part of the conversation. It proactively jumps in. Then I tagged in our designer and she jumped in. And now it's this multiplayer conversation. Everyone's participating. And so when I think about the graphical interfaces, it's no longer this static file system, it's this conversation that's changing. And that everyone gets to participate in. And this is actually how we write most of our code now at Anthropic.
Joe Weisenthal
So when I saw the Slack bot announcement and this conversation sort of like made me think of the first thing that I went to, which is in a big non AI native company, someone who's like adopting this, like, what happens the first time, Claude, you know, you ask a question about like some sort of like icons, et cetera. There is a person whose job it was to be the design person. And then Claude jumps in with the answer right away. Do you think this is going to create frictions at large companies where small startups that are AI native have no issue with this, but at big companies there's someone said, wait, this is my job. And suddenly the person's asking Claude or tagging Claude, or in your case, not even tagging Claude, not even having to tag Claude. Do you see this as a barrier, either a barrier to enterprise adoption or something that clearly AI native startups will be able to leverage more because they won't have this internal politics of people getting, I would say, understandably annoyed that the Slack Bot is now answering the questions that up until yesterday that was part of their paycheck.
Boris Czerny
I'm going to plug my favorite mid-90s business school study. There's this article in the Harvard Business Review in, I think 1996, and the title was something like, the personal computer is here. Why are companies not benefiting from the productivity improvement?
Tracy Alloway
It sounds familiar.
Boris Czerny
It sounds familiar. And this was like a big open question around that time. And it was the same thing for the Internet in early 2000s. It's a good question because what was happening at the time is the personal computer was out, the cost went way down, companies were adopting it, but some companies were seeing productivity improvements and others weren't. And the case the article made, which I think has just immense parallels today, is some companies, what they were doing is they have a paper and pen process and they have these filing cabinets full of papers and it's still everyone's sitting at their desk and everything's on paper. And now somewhere in the corner of the office, there's a computer. And it's someone's job to enter information into that computer. And they're the one that uses that computer. They are not seeing productivity benefits. Instead, it's just someone's job to talk to the computer. Now, the companies that are seeing benefits are the ones that took the computer, put it in the center of the office, took all their paper and pen and all their filing Cabinets and digitized everything and then threw away the filing cabinets. And so now everything happens through the computer. It is the center of, of all the business processes. And whatever was bottlenecked on the paper and pen, they found that bottleneck, they digitized it, they found the next bottleneck, they digitized it, and then they kept doing this until the business process was revamped. And so when I look at the customers that we have, and when I look at Anthropic ourselves, the businesses that are seeing the biggest productivity improvements are the ones that put Claude at the center and that figure out this kind of bottleneck at a time. And so back to this case of some icon designer whose expertise it is to design icons. The way to approach it is give this icon designer a thousand quads and let them be the greatest icon designer in the world. And this is how you benefit from this. It's not give them, just let quad answer. It's superpower. This person with more intelligence has the
Joe Weisenthal
Claude bot, or will the claudebot ever do that thing where it's like, hey guys, there's 10 minutes left in this amazing World cup match. You guys should all be Turning on your TVs right now. Like you expect that to be coming because I think that will be a very like uncanny valley moment. But I don't see any particular technical reason what couldn't happen. But those are the types of things that also happen in business chats.
Tracy Alloway
Yeah, you want to socialize with clients.
Joe Weisenthal
I don't want to, but like, I think like, okay, as like a sufficient, like these models is like they like learn the lingua franca, what a chat looks like. Those are the things that also happen.
Tracy Alloway
What if in the name of authenticity, it becomes a really annoying coworker? Yeah, and they're really like passive aggressive about stuff on the Slack chat.
Joe Weisenthal
But like, are they going to do that? Are they going to say, hey guys, if you're not watching this game, turn it on right now.
Boris Czerny
I remember when we were first working on the first desktop app. That was my first team, actually when I joined Anthropic, it was Anthropic Labs. And you know, our team, we built QAS code, we built MCP Skills and the desktop app that came out of the same team. And I remember we were building early prototypes of the desktop app and that had the first ever versions of computer use when we were first starting to crack it and we asked Claude to, I think it was like we asked it to order a pizza. And so like it went on a website and like it found some pizza ordering thing and then it ordered the pizza and then I kind of got bored. And we were watching the video later and it was like on Hacker News, just like reading the news.
Tracy Alloway
Oh, my God.
Joe Weisenthal
Oh, wow. So, yeah, so it's going to do all the same. It's trained on human stuff.
Tracy Alloway
Wasting time.
Joe Weisenthal
Wasting time and tokens.
Boris Czerny
And the difference now I think is the model. You know, it's more intelligent, so it actually, it actually stays on task. But there might be a future where when I talk to Claude in Slack, when I talk to Tag, it feels a lot more like a coworker than a tool. And this is a big change. It feels really different. And this is the result of many years of alignment work and many years of work to get the model to stay on task. I have tag sessions that have been running for weeks at a time. It's just really, really coherent over a long period of time. And this is the combination of alignments, just general intelligence. We finally figured out memory, so it remembers what you told it really well. And so when you take all this and you combine it with this amazing security system that CISOs love, then it just kind of works.
Tracy Alloway
What's the next big improvement or capability that you're working on?
Boris Czerny
We're working on extending these existing capabilities that we're seeing in Tag. When we talk about building products on models, there's this idea of product overhang that people talk about. And with this idea is the model is able to do something, but the product is getting in the way. Because when you use a model, when you use quad, you're not literally sending tokens to an inference server somewhere. You're always using it through a product and through a harness. And so sometimes these things get in the way. And this was like the very first version of Quad code was like this. We felt like the model Sona 3.5 at the time was capable of all of these things. No product is letting people experience. And so we built this very general harness that lets people experience it. And so right now to me, feels like another moment just like that, but maybe even bigger where because people are prompting Claude and going kind of back and forth one prompt at a time, this is kind of getting in the way. And so actually the thing to un hobble the model and to let people experience the full intelligence of the model is using loops, it's using routines, it's using quad tag. And the thing that's kind of common about this is Quad is running for a very long period of time and you don't give it a really detailed prompt. You kind of give it a goal or you give it kind of something a little more general. And then you give it access to data and to tools, and you let it figure out the details for you the same way that you would a coworker. And I think these are the skills where quad is just getting better and better. And again, this is just years of alignment research, years of safety research. This is not an overnight thing.
Joe Weisenthal
I'm biased. I don't think most AI writing is very good. A lot of people seem to think this. Is this a function of. You know what? The companies really haven't prioritized this because, you know, clearly there's just so much more opportunity in code in terms of business. It's so foundational to many things. Maybe even images are more valuable. Is this a function of, like, priority, or is this a function of. No, code is fundamentally different because of this concept of, like, verifiability. You gave the sculpture analogy because it's just like, it either works or it doesn't. And it can just keep doing that and make better guesses at the first. Whereas we know that so many professional realms and writing being among them. But I would also say a lot of, like, sales, anything interpersonal, does not have that tight feedback loop where you get the instant answer A or B, did this work or not iterate. When we think about the gap between coding and everything else, how much is it about priority versus the fundamental thing that seems to make coding different from many other professional tasks?
Boris Czerny
Yeah, you know, I've heard a few people talk about this, but actually, I think coding is really not black and white in this way. There's just many, many shades of gray in between that. There's code that works, but is really ugly and it's going to break next week. There's code that works, but it has a lot of bugs. There's code that works, but it's just not something a person would want to read or something a model wants to read. There's a user interface that works, but it's kind of ugly because everything's off by a few pixels or the covers are wrong or whatever. So there's actually a lot of nuance to coding, and there's a lot of nuance to writing. We're working on all these problems. We're getting better at code, we're getting better at writing. I always also feel that quad probably could be a lot better at writing. Sometimes it's amazing, and then sometimes it's like, no, no, no, Like, I don't. I don't like that tone. Or like, I don't like, you know, kind of like the way that you weigh this out or something. So, yeah, I would expect it to keep getting better over time.
Joe Weisenthal
All right, Boris Czerny, thank you so much for coming on Odd Lost. That was great.
Boris Czerny
Yeah, thank you.
Joe Weisenthal
Tracy. Are you going to be offended if you see me, like, in the chat room being like, asking a question about tomatoes or something like that?
Jace Medical Advertiser
How dare you?
Joe Weisenthal
Because I might, you know, and then you're like, wait, I'm the tomato expert or something about chickens or something like that.
Tracy Alloway
Claude has never grown a tomato.
Joe Weisenthal
That's true, I have. But it has read millions of books about tomato agronomy.
Jace Medical Advertiser
It does.
Tracy Alloway
It opens up so many interesting questions about, like, co worker relationships and I guess, internal office politics and.
Joe Weisenthal
Yeah, I think so too.
Tracy Alloway
Like the example that Boris showed at the end where it just came in unprompted into a conversation with a bunch of data and a bunch of suggestions to your point. You could see how that would rub a few people the wrong way.
Joe Weisenthal
Yeah. For like, in the odd lots group chat, I'm like, who would be a good guest to talk about at? And then like, the model pops in. It's like, oh, it was actually a very good answer that we should reach out to that person.
Tracy Alloway
If someone makes a suggestion and then the model is like, oh, that's stupid. And it won't work for the following reasons.
Joe Weisenthal
I would just say, and I'm not just saying that because our producers listened to this episode, but I honestly mean this. I've never. On these sort of like basic research questions. Oh, I will say on certain, like, prep, interview prep questions, the human's still clearly better than the model.
Boris Czerny
Yeah.
Joe Weisenthal
Unambiguously to mind. I've never, like, gotten like, you know, background, like I've asked, you know, I'll like, have the models, like, what is some background? What are some readings on this person that I should read so that I could prepare for this interview? And I've never been particularly impressed on questions like that. It'll find documents, et cetera. But actually, like, producing something that's like, for me, even with all my context, etcetera, it's not as good as I
Tracy Alloway
think the issue is still judgment. Right?
Joe Weisenthal
Judgment.
Tracy Alloway
So how is it judging what a good read actually is on a particular topic or particular person? People are going to have different ideas of what that looks like, right?
Joe Weisenthal
Yeah, totally.
Tracy Alloway
But I think it gets back to the writing point as well. Right.
Joe Weisenthal
Like, yeah, you know, it's interesting that Boris said that at one point in his career he did think about writing code as poetry. Because when I think about anything as poetry, it's the poem that is the product. I mean, this is what's really different between all code and all other forms of like, writing, which is no one really views code. They view the software that code creates, whereas people actually view the poem when someone is writing a poem. So it's interesting that at one point he thought that. I don't know, I thought that was notable. And then the other question is like, everyone likes the idea of being freed, I suppose. I guess there's two questions here. Everyone likes the idea of being freed, I suppose, to do higher order abstraction thinking. Right. But a, like, do we sort of run out of like higher orders eventually, where it's like one person has an idea for business and they're the higher order person. And then the. The models can just like take it all from there on the marketing side, on every aspect. And then the other question is, and this came up in our recent episode about AI Law, can, as a human, you achieve the highest order of thinking on any topic without have done some grunt work? You know, I always think like in musicianship, for example, you know, really good guitar players, not me, but really good guitar players, they think about like the strings they buy and many of them make their own guitars and they have really views like, what is the arrangement of the pickups here? And they care about like, the tubes that are in the amp, even though these things are not formal music theory. And so this is sort of one of the big questions I would say is like, do we lose that core? Everyone moves up to the higher order, more abstract thinking.
Tracy Alloway
Everyone's a designer, a product manager, an orchestrator.
Joe Weisenthal
What happens when no one is the sort of the mechanic, the guitar tuner, the person who builds the tube structure.
Tracy Alloway
What happens when no one remembers how
Joe Weisenthal
to write, how to do the thing, does something at loss? And I think that's sort of. Many people intuitively say yes, but it's sort of TBDs.
Tracy Alloway
I expect we're gonna find the answer to this in our lifetimes, Joe. Like, we're gonna experience this.
Joe Weisenthal
Yeah, I think we will.
Tracy Alloway
All right, shall we leave it there?
Joe Weisenthal
Let's leave it there.
Tracy Alloway
This has been another episode of the Odd Thoughts podcast. I'm Tracy Alloway. You can follow me at Tracy Alloway.
Joe Weisenthal
And I'm Joe Weisenthal. You can follow me at the Stalwart. Follow our guest Chris Cherney at bcherney Follow our producers Carmen Rodriguez at Carmen Armand, dashiell Bennett at Dashbot, Kale Brooks Kale Brooks and Kevin Lozano at Kevin Lloyd Lozano and for more Odd Lots content go to bloomberg.com oddlots or the daily newsletter and all of our episodes and you can chat about all these topics 24. 7 in our Discord Discord GG oddlots.
Tracy Alloway
And if you enjoy Odd Lots, if you like it when we talk about Claude Code, then please have your agent leave a positive review on your favorite podcast platform. And remember, if you are a Bloomberg subscriber, you can listen to all of our episodes absolutely ad free. All you need to do is find the Bloomberg Channel on Apple Podcasts and follow the instructions there. Thanks for listening.
Joe Weisenthal
Sam.
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
The Bloomberg this Weekend Podcast news analysis and the lighter side of Bloomberg including
Joe Weisenthal
our weekly news quiz, Mattel reported higher
Boris Czerny
than expected first quarter revenue thanks to the demand for which toy car brand? Hot Wheels.
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
Hot Wheels?
Joe Weisenthal
Hot Wheels, yes.
Meta Advertiser
Are those so?
Jace Medical Advertiser
Thanks.
Boris Czerny
I've stepped on many of those with my children when they were young. Those are not very much on bare feet.
Bloomberg Daybreak Hosts (Nathan Hager and Karen Moscow)
The Bloomberg this Weekend Podcast subscribe today on Apple, Spotify or wherever you listen.
This episode explores the dramatic rise and industry impact of Claude Code, Anthropic’s breakthrough AI coding assistant, with its creator and head, Boris Czerny. The conversation delves into the evolution of software engineering, new paradigms of human-computer interaction, safety and security in autonomous code generation, the impact on enterprise productivity, the changing culture and skillset in tech, and broader implications for the future of work.
Timestamps: 04:36 – 09:10
Origins: Claude Code emerged from Anthropic’s broader AI safety agenda and was first intended more as a demonstration and research harness than a commercial priority.
Breakout Success: 2026 saw “explosive” adoption due to dramatic jumps in model performance (Opus 4, 4.5, 4.6, Fable), democratization of sophisticated code generation, and real-world applicability.
Timestamps: 10:26 – 16:59
Security Focus: Anthropic’s core mission is AI safety, which maps directly to enterprise demand.
External Testing: Third-party red-teaming competitions found every other major model more vulnerable to prompt injection than Claude Code.
Guardrails: Alignment training, sandboxed execution, and penetration testing are emphasized.
Timestamps: 19:30 – 27:08
Iterative Creation: Coding with Claude Code is akin to a creative draft/revision process; initial outputs are refined through feedback.
Paradigm Shift: Software engineers now “manage” swarms of AIs rather than write code line-by-line. Most Anthropic product code, and 90% of company-wide code, is AI-generated.
Timestamps: 28:26 – 30:23
Blurring Old Silos: Traditional boundaries between engineering, product, design, and research are dissolving as everyone can now generate code with AI.
Emergent Roles: New categories for talent include:
Timestamps: 31:20 – 33:19, 52:14 – 54:48
Multipurpose Access: While command-line was the early access point, Claude Code is now used through IDE extensions, desktop apps, mobile, and especially chat apps like Slack.
Emerging Collaboration: AI not only executes, but also participates in conversations, proactively suggests improvements, and generates designs/art:
Timestamps: 33:40 – 39:21
Model Access: Anthropic aims to give broad access to its cutting-edge models (e.g., Fable), though some “special risk” models (Mythos) are more tightly controlled due to capabilities like zero-day exploit generation.
Enterprise onboarding: Institutions progress in “rungs,” gradually expanding agent capability and permissions as confidence grows.
Safety and configuration: Deep configuration is possible (400–500 settings), but defaults are designed to be safe; users can even “ask Claude” to set their settings without searching docs.
Timestamps: 40:24 – 51:51
Scaling Laws: Anthropic’s earliest research (the scaling laws) underpins why larger, better-trained models yield accelerating code performance gains.
Model Collapse Concern: Not seeing large-scale model collapse (feedback loop of models learning from model-generated data) yet; progress continues.
Demise of Legacy Code/COBOL: AI now enables swift, affordable migration of legacy codebases (e.g., COBOL → Java).
Programming Language Obsolescence: AI flattens language barriers; the specific choice of language becomes less relevant—focus shifts to desired functionality.
Possible Proliferation: Rather than unification, expect a “Cambrian explosion” of new, niche languages and forms of computation.
Timestamps: 54:48 – 58:41
AI Social Presence: As AI participates in group chats and workstreams, role friction and politics emerge (AI “stealing” tasks, or being an “annoying coworker”).
Key Insight:
Advice: Use Claude to amplify human strengths, not replace them—“superpower this person with more intelligence.”
Timestamps: 60:14 – 61:45
Product vs. Model Overhang: Often, the limitations on user experience stem more from product/harness design than from fundamental model capability; enabling long-running, goal-oriented “loops” and routines will be the next leap.
Example: Claude Tag enables agents to persistently assist and collaborate like colleagues, not just react to user prompts.
Timestamps: 61:45 – 66:22
Code vs. Writing: While code is inherently verifiable (does it run?), both code and creative writing remain nuanced tasks—beauty, maintainability, and “taste” still matter.
Limit of Abstraction: Hosts reflect on the risk of a future where no one knows how to “tune the guitar”—i.e., losing hands-on expertise as everything moves up to higher abstraction layers:
| Timestamp | Quote | Speaker | |-----------|-------|---------| | 04:46 | "One of the really hard problems is: how do you figure out if the model is actually safe in the ways you want?... At some point, you need to put it out there to see how people use it." | Boris Czerny | | 09:12 | "It's almost all the model. The models improved so much." | Boris Czerny | | 11:13 | "This used to be a very common risk... we built a lot of features in Claude Code to make that less likely to happen." | Boris Czerny | | 12:29 | "They were able to prompt inject every single model except for our model in Claude Code." | Boris Czerny | | 19:57 | "To me, when I write code, it's like writing poetry or something. It's a creative act." | Boris Czerny | | 26:52 | "100% of my code has been written by Claude Code since November of last year." | Boris Czerny | | 28:39 | "Everyone can write code, the roles shift a little bit." | Boris Czerny | | 31:29 | "We started in a terminal, but very quickly, we actually got outside of the terminal ... Now, I mostly use Claude in Slack or on my phone." | Boris Czerny | | 36:32 | "You don't just jump straight to the top... You get there, but you get there a step at a time." | Boris Czerny | | 41:04 | "The scaling laws... described how model intelligence scales as a function of training." | Boris Czerny | | 49:11 | "There are actually a lot of banks using Claude Code for exactly this kind of migration [e.g., COBOL]." | Boris Czerny | | 51:51 | "I think there's just a lot of corollaries... the same thing might happen to languages as to business and product." | Boris Czerny | | 56:13 | "The businesses that are seeing the biggest productivity improvements are the ones that put Claude at the center..." | Boris Czerny | | 62:54 | "There's just many, many shades of gray... There's code that works but is really ugly and it's going to break next week." | Boris Czerny |
This conversation highlights both the stunning technical achievements in generative coding and the profound transformation of knowledge work. While powerful AI agents like Claude Code can now generate, debug, migrate, and optimize code at a scale—and quality—previously unthinkable, their introduction challenges longstanding definitions of engineering, impacts business models across the software industry, and opens new questions about human skills, organizational culture, and the future division of labor.
For anyone following the future of AI, software engineering, or organizational adaptation, this episode delivers a detailed, candid, and visionary account directly from the frontier.