Welcome to Changelog and friends, a weekly talk show about Notepad++. Thanks to our partners at Fly.io, the public cloud built for developers and AI agents who like to ship. We love Fly. You might too. Learn more at Fly.io. Okay, let's talk.
Well, friends, I'm here with Damien Schengelman, VP of R&D at Auth0, where he leads the team exploring the future of AI and identity. So cool. So Damien, everyone is building for the direction of Gen AI, artificial intelligence, agents, agentic. What is Auth0 doing to make that future possible? So everyone's building Gen AI apps, Gen AI agents. That's a fact. It's not something that might happen. It's going to happen. And when it does happen, when you are building these things and you need to get them into production, you need security. You need the right guardrails. And identity, essentially authentication, authorization, is a big part of those guardrails. What we're doing at Auth0...
is using our 10 plus years of identity developer tooling to make it simple for developers, whether they're working at a Fortune 500 company or working just at a startup that right now came out like Combinator, to build these things with SDKs, great documentation, API-first types of products, and our typical Auth0 DNA. Friends, it's not if, it's when. It's coming soon. If you're already building for this stuff, then you know. Go to Auth0.com slash AI. Get started and learn more about Auth4GenAI at Auth0.com slash AI. Again, that's Auth0.com slash AI.
So the 2025 Stack Overflow Developer Survey Report is out. It's out there, Adam. You know, surveys like this are very much needed, I think. It grounds us in our crazy cycles, right? It does. This is their 15th year doing it, which seems like a lot. Wow. Maybe it took them a while to get this prominent. Maybe if you do something 15 years in a row, you must be doing something right. They say that. Or else you'd stop. They do say that. Or you're crazy. Or you're crazy. Or you're crazy, you know?
So this year, I mean, it's gotten pretty big. It says that they've received over 49,000 responses, which you know how much they wanted to get to 50,000. Couldn't quite get there. So that 49,000 is cool. But, you know, as the people running that survey, they much would have rather said 50,000. Yeah, no one will say 49,000. Unless it's a price. You're trying to like do the 49,500 versus 50,000. Oh, trying to round you up? Yeah, you know, that's when it makes sense. But when your stats and audience size, you want big. That's right.
No, 1999 here. You know, this is a 49,000 plus from 177 countries across 62 questions focused on 314 different technologies. And as is obligatory, a brand new focus on, can you guess it? Maybe it's a, I don't know. Surprise. What is it? AI agents. Oh my gosh. Of course. LLMs and such like. Are they, I didn't see it in here yet, but did they talk about their downtrend?
As a result too, or is it, this is just a developer survey? Stack Overflow's downtrend? Yeah. I don't think they want to talk about that at all. No, I don't think so either, right? But it's real. In fact, they have an open tab because I was thinking about that. 49,000 responses. However, Stack Overflow itself is declining, as you said. Yeah. Here's a blog post from Eric Holscher, friend of the show, from Read the Docs, right? Eric Holscher, Read the Docs. Read the Docs. And Read the Docs, I believe. Read and Write. Read and Write the Docs. Someone's got to do both. Yeah. Why not? Eric's a fan of both. He's been on the pod a few times. Yeah. And here he is talking about Stack Overflow's decline. Of course, he's...
quoting our fellow friend of the show, Gergeo Rose, who I think was just analyzing somebody else's gist that they dumped. So this is like three layers of inception right here. But the chart is nice, showing monthly questions asked on Stack Overflow, dating back to 2010, pre-2010. And they peaked between 2014 to 2017 at about 200,000 questions asked per month or answered per month. Just questions per month. Whether or not you get the answer, I guess, depends. And then it's been a precipitous decline ever since. Most people blame ChatGPT, but if you look at this chart,
it was already on its way down prior to chat gbt launching in 2023 but since then it's gone like way down like 25 000 ish you know it begs the question so there's a place i mean prior to ai and prior to let's just say deep learning and you know data lakes with lots of knowledge toward in them uh i think asking a question to a community like this like stack overflows provided for many years has been very pertinent But what has been your personal experience with that user experience of the have a question, find a question, get the answer, apply the answer, move along with your life because you're a developer, you've got better things to do. What's been your experience with that, with them? With Stack Overflow? Yeah, like what's been your personal happiness level, I suppose, with the status quo user experience they offered? So I should say I've never been a user. Like, I don't think I have an account. I've never answered a question. I know that. Maybe that's not true. It's been a long time. Maybe I answered one way back. I do not believe I have an account. If I do, it would be news to me.
So I'm merely a person who lands there. I've heard a lot of the stories about the moderation on Stack Overflow and the complaints about people's questions being deleted. and some just draconian moderation around what is a good question, what's not, et cetera. And of course, I've also seen the gamification and how some people have rose in prominence from it. So there's also social benefit of using it over time. And so I've been along for the ride, but I haven't been a user. I've only been a question reader, answer reader. Yeah, I'm a taker. No wrong with that. I mean, when you're a mass appeal website like that, you have to have a large majority of takers, not givers. For sure. I'm with you. So you've been able to have a profile there. You've been able to gamify or gamify, however you want to pronounce that.
your involvement, whether it's an answerer or a questioner, I don't know how you would phrase those personas either, but very much so has been like this really kind of unique world. If you're a listener out there and you've been a gamified, enriched user of Stack Overflow and you love it, let us know. I'm curious what that's like or has been like, but to me, I've never been like, oh, I've got to go there and answer all the questions I know so that I can rise to prominence. I've never understood that specific user experience, but I think my experience with Stack Overflow has been generally, I would say on par. Sometimes find an answer, sometimes out of date. Sometimes you have some response to the bubble up as, hey, it's been a year or two. This has changed. This is the new way. So generally it's been, you know, the prompt before the prompt, so to speak. Right. Yeah, obviously I'm glad it exists. I wish it would continue to exist prominently. I do not know the details of the whatever moderation drama and, you know, there's backlash. Even from people who are like longtime contributors, I've seen them like leaving the platform and so they've got their problems.
Every website does. It's a difficult thing, moderation. And however, like most people, even as just a casual user, I'm not using the website anymore. Like I'm just not landing there. And so that's a problem. And in fact, Eric, in his post about this, says that he's a little bit worried about something like this happening to Read the Docs. Because obviously his livelihood and a lot of his life's work is with Read and Write the Docs. And it's a very similar situation, a Q&A site or documentation site.
Of course, the LLMs answering questions for us is the biggest reason probably for Stack Overflow's decline. And so he's hoping that doesn't happen to read the docs, but at least when he wrote this back in January, he said they haven't really seen a huge decrease in traffic. So it hasn't happened to them yet, but it is slightly different when you have official documentation for your Python library versus questions about how to use your Python library. It's a different beast altogether. I hope Stack Overflow does not continue to decline. I think it kind of needs to exist. I think the LLMs need it because it's a source of truth for them.
But the incentives, just like the rest of the web, the incentives to publish are just going away, right? Like, why would they do that if they're not going to get the traffic? Yeah, I mean, even the reason I mentioned the UX experience is the fact that you mentioned the decline was prior to really this uprise of AI and agents being a thing. Like, it was already in a downward trend. Based on, you know, Eric's blog post and Gary's illustration, of course, you know, it's already showcasing that there's an obvious spike up for COVID whenever that happened because everyone was trying to figure out everything, right? Yes. And so obviously there's a peak and unearned potentially peak in user experience or even just usage. It was already on its downward trend. So I just wonder, like, was it already, was it a systemic issue with how Stack Overflow works?
insofar as that you said it's needed, right? Like we need a source of truth. That's what docs present. That's what Stack Overload has presented in the past or even now is this version of what is true in terms of a question developer asks. Right. So back to the survey, they...
have the data, of course, but they also do some editorial, which is nice. And related to Stack Overflow's decline, on the homepage of the survey, you'll find kind of their editorial, the creators of the survey, meaning like they try to contextualize some stuff and make a few conclusions for the reader. In fact, there's probably 20 or 30 of them on the homepage that just randomly refresh or they switch orders, I just refresh the page. So they're not trying to make one more important than the other. But one of their takeaways from the survey is Stack Overflow is a destination developers visit frequently. I thought that one was funny because that one almost sounds like a self-serving.
selection from the data. Of course, they publish the data as well, and everyone can come to their own conclusions. But connecting the dots and trying to have takeaways is, of course, the interesting part. And many of us don't have time for that. In fact, if you don't have time for that to our listener, of course, we're here to even read you some of those connections. So there is a question about Stack Overflow, frequency of visiting Stack Overflow. And of course, on the homepage, they create these conclusions, and then you can drill down on the actual chart that that comes from. And they have a few questions like, how long have you had an account on Stack Overflow? And then frequency of visiting Stack Overflow.
And what's crazy is there's 45% of the people who answered this survey have had a Stack Overflow account for over 11 years. Wow. So that's like a very dedicated, longstanding group of folks, you know? Yeah. And a strong majority, 82% of respondents visit at least a few times per month with 25% visiting daily or more often. So it's declining, but I think in terms of a community, they're showing through this data. At least, of course, they're serving their own community. So that's...
inherently self-representative, I guess, people are using the site. It's just not the same numbers that were prior. 76% use the site for more than six years. So you mentioned 45% over 11 years. There's another stat, 76% having an account for six years or more, it says, or more. So maybe that's like six to 10, you know, something like that. That's a lot. I mean, that's, they're definitely in their echo chamber when it comes to the survey, right? Like this is not randos who don't know Stack Overflow. So this is very, this is going to be as truthful.
as it can be given the tenure of the account holders. When you got 76%, six years or more as an account holder, that's a lot. Here's a funny one. So in the data, they provide you the range of responses and then they also categorize that based on the people responding. And so in this case, they're categorizing it by age. And so you can look at all respondents and you can look at age respondents. And the youngest category is age 18 to 24. And in that category, the number of people who've been using the website for 15 plus years is two tenths, a fifth of a percent.
So what's 32578? That's how people took it. Times 0.002. 65.15, if I'm doing math right. So 65 people started using Stack Overflow somewhere between the age of three and nine. Wow. They would have to, right? Because they're age 18 to 24. Unless they're lying. Oh, they're just lying.
What's the other thing about surveys is people just like fill in random things. 65 people were, you said nine was the highest age or five or nine? It had to be three to nine because they're nine. Well, they've been using it for 15 years and they're age 18 to 24. So three on the low end and nine on the high end. So can you imagine some three-year-old stumbling across Stack Overflow and signing up? Oh, go ahead. How does this pacifier work? Okay. How do I get into this? Yeah. I mean, most of the question is probably about Roblox and stuff like that. Minecraft. That's true. That's true. Yeah. Wow.
Very interesting. So definitely some interesting stats coming from that. What about the, what I'm noticing as I go through the different age brackets is, is really, it's the older generation that has been using it for longer, obviously. So I think 35 to 64 is probably a range of the last 15 years. So if you were 35, 15 years ago, you were what, 20 years old? It's pretty common to pick up stack overflow at 20 whenever you're in your junior days or just getting developed. And that was, you know, 15 years ago, that was 2010, 2015, yeah, 2010.
So 2010 was a pretty popular year to use Tech Overflow, I think. All right. Well, I thought we would go through some of these conclusions and use those as launching pads to drill down. Was there anything that jumped out as you? I mean, we can go into the AI stuff. Obviously, some of our listeners would love that. Another ones are so sick of it. We could go into technologies. You're going to have AI in there as well. We could talk about remote work. We could talk about content creation. We could talk about all kinds of things. History. Yeah. I want to talk about YouTube, man. Can I talk about YouTube on this?
I'm trying to scroll it and keep my context. So forgive me if I get a little discombobulated. I'm looking at two in particular. And I'm thinking about the younger generation because we can obviously talk about AI, but I think that that's an obvious large category to talk about. But I think we're going to start to see how that is impacting younger developers, those who are coming into software development, whether they're the traditional engineer type or someone who's just thrown together something because they have to build a website for their business or whatever. I'm looking at this, the one that says younger developers want developer content with social or interactive formats.
It's a little self-serving here. We run a podcast, as you know, Jared. So, you know, we're on YouTube and stuff like that. So I'm thinking, where is the young model of who we want to reach and who we want to serve? Because we serve humans, not machines. We use machines to serve humans and solve problems. But I'm thinking, how are the younger generation going to be impacted by this major change? Thankfully, they still want good developer content. They're not just saying, hey, every LLM give me all the content only. They want that social nature and they want interactive formats. So that's one piece of this data puzzle.
And then the other one was the respondents learning to code using YouTube for community more than professional developers. So they're leaning on this scalable content, maybe even influencer, which I'm not really, we wouldn't consider ourselves influencers, although we may influence. We're not considering ourselves the stamp of approval influencer, but it is reassuring that the places that we're pouring our efforts into. is being looked at by the younger generation, the younger developers coming in, even though, you know, AI is coming and AI is here and is doing good stuff. Yeah. So there's two questions that speak to that. Like you said, the first one is how do you choose to find relevant developer content? And the Stack Overflow folks say, well, all age groups want lists and articles because everybody loves a good listicle. Younger developers show a significantly higher interest in more social and interactive formats. For example, 37% of 18 to 24 year olds want chat with people, not with GPT.
Well, that's a new, that's all the kids are saying now. ChatGPT is just chat now. I've learned. So ask chat. Yeah. Ask chat. That means chatGPT. Ask chat. That's what kids are saying. Yeah. Compared to only 20% of 55 to 64 year olds. Do you want chat with people, Adam? Do you want this? I mean, because you're, okay, you're not 55 to 64, but we're between these two groups, you and I. Yeah. And young people want chat with people and old people don't as much. You know, I don't know. I think.
I think with people is still a necessary component. I mean, that's obviously why we have Zulu. That's why we had Slack. That's why we went from Slack to Zulu because we really care about community. So I personally desire that. Now, am I trying to chat with people more than chat with GPT? I think it depends. I think I want to, I want to self-explore as much as possible and with little to no hallucinations. And I've learned to.
do chat, solo chat, let's just say with the model inside of ChatGPT or Claude or Grok or wherever I'm doing it. And I'll have a certain amount of happiness with that process. And then I have a prompt that is sort of canned. that I've learned to can't, essentially it's become repetitive. So I'm like, okay, I should probably store this so I can just like copy and paste this in the future. And it's this version of summarize what we've discussed here so I can have my XYZ agent review and verify what we've found. Cause I, I get to a session and I'm like, this is awesome conquering the world. Meanwhile, there's like four core hallucinations in there that just like destroy the model, you know? So getting at the with people parts, I want to, I want to explore self driven for a bit with less hallucinations as possible.
And then once I've gotten to a certain comfortability with what I'm trying to accomplish and my own mental model or new lexicon, I had to learn to do whatever. I will then, I would want to have this community of folks to pair with or spar with or ask questions. So I agree with that. I think I want to chat to a certain degree, get some self-assurance and then expose those ideas to real people to validate. Yes. Good path. No, not good path. Yeah. I think a mixture is for the win for sure. I think they serve different purposes. I certainly enjoy chatting with people generally more.
because I can't easily predict the responses. It seems to me like when I'm looking for advice on how to do something or a tool to do a thing, I'm perfectly fine with asking chat. But I don't find things there unless I'm looking for them. I think people are the best source of unsolicited recommendations. Because if you're excited about something, you're just going to find me and come and tell me, right?
And we see that all the time in our Zulip where it's like, this is cool. In fact, that's what I do. Most of my work is finding cool stuff and sharing with people, AKA ChangeLog News. So like that's unsolicited recommendations, right? Like, okay, you solicited it because you signed up for ChangeLog News. But if you're hanging out in Zulip and you're just part of our community, you may have not wanted to know there's this cool movie you should watch and someone's going to come and tell you. And that's irreplaceable, I think. I mean, you could be like, hey, every N hours, please send me a recommendation. Like you can do stupid stuff like that to imitate it.
When people find useful tools, useful lists, useful long form articles that really compel them, they'll share. And you can't, I think we need to chat with people for that. Do you remember, this is really going to date us, Jared, if you remember this. I know you do because we're old. Yes. Mahalo. I do. That was Jason Calacanis' thing, right? Yeah. It was like.
Was it the encyclopedia? It was essentially search power by humans. You ask it and this human goes find it for you. Right. The list of results wasn't necessarily algorithmically compounded and refined, etc. It was somebody, a real human with context. I think it doesn't scale, but the premise is good. And the fact that you've got humanity in this seemingly inhumane process. You search Google, get results. That's a machine. It's ranked by some sort of order you don't even have.
It's a black box, you know, how the results got there. Somebody could have paid, somebody could have paid an SEO engine, somebody could have like gamified the thing and to not earn the number one ranking or even the top 10 ranking. But then you go to Mahalo, which was this idea, okay, take the same kind of result, the same kind of search term or search query, and you put a human in the middle there, which says rather than return this algorithmic result list that is arbitrary and black box and controlled by the behemoth, let's put it in control of maybe Jared, a particular human, and their name is on the result. And so it's owned by a human. I like that idea. I think I want to see a resurgence of Mahalo in today's world, personally.
So here's a question. Why do you think it is that 18 to 24 year olds want to chat with people more than any other older age group? What is it about that group of folks? Loneliness. Yeah, I think it's a lonely world there. I think the more we're, I mean, this is really philosophical, but I think the more, well, this is 18, right? So these 18 year olds were probably not just introduced to their smartphone or to their smart tablet or whatever you want to describe it as. It's not a computer anymore, right? Like that's not a computer to people like us. They probably had something for many years. And so they've probably already been in this, this ice, this self-isolating.
uh, framework or decline where they're just like socializing less. And I, if I were 18 and 24, I want friends and I want friends. I don't want just money. I don't just want a job that fulfills me. I want the whole kit and caboodle. So to speak, I want to, uh, self-learn cause that's just my personal nature, but I want to socialize and I need to, I personally am the kind of person that needs a sounding board. I need my idea to be reflected off of somebody.
And you know this because we've been working for so long, how I operate. I need somebody to hear my idea. You don't even have to say yes, you like it or no, it's a bad. Like, don't just please just listen. Just listen. Right. And then I do desire feedback, but you don't have to. This is not a requirement I need as an individual. I need to tell another human about my crazy ideas just to see if there's any resonance. And if there is, I'm going to chase that dog.
If not, well, the idea dies in my brain. I move along. I keep doing my daily thing. You know, so I'm a person who needs other people. So I can empathize with these 18, 24 year olds that are in a world where they're more self-isolated than normal than we ever have in our history. Yeah, what's interesting is like the 25 to 54 year olds all want.
chat with a bot. And then the, the olds don't want that either. I think they're just grumpy. They don't want anything anymore. We're good. Like this is how you choose to find relevant developer content. So there's a context for this. It's not just like, do you like chat bots? It's like, do you like to find relevant developer content via an AI chat bot? And I think 55 to 64 year olds don't care too much about finding relevant developer content. At least I don't think I'm going to at that age. Um, but one thought I had, which I agree with the loneliness factor and what about novelty? So I feel like our age ish.
is more likely to become infatuated. And I guess I use that word from a lack of thinking of a better word with AI chatbots, because like we remember how bad it was. Remember the bots? I mean, maybe you didn't do this, but when I was a kid, we wanted to talk to a computer. Like we could never do that.
And if you found a chat bot that was anywhere near decent, I would just talk to that thing. Let's see if it can make, say this, say that, you know? And they were just like pre-programmed responses back then. It was all deterministic and they only had so many responses and you could, you know, they were terrible. They didn't pass the Turing test, that's for sure. And so like for most of our formative years and up, we've been desiring smart computers that can talk to us. And now we have that. And so we kind of want it more. Whereas these young bucks, they kind of grew up with that ability. I mean, it's gotten better over the last three or four years. It's gotten way better. But.
I don't know. Chatbots aren't all that novel when you've grown up in the smartphone era. You've had Siri your whole life. Yeah, the 18 to 24. If you just started recently, then you're still in that first five years of your journey, which is the fresh part. That's when you're learning all of your initial things to consider and concern about.
For the next 10 years. Yeah, I agree with that. I suppose. Not when this makes sense. I agree with that. Then when it comes to YouTube specifically, so back to the other question that's relevant to this YouTube topic. Is this the one you're looking at? Community platforms? It's a summarization of it. So the question in particular was, it's kind of hard to search, I think, was, let me scroll back. Respondents learning to code use YouTube for community more than professional developers. So they're using this, you know, algorithmic feed and search to find content versus, hey, Jared, you're a friend of mine. Where do you get your content? So they're going there.
That was the one. And then the other one was younger developers want developer content with social or interactive formats. Which is the one they were just looking at. That first one comes from this particular question. When you click the link, it goes to here. Gotcha. And the question was, which community platforms have you utilized considerably or consistently in the past year? And which would you like to use next year? Select all that apply. And that's where they're drawing this from. And so again, broken out at this time, not by age, but by professional learning, professionals that use AI and learners that use AI and write-ins. Oh, you could write in.
Did anybody write in changelon? It's almost non-existent, really. Mastodon, Lobsters, Matrix, Lemmy, Tiscor's, Mastodon's on her twice. Yep. These are all right-ends, Fediverse. Lobsters on her twice, Matrix on her twice, Lemmy's on her twice. Fediverse is obviously the undercurrent. It's all of those things. Right. So these are the CD underground where you get 0.02% of right-ends. But back to, like, the major platforms. And so, of course, it's a Stack Overflow survey. Stack Overflow's number one. But specifically, YouTube is up high for all developers, and especially for learning to code people. It's number two at 70%. So 70% of people learning to code will go to YouTube.
versus 60% of professional developers will use YouTube. And that tracks with me. I think that younger generation, of course, will more likely be learning the code if there are people who are older and still learning, like they're transitioning or switching careers. But most learning the code are in that 18 to 30 age demo. And again, like YouTube is a primary form of learning for these people. It just become...
a thing you do right yeah whereas our age isn't up like you we started with blogs and forums and documentation and so and and many times for me youtube is just like way too slow like i do not want to watch a video that's been dragged out to 10 minutes on purpose because 10 minutes is the perfect length of a video but really the content should be 90 seconds in order to get one thing out of it that i'm looking for or to learn something new I'm less likely to do that than I am a blog post that I can scan quickly and look at some pictures and then decide if I want to dive deeper. Not saying I don't do that with YouTube. I'm just less likely to. But I think that calculus has flipped as you go down the 80 brackets. Thankfully. I mean, I'm surprised. Not really, but kind of surprised Stack Overflow is so high. I don't know if the... Maybe because of the echo chamber, it makes sense for it to be so high. Sure. I think they bust out the echo chamber. It's going to be drastically lower than that. I am happy. I mean, it's really wild to see GitHub and YouTube compete.
Such a uniquely different platform. Yeah, I wouldn't even put those in the same category. No, but they compete. I guess they're both social. So there you go. Right. I mean, where else can you go in the world where you can self-publish for the most part without any real censorship? I mean, there's obviously copyright. There is some censorship. There is definitely, I would say, socially acceptable censorship.
some socially unacceptable censorship when it comes around politics we're not talking about politics generally in this podcast and generally around software development generally i mean it becomes political at some point as code yeah i think most coding channels don't have any issue with that kind of stuff yeah yes i mean for the most part you have an unfettered ability to publish yes video you know as well as you want to or as poor as you want to and so i think with that kind of platform it makes sense to me to see that be so high and thankfully chaptering so for me i'm i'm with you in the way you responded except for if I find a 10 minute video and it doesn't have chapters, I'm bailing. Sure. If it does have chapters. And I think that, and I don't know how to describe this litmus test I go through, but for some reason, there's this way to discern as a human, whether something is good or bad or for me or against me. So in that reptilian brain version of Adam, when he's watching YouTube videos, he's thinking about that. Chapter is bad. Yeah. So chapters are a must for me. And if, if it's a 10 minute video and I think, well, this probably took about two or three minutes to explain, I'll look for the chapter, the chapter that go past the intro or the who I am and why I do what I want. I appreciate all that.
i'm a diehard fan i want to hear that's how i became a fan of techno tim you know timothy stewart he's a friend of ours now yeah i was a watcher like everybody else but then i became a friend i said hey let's talk about a podcast let's be friends we're friends now i will still watch his stuff and i'll go past the preamble and he's cool with that why because we're friends i don't need the i'm tim or techno tim this is where i came from this is my context no just take me right to the true naz don't fail how do i configure it scenario and thankfully he's of the chapter mindset where he chapters so i'm like youtube must have chapters if there are any length of video whatsoever for me to get my attention unless it's like Golf content. I'll watch that. I'll watch that. 45 minutes straight. No problem. I mean, I waste a lot of time when they're watching golf content. Especially if you need a power nap. So speaking of chapters, we got some props, dude. We got some props in Denver from a listener who attended the live show for our chapters, which was nice because, you know, we do those with love. We do those because we're now chapter snobs.
But we don't always know if other people are, we know that some people like them. We've heard some things, but it's always nice to have reinforcement learning of, hey, I love your guys' chapters. They're so on point. He's like, he turns his nose up at people that don't have them on their podcast now, now that he's learned, you know, the better way. And him and I had some camaraderie around that. So I can't remember his name right now. He was the fellow who gave us a hiking recommendation. I can picture your face. Jim? Was it Jim? No, it wasn't Jim. Okay. Maybe it was. I don't know. We met a lot of people. Here's a couple of shout outs. Names I do remember. So at the meetup on Friday night.
There were three, I think, randos that came. And very cool. We say that love, right? Can you explain what the randos are love just for those who are not getting that insider joke? First of all, randos is part of one of our Change Login Friends theme songs, Adam and Jared and some of the rando, because we usually have a third or sometimes a fourth, although today was just the two of us. And so that got worked into a BMC song that we play sometimes on our show.
And then we also invited a bunch of Denver locals to the show, people who aren't necessarily listeners. And so some of them came, some of them didn't. It's not easy to get outside your comfort zone and go to a meetup of a bunch of software podcasters on a Friday night, knowing nobody. Like they didn't even know the show, some of these guys, until like the day of. We didn't have signage. We were like, just show up. We had nothing. We told people. Hopefully find us. He said, if you can't find us, just start asking people if they listen to the ChangeLog podcast. It's not really helpful advice. And yet they did. Like that was very cool. It takes guts. I'll shout out to Aaron, Randy, and Pedro.
And I think Trevor, well, he might be a listener. I think Trevor's a listener. Those of you aren't even listeners. Maybe they are now. But they just came out and hung out and they came to the show. I thought that was pretty cool. It takes us to do that. And so we appreciate it. I think they had fun. So I think it was worth the discomfort. Yeah. Yeah, I agree with that.
Names from Friday night, I don't remember any of them. So good job for you. Remember Randy, Aaron, and Pedro? Probably, but not by name. I'm so sorry. No offense, obviously. That's why there's two of us. It's easy for me to get overwhelmed in public-facing scenarios because I feel so much pressure to give my full love, I would say. I'm a giver, you know? It takes a lot out of me. I'm not an extrovert. I'm an introvert that gets depleted through social interaction, not invigorated. I will say, though, I was riding a high, so there's a part of that that's not true. I do get fueled, but I also get equally depleted.
Well, friends, I'm here with a brand new friend of mine, Kyle Galbraith, co-founder and CEO of depot.dev. Your builds don't have to be slow, you know that, right? Build faster, waste less time, accelerate doctor image builds, get up action builds, and so much more. So Kyle, we're in the hallway at our favorite tech conference, and we're talking. How do you describe depot to me?
And Depot's a build acceleration platform. The reason we went and built it is because we got so fed up and annoyed with slow builds for Docker image builds, GitHub Action Runners. And so we're relentlessly focused on accelerating builds. Today, we can make a container image build up to 40 times faster. We can make a GitHub Action Runner up to 10 times faster. We just rolled out Depot Cache. We essentially bring all of the cache architecture that backs both GitHub Actions and our container image build product. And we open it up to other build tools like Bazel and Turbo Repo, SC Cache, Radle, things like that. So now we're starting to accelerate more generic types of builds and make those three to five times faster as well. And so in simple terms, the way you can think about Depot
is it's a build acceleration platform to save you hundreds of hours of build time per week, no matter whether that's build time that happens locally, that's build time that happens in a CI environment. We fundamentally believe that the future we want to build is a future where builds are effectively near instant, no matter what the build is. We want to get there by effectively rethinking what a build is and turn this paradigm on its head and say, hey, a build can actually be fast and consistently fast all the time if we build out the compute and the services around that build to actually make it fast and prioritize performance as a top-level entity rather than an afterthought. Yes. OK, friends, save your time, get faster builds with Depot, Docker builds, faster get up action runners and distributed remote caching for Bazel, Go, Gradle, Turbo Repo and more. Depot is on a mission to give you back your dev time and help you get faster build times with a one line code change. Learn more at Depot.dev. Get started with a seven day free trial. No credit card required. Again, Depot.dev. Well, let's change our focus to some technology here. Still avoiding the topic. And let's talk Python. So one of the things I had is this admired and desired question.
where they asked people about certain tags, meaning like stack overflow tags, so technologies usually, or concepts represented by a tag, that the respondents desired or admired. And the distinction, I have to go read it again because I didn't totally, it's like admired, okay, I'll read their words. To better gauge hype versus reality, we create a visualization that shows the distance between the proportion of respondents who want to use a technology that's desired. So you desire to use it. And the proportion of users that have used the same technology in the past year and want to continue using it, that's admired. Did you track that? I'm tracking it. So I can be like desired Rust, but I've never really used it, so I can't admire it because that would require use. That's how they're separating the hype cycle. Okay. It's connection to the hype, essentially. Yeah. It's making hype real. Yeah, exactly. And from that said, I want to talk about UV. UV is a Python package manager built in Rust, and it's the most admired.
Stack overflow tag this year. UV. Have you heard of UV, Adam? I have not heard of UV. Okay. In this context. No. Yes. You know, ultraviolet. Yes. All right. So.
I haven't used UV, so I guess I desire it. We do desire it. We think the way you install Python packages is weird. Exactly. We know that. Yeah. So this is why I'm excited because this has been a longstanding bugaboo, you know, for the Python community. It's like, and for the community to have to use Python because they're trying to do other stuff. And Python is so prevalent, right? It's like package management is weird. Requirements.txt, et cetera. Like the weirdness of that. Pip and the other stuff. I made a whole show with my friend Brett Cannon just like telling us how to do it right because it's weird. And UV is a relatively new technology. That's a better Python package manager.
by Charlie Marsh. Charlie Marsh, a developer who's building Astral, which is high-performance tools for Python, in Rust, of which UV is one. And he's one, oh, see what I did there, the hearts of many Stack Overflow respondents and just developers in general. People really love UV. It's solving their problem. And did you know this, Adam? Charlie will be on the podcast in September. So he's coming up. He's going to be joining us. I didn't know that. Yeah, so there's a teaser in there. I'm excited about that.
But yeah, 74%, the most admired. I mean, he's beating out large language models. He's beating out Tailwind. He's beating out Delphi. Yeah. Wow, well, a lot of people probably don't know what Delphi is. He's beating out Polars. I don't even know what Polars is. Even Olama. He's beating them all, man. Charlie Marsh and UV winning. Winning. So there's obviously the context of UV, but I think just this spectrum of...
desire and admire. That's a really interesting measure because that's hype and hype and reality, right? Hype versus reality. That essentially stands for my brain. Yeah, because desired is kind of the hype and admired means like, no, you're actually using it. You still like it, right? Yeah, you block the hype and you tried it and you're using it. You're like, okay, this is actually, this was what they said it would be. And I agree. I'm gonna keep using this thing. So going back to your desire for Stack Overflow to remain, this is the reason why I would want it to remain. I don't know where we can get this data. Otherwise, maybe the LLMs will expose this to us.
And maybe with a much larger and maybe potentially more accurate data set. But this kind of range here alone from the desired admired is cool. It is cool. Yeah, I mean, this is signal versus noise is what we try to produce since our inception, which was open source is moving fast. There's so much happening out there. What's worth your attention has always been our thesis of content. And I like this. Obviously, thank you for getting him on and September like this stuff because we get to examine, you know, this desire versus admire scenario and what exactly is happening there. But it's a cool measure. It is a very cool measure.
And it seems like UV itself has grown as a way of solving the Python problem. Python continues to grow. So in the programming, scripting, and markup languages section, Python capturing almost 58% of all respondents using it behind only SQL, HTML, which is, of course, yeah, databases, and then the web. So HTML, CSS. And number two is 62%. And of course, JavaScript, which has eaten the world and continues to, is used by 66% of respondents. I assume that includes TypeScript.
Since I don't see TypeScript as its own category, good job, surveyors. Oh, is it? Is it 43%? Yeah, see, that's weird. It blended in. It did blend in. Well, if you add those two together, it's pretty tremendous. Yeah, it's huge. So if you had JavaScript and TypeScript, you got 100%. Now, some of those people are using TypeScript, but they also answered yes on JavaScript. Yeah. Because they know. I mean, everybody pretty much knows. Or somebody only entered JavaScript because they thought it meant both. Exactly. And then later they saw TypeScript and they're like, oh, I should mark that one too.
someone needs to fix this bug they need to be like make a category called like typescript not javascript or i don't know javascript not typescript or i don't know anyways so you know that separation yeah so python though saw a seven percent point increase over 2024 to 2025 that's that's a lot that's a pretty big increase especially for a language that's been around for like 30 years right scroll down to the number of people who submitted to this one i can't see it in my view okay so 31 700 responded to this question which is 64% of the total respondents of the whole survey. You know, I don't know about you, but I feel like the web is kind of default. We should keep measuring it, of course, but I'm not surprised it's up there at the top because what else do you choose? And there is no other choice besides HTML, CSS, and obviously JavaScript. So I feel like those are naturally going to be at the top. So Python kind of is the true number one, aside from SQL, which is more and more understanding of databases, which totally makes sense as we move into...
the next era of of all the things databases have always been there but they've been super prominent as companies open source etc for the last decade but python has been steadily growing year after year and i think that that trend is actually shows up in another question about web frameworks and technologies because on that one we have um no js at number one with 48.7 react number two 44.7 then jquery number three hello jquery Hello, darkness, my old friend. But the interesting rise here is FastAPI, which is a Python-based web framework, has had a five-point increase over the last year. So this is a significant shift up for FastAPI, which I had previously not heard of until maybe like six months ago. And that's because people are building more Python stuff with APIs and MCP and that kind of thing. Right, they're not having to worry about the interface. The interface is somewhere else. It's the conduit of the data that they're trying to engineer around. Yeah. So Python continues to grow despite being dominant. Pretty cool.
Pretty accomplished. What else? What else is interesting here? Do we broach the AI tooling topic or do we just continue to avoid it for now? I just live in the world, man. I just do what I got to do. If I have to talk about it, I do. If I don't, I don't. I'm cool with it. Let's start with an anecdote because I feel like we've been very bullish of late. Maybe because I have been more bullish of late than I was. I've had the ability to also be bullish because I've already been bullish. I can pile on. Yes. And I've been singing Claude Codes praises quite a bit.
And here's a story. So I think it was last show after we quit recording with Nick Neesey. We had just talked for a long time about... are my new cloud code habit and how much nick is using it etc etc ultra think if you recall that conversation i tried that recently did it work i mean i got a result i was tagged with it i want to think about ultra think exclamation point had something to do with it i don't know though so after that conversation we're hanging out with nick in the post show and we're talking about cpu.fm coming soon we now have a design we haven't been completely dragging our feet just sort of dragging our feet but we're making progress and we're telling nick that it's time for me to take the design which is in figma and put it into our Rails application so we can get this sucker out there. And I said, Nick, I don't want to write any code. Remember this, Adam? I think I told you guys. How can I do this without writing a single line of code? I was very hyped. And Nick said, well, there's a Figma MCP server. And so you turn that on and you point cloud code at your design file or your project. And then you tell it to turn that into a web page. Well, that's what I did this morning. I turned it on, only it wouldn't turn on because I needed to first upgrade our plan because Figma needs to make money. And so we went from...
starter free to pro 20 bucks a month for me 20 bucks a month for you spoiler we'll be turning this off soon yeah one month trial i hate those annual plans i know they get you because like 16 and you're like i don't want to spend 900 right now so i went with the monthly 20 bucks a month i had to turn us both on because we still we both actively use it and that allowed me to get inside of figma and turn on the mcp server this is my first mcp server people so here's my experience And I went to Cloud Code and I said, hey, can you use the Figma MCP server? And Cloud was like, no, I don't know how to do that. And so I taught it how to do that. And then I said, basically that. Take this design and put it into this Rails index with Tailwind. And the first thing I said is I can't do that because it requires way too many tokens. And so instead of reading the entire, because the whole webpage is one Figma project, I pointed at the entire thing at first. And I said, instead of that, I'm going to take a picture of it. And then I'll ingest the picture.
and then i'll reproduce the picture and i said okay fine good for you go do it go do it so however you do what you do do it it goes away probably takes like 45 seconds maybe a minute i don't know yeah and it writes a new rails view and all the css or the tailwind classes or whatever whatever whatever and like triumphantly declare success now he says reload that page and see what you think it was complete dog trash dude it was like a child it was like a you take like a picasso because it's a high fidelity comp you've seen it like we've seen it like this is a very nice website it's like taking a child and saying hey can you reproduce that picasso for me you know in the next 45 seconds and then they draw stick figures and stuff and like present to you and it's your kid so you have to be nice and be like oh it looks good such a great effort this is so bad dude it was so bad yes i was so disappointed and then he's like well okay at least it had the structure though like it had the sections It was like the content of the sections was really bad. So I'm like, okay, that's a start. How about now? And maybe it's because it took a picture. So I said, okay, there it is. Now let's focus in on like the hero section. Now we just limited the scope and I went and selected that in Figma. So it uses like the currently selected object or whatever. I said, now that we have the framework, I want you to focus on the hero section. Don't take a picture. Like actually use what Figma gives you.
and just reproduce that pixel for pixel. I can't remember when I said something like that, like make it look exactly like the Figma thing. And it went away and it did its thing and it had checked, you know, a checklist and it checked everything off and it declared victory. Like, go check it out. It was like lipstick on dog trash, dude. It was just terrible. So I'm disappointed. And I'm like, dang, I'm going to have to code this thing, aren't I? Oh my gosh. So that leads us to SEC overflow conclusion. 66% of developers are frustrated with AI solutions that are almost right.
they're almost right yeah but that makes them wrong can we dig into the yes we can some some details there well not the question your experience oh my experience yeah of course i want to go to the graph yeah sure go ahead ask away probably okay so i'm unfamiliar with this so did it let you are you able to say using tailwind or using you know class-based utilities i already had tailwind set up in the rails app so all i had to do was like use it and so yes i said using tailwind which it did like if you go look at the html it has all the tailwind classes But where it really falls down is like it's not like we have like the CPU logo, you know And it's not gonna go like take that asset out of Figma and put it into a webpage in any sort of way which is what I'm going to do. Like, that's what you're going to do, right? Like you're going to say, okay, here's a logo. However, what's the best way to get it in? No, it just like reproduces it in HTML with like, it's like a circle. It's a CPU. It's like literally a circle, like a red circle or blue. Could you have been said for assets like that, don't use that. Just put a standard known size for a future SVG logo replacement. Like, could you have said, give me the framework, the bones, and I'll fill it in with the good stuff. I probably could. And there is a blog post out on Anthropix site, like how best to use this thing, or maybe not on Anthropix, on Figma's website.
about how best to use it. And I think, yeah, I mean, I'm not reading that. I'm not reading that. I don't really, I don't have the patience. I'm going my own, man. I got this. I'm frustrated that I'm moving on. Like I'm back where I was with Gemini when it wrote that crappy function, when I was like, no, this function sucks. And that's why I'm like, this front end sucks. Now I got to decide, I'm going to rip it all out and start fresh or I'm going to use like at least the skeleton it has in place. I don't know. I stopped right there because we need to record this. So I stopped working on it, but it brought me back to earth a little bit from where I was, which was cloud nine because cloud code had impressed me so many times. But when it comes to this, I mean, this is for me going to be the,
bomb diggity is like figma design to html like to like pixel perfect yeah responsive etc etc like optimized that's gonna save people so much time and money like i will love that i was very hopeful that this would work i'm also not willing to like continue to try it though you know and maybe that's me i'm just frustrated and going back to my old ways on this particular i'm waiting i'll try it again later but the stuff that you're saying, like, could you tell to do this, that or the other thing? Probably. But I just don't think I have the patience for that. Cause what if it doesn't work? And now I've just wasted more time. Like my early indicator is it's not going to get to the fidelity that we want. And there's no, there that like, it's not going to cross the chasm with current tools. So yeah, I think for like a random landing page that you want to get, I mean, maybe that's even a bad example. Like where, yeah, you want to, you want something with good bones. Now what you can do, it is cool. Cause you can like, it's plugged into it now. So you can say like,
and I haven't tried this yet, but they tell me you can say this, like take all of the colors out of that Figma file and like use those whenever you're doing any sort of component creation or something. Like you can have it use the colors, maybe like copy gradients or the exact radius for rounded recs and stuff or for rounded corners. And that's cool. It's like a little bit of a shim, but it's not going to just take a Figma design and turn it into a web page, which the world wants. The world wants that feature. What is V.0 doing then with Vercel's thing? How is that? I mean, is it focused on components versus bigger picture?
Is that why you think it's maybe more used and maybe more popular? Cause it's like getting to a component result versus a full on painting, you know, make the tree nicer, not make the whole painting nicer. Yeah. Maybe they also, and I don't know, V zero personally, like Bob Roshto, by the way, that's a good, that's very happy. I should have said happy little tree. Yeah. I want to give you the shout out of the AK reference acknowledged. I think a lot of those are using that one component library that Shaw CDN or Shadi. I don't know what it's called. It's the worst name ever. You know what I'm talking about? No, is it called Shadi? No, Shadi would be cool. It's like Shaw CDN or.
i'm sorry i was just saying like calling shorty but like the slang version shawty it's your birthday uh this one dcn shad cn what what do people call this thing anyways this is a very popular thing it's by versell i think it's not by versell i should say that differently i think versell is hired the person that built this i think it's named after the person so the person's name is shaw dcn or shad cn and they built this component library my assumption is chinese that's all the cn maybe maybe Just a guess. Or it's a CDN. Very popular, 91,000 stars on GitHub. And so a lot of these coded from scratch, five coding tools like V0 are just using this and they're all components, like you said. And so they can just use this and it will look like this. And for your startup's, you know, first version or whatever, it's good enough. But they're not going to take an existing design and build it out. Unless that design is like wireframes. They're not going to take something that like a designer did and turn that into a webpage. That's like still a world of front-enders, you know? Right. Yeah.
So that's where I thought maybe that's where my question came from was if you're using Tailwind, Tailwind has a lot of really well-known components out there. My assumption is that a lot of the, you know, wrapping divs you got to do in the various utility classes you got to use to get to these layouts is pretty well known. And so I thought, well, it would be smarter to think like that, but clearly it's not because I mean. What do we expect? We're expecting a machine to do both the thinking and the art in the same motion. I think even as a human, I have a hard time doing that. Like, not that I'm better than these LLMs, but we're the original art creators. And I'm using me because I'm the best example I know of because I know me. It's hard to do both the thinking and the artistic side. So we have a left and right brain analogy for human beings. Like, well, I'm more right brain prone or left brain prone kind of thing. I think like that, like we're asking it to do potentially in the moment way too much, like technical code and visual design. It's a lot. Sort of. I think that.
So our designer, John Henry, if you'll read the Figma file, like that project, he has embedded a lot of the thinking into Figma. So there are layers, there's groupings, everything's logical. Like there's a structure in there that doesn't, that has been thought through. And so I feel like a machine could be able to do that. Could be like, okay, I'm going to take this and I'm not sure what it is over there in Figma. I think it's probably like all bunch of SVGs, but whatever there's this tree structure that I'm getting from the MCP server that has all the information in it somewhere. I'm going to translate that into HTML and CSS. I think we can get there without very much thinking. Now there are like...
on the specific like details, like how do I implement this picture? Should this be a PNG? Should it be SVG? Should it be a this, that, the other thing? Should I use some sort of CSS based animations and stuff? Like, yeah, that might be a step beyond, but I think a static representation of a Figma project in HTML, I think that's possible. And so that's always kind of what I was expecting. Now, maybe the skeleton and the bones are there and I'm just getting too stuck up on how they're too caught up. I don't feel very stuck up about this, but if you're caught up on how bad it looks and how like when it did try to do a thing, it's like.
You know, not good, dude. Not good. But when I go back and look at what it has done, which I haven't done, I just stopped. So we record. Maybe, like I said, maybe the bones are good. Maybe the structure is good. Maybe I can just build from there and not have to throw it all away. But just trying to provide, you know, some color around my previously always bullish last couple of weeks stance. AI tool frustrations. Yep. So people are kind of frustrated or frustrated. 66% quote AI solutions that are almost right, but are wrong. And then people are also frustrated with debugging AI generated code and saying it's more time consuming than.
Human generating code? Maybe not a great analogy, but this is what's coming to mind in the moment. Imagine you go and you rent a car, right? And you get there and you stay in line, you prepay, you consider the insurance, whatever you got to do. And you get in the car and it doesn't go. It's not a car. It's just looks like a car. It's not a car. Are you upset or excited? Right. Right. Like that's. Yeah. Almost the real thing is like worse than not even close because you are bamboozled, right? Bamboozled is very accurate. Yeah. That's not a car. This is, come on. It's a car. It's tracked in. Yeah.
You know? Yeah. Can I get the car, please? I want the actual website, not the thing that looks like a website, you know? Well, and even going back to the dinosaur era of this, which was PSD to HTML. Yeah. And for those who don't know what PSDs are, gosh, you live in a cool world. This is a good analogy, actually, though.
Because there was similar frustrations. I'm not sure if you're going there. Kind of. Yeah, go ahead. Yeah, finish your thought. Well, mostly there was this idea that I, as a designer, can do really cool stuff. I can make it very cool looking. But somebody else has got to turn this into a real website. And that's the hard part. And you kind of want this pixel perfection. And you almost amend it. And the website kind of sucks from a Braille standpoint when it comes to mobile or not mobile, which is a whole different era. Mobile first was post PSD to HTML. Right. And so you got all these anomalies along the way that could happen that sure, it looks like it, but it doesn't function the way it should.
yeah and even then you had more layers because you had the designer right pun is that a pun yeah nice designer with their photoshop layers that's right and they have pixel perfect perfection in their photoshop file right that's what they want on the web page and they know they're not going to get it but they hope they get close then you have the psd thtml shop or person a lot of times you'll just send this to a shop they'll send it back right there's even companies that would do this for you it's big business and you would spend a couple thousand dollars maybe i don't know yeah 1200 bucks i find an amount of money yeah And you'd send the PSD file out and you get back HTML and CSS. And that might look pretty stinking close to that file. Or maybe not, there'll be little things wrong. And then you have the developer who's implementing that into the site. And they go open those HTML files and it's like div chaos. And it's like incredibly brittle and hard to work with and terribly coded. Like somehow they managed to make it look almost like the website design, but it was like unusable trash when it came to the code quality.
and um or break constantly as you change it or anything with it you added too much text to your birth the whole website right they're like space stuff with like the ampersand nbsp the actual break tag yes lots of break tags lots of uh ampersand nbsbs with that non-breaking space that's right the invisible space like if i do seven of these i'll push that thing over far enough you know and you're like yeah but that was just once you could have put in css and it applied to every single element but instead you have seven nbsps 14 times yeah every time So those are the battle days. So I don't know. We're definitely better off than that. Are you saying frontenders have a future then for a little bit? For the next few years? Heyday? I think they're not going anywhere in the short term. Yeah. I think so. I do think just like everybody, their job will be evolving. But until you can hook these things up directly to Figma and say, codify this, and it just does. At that point, I think frontenders will be looking for something else to do with their time, which would be great because it's just a huge waste of time. I mean, it's not like a waste like you shouldn't.
be good at it. It's just like, it's an implementation detail of a bigger project that nobody really wants to have to do, you know? Like, if it were easy, nobody would be like, nah, I'm going to do this anyways. Right. They'd just be done. And there's lots of people trying to solve that problem, like the Nordcraft folks, like Figma themselves, like, what if we could just take the designer and developer and make them work together on the same thing so there is no translation step? Like, people are trying to solve that problem. Anyways, vibe coding not really a thing, Stack Overflow says. Most respondents are not vibe coding.
72.2%, in fact. It is burgeoning, and it's not their core audience. So of the folks who already identified who has accounts, right? Yes. And wasn't a large majority of the survey respondents had accounts? Yes. And most of them had accounts for 15, at least six years, right? A lot of them. So that makes sense to me that Vibe Coding's not represented. It's not true. It's true amongst that group, though. My favorite part about this one is you can answer no, which 72% did, and you can answer no, emphatically, which means like...
Not only am I not doing it, but I despise the fact that you asked me about this thing and 5% of people said no, emphatically. Of 26,000 people, that's a pretty huge percentage. I mean... Yeah. What's the number there? 26,500. Well, 1% would be 260, right? Yeah, do the math. 1,200 maybe? Uh, 13-ish. Yeah, almost 1,400. Yeah. That's rounded. That's... And so what was the question again they were saying no to? Vibe coding. Okay. Is Vibe coding something you do in your professional development work? Yeah, I'm not excited about Vibe coding personally, but I can see... See, there's so many...
like like all things exist on a spectrum right vibe coding is not somebody who doesn't know how to software to write software uh speaking into a microphone and getting software out that's one that's a the i would probably say the status quo what you think it is but it's also you can vibe code a certain feature a certain thing you know not have to be like a full-on green code base from zero to one it's more like well just add a feature i don't know i'm not i'm not personally vibe coding and you tried at least front end wise well i do vibe code scripts basically so i just tell cloud code to write a script that does a thing and as long as the script works i don't look at it right so that's and that's what i mean by the spectrum is like yeah does that are those folks just upset that you even ask them and they're saying no and then no emphatically yeah or is it a true no like is it it's a human existing the future obviously that that 1300 or so on the emphatically that makes a lot more sense it's more like i don't vibe code and i'm never gonna vibe code so leave me alone yeah that's how i read it at least all right well anything else that jumped out to you obviously there's way more on this survey we're not here to be comprehensive or anything
that we want to talk about before we uh say goodbye i think there's obvious ones around here as i scroll it uh look when they jump out like claude sonnet is the most admired ai model and i assume they're doing the desire versus admired spectrum there which is cool so we look at claude sonnet it was 33 desired desired and that's of 26 000 respondents and it was pretty high on the gosh it's really hard to navigate this going back and forth The admired is the red one. I had the data in front of me. I was scrolled perfectly and now I'm not, so I can't answer my question anymore. But it was pretty high. It was pretty high. There was a lot of folks liking the line. I would say make this thing easier to dig into and not lose your place and not have to, you know, open a new tab just to kind of keep the place. But that's me asking for a lot. Somebody, I probably vibe this randomly fast. It's pretty good. I mean, it's not perfect, but I think there was humanity involved. Well, I think one thing that's clear is that
You know, obviously, AI is getting better and better. And I think for now, there's a lot of really good use and provided your, I guess, provide your patient with, you know, having to maintain AI slop or generate AI slop. I think the folks doing that are the ones who could not originally do software development anyways. Or they're being told by companies, you've got to do this because everyone here is a developer now. We heard that at Build. Everyone's a developer. Everyone's a builder. And I kind of agree with that to a certain point. But I mean, an engineer is an engineer. I don't care how you slice it. An engineer can make something from zero to one with docs and their own gumption and their own abilities and not get stuck behind a poorly vibed solution that didn't work. They will find the path forward and they will deliver it. Whereas everyone else is more like trying to leverage it.
And getting poor results. Well, the hype is there. For some, it's real. For others, it's a dream. And others, it's a nightmare. For others, it's an absolute nightmare. Emphatically. Yes, emphatically so. I am not surprised that VS Code is still the top. Good for them. They've earned that. Yeah, the one that surprised me from that was actually, not that VS Code is the top used IDE, but that Visual Studio was number two. And Notepad?
Third? Notepad++. It's better. Is that your version of it's better? I love that. I've never heard that before. I just want you to do it again. I just did that on the fly there. Yeah. Notepad++. 27.4% of 26,000 people. So what that's telling me is that there's a lot of Windows users taking this. Right? Yeah. It's the number three most used dev IDE. It beats Vim. It beats Cursor. It beats NeoVim, of course. It destroys Xcode. It destroys Zed.
it makes me yeah i mean like a piker zed is 7.3 percent of respondents not bad for a newish editor still not beating sublime 10.5 percent which was our original marching orders two years ago i feel like zed at seven is respectable until you see clod code at 9.7 because that's existed for like six months you know and it goes back to our conversation with nathan sobo when you asked him if he's been working on the wrong thing or would you ask him he got passed up something like that yeah it was something like that like uh because he's building from scratch you know yeah i really hope that That bet pays off and it pays off if the IDE doesn't die, which trending is trending down. The IDE is trending down. I think it'll be a long, slow decline if it actually goes that way. Trending down is a long slope. Yeah. When you're so high, there's so much. That's right. Yeah. But it is trending down. I mean, so even so far as that, who did I speak to recently? And I asked them how much code they're writing. They were on stage with Nora. Yeah. She said none. Yeah. And then somebody else. That's a different example. Yes, I agree with that. Contextually different example.
And they ask somebody else, how much code you write? And they're like, oh, I won't tell you their name, but it's somebody we both know. And they're at a very, they should be in the FAANG list in the acronym, but they're not. So very prominent company. It should be in the FAANG. Zero, writing zero the code. And what role are they? I can't tell you too much. I'll give them away. They should be writing code. They previously wrote code up until a year ago when they didn't have to anymore. And so now they don't have to. And so document driven, documentation driven, theory driven, architectural driven, you know, things like that that's driving the code.
There's still AI is checking that code, which, you know, I'm not going to toot a sponsor's horn too much, but I'm a big fan of CodeRabbit mainly because they offer what they do to open source for free. So if you're running open source out there today and you've got AI spam coming into your PRs, you can curb it with them and also get some intelligence. I think it's pretty cool. But there's there's ways around the slop that isn't me human. discern the slop fix the slop it's ai fixing ai which i'm not sure is a good thing but the trend towards ide dying for the people i'm talking to i think you too is that id is the id is just going away for them and they're writing less and less code that could be a two-year streak and they're like nope we were wrong for two years and they're back to writing code yeah and the id is well alive again so it could be a failed two-year or multi-year experiment but for now the id is dying steve yegi Like Steve said, like you predicted, and that less code is getting written as a result. Less code is getting written by them. It's getting written by not. Less code is being typed into an editor. Right. No one's hand coding the code anymore. They're vibing. Now you said no one, and you just went beyond the trending. You're like, no one is? No one? Come on. Yeah. It's a trend. It's not an absolute. Yep. All right. Well, no one is talking anymore, or at least will be shortly, because that's it, man. That's all I got for this week. All right. Bye, friends. Bye, friends.
All right, that's what we have for you this week. Next week, we'll bring you our awesome interview with Nora Jones and our live Kaizen 20 and Pipely launch from Denver. Stay tuned for that. In the meantime, maybe dig into Stack Overflow's survey results for yourself and see what you can uncover. If you do find something or if you have any feedback on what we covered in this episode, let us know in our community Zulip chat. Sign up for $0 at changelog.com slash community and let your voice be heard. Thanks again to our partners at Fly.io and to our sponsors of this episode. Auth0, start building at auth0.com slash AI. And Depot, 10x faster builds at depot.dev.
Have yourself a great weekend, share a changelog with a friend or three who might dig it, and let's talk again real soon.