CZM Rewind: The Truth About Software Development with Carl Brown

In this episode, Ed Zitron is joined by Carl Brown, a veteran software developer and host of The Internet of Bugs, to talk about the realities of software development, what coding LLMs can actually do, and how the media gets it wrong about software engineering at large. Original Air Date: 6.4.25 https://www.youtube.com/@InternetOfBugs New GitHub Copilot Research Finds 'Downward Pressure on Code Quality' - https://visualstudiomagazine.com/articles/2024/01/25/copilot-research.aspx Report: AI coding assistants aren’t a panacea - https://techcrunch.com/2025/02/21/report-ai-coding-assistants-arent-a-panacea/ Internet of Bugs Videos to watch: Debunking Devin: "First AI Software Engineer" Upwork lie exposed! https://www.youtube.com/watch?v=tNmgmwEtoWE&t=3s https://www.youtube.com/watch?v=tNmgmwEtoWE&t=3s AI Has Us Between a Rock and a Hard Place https://www.youtube.com/watch?v=fJGNqnq-aCA Software Engineers REAL problem with "AI" and Jobs https://www.youtube.com/watch?v=NQmN6xSorus&list=PLv0sYKRNTN6QhoxJdyTZTV6NauoZlDp99 https://www.youtube.com/watch?v=NQmN6xSorus&list=PLv0sYKRNTN6QhoxJdyTZTV6NauoZlDp99 AGILE & Scrum Failures stuck us with "AI" hype like Devin https://www.youtube.com/watch?v=9C1Rxa9DMfI&t=1s https://www.youtube.com/watch?v=9C1Rxa9DMfI&t=1s YOU CAN NOW BUY BETTER OFFLINE MERCH! Go to https://cottonbureau.com/people/better-offline and use code FREE99 for free shipping on orders of $99 or more. --- LINKS: https://www.tinyurl.com/betterofflinelinks Newsletter: https://www.wheresyoured.at/ Reddit: https://www.reddit.com/r/BetterOffline/ Discord: chat.wheresyoured.at https://discord.com/invite/QUUQUP9szv Ed's Socials: https://twitter.com/edzitron https://www.instagram.com/edzitron https://bsky.app/profile/edzitron.com https://www.threads.net/@edzitron Email Me: [email protected] mailto:[email protected] See omnystudio.com/listener https://omnystudio.com/listener for privacy information.

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Speaker 00

  This is an iHeart Podcast. Guaranteed Human.

• 0:04Speaker 01

  OnDeck is built to back small businesses like yours. Whether you're buying equipment, expanding your team, or bridging cash flow gaps, OnDeck's loans up to $400,000 help make it happen fast. Rated A+ by the Better Business Bureau and earning thousands of five-star TrustPilot reviews, OnDeck delivers funding you can count on. Apply in minutes at ondeck.com. Depending on certain loan attributes, your business loan may be issued by OnDeck or Celtic Bank. OnDeck does not lend in North Dakota. All loans and amounts subject to lender approval.

• 0:34Speaker 02

  Empower is all about helping you invest well so you can go out and live a little. And their Free Empower Personal Dashboard shows you your full financial life in one place. You'll be able to see your net worth, monitor budgets, analyze your portfolio, set retirement goals, and more. Whether you're saving for something big, want to treat yourself, friends, or family, or meet long-term goals, Empower helps you see where you stand. You've worked hard for your money, and Empower can help you make the most of it. Download the Empower Personal Dashboard or visit empower.com. Not an Empower client paid or sponsored.

• 1:07Speaker 03

  Call Zone Media.

• 1:11Ed Zitron?

  Hello and welcome to Better Offline. I'm your host, Ed Zetron.

• 1:26Ed Zitron?

  Today, I'm joined by Carl Brown, a veteran software engineer and host of the excellent YouTube channel Internet of Bugs. Carl, thank you for joining me.

• 1:33Speaker 05

  Thanks for having me.

• 1:34Ed Zitron?

  So I'm going to start with an easy one. What is a software developer? Like, what actually is that?

• 1:40Speaker 05

  So basically, what we do is we take ideas about problems that people want to solve generally. And we write software, we write code that tells computers instructions how to make the computer do the thing that needs to do to solve the problem the person asks us to solve.

• 2:04Ed Zitron?

  Right.

• 2:06Speaker 05

  Gaming programming is a little bit different, but that's... Most software development is basically that.

• 2:12Ed Zitron?

  And this is another quite silly question, but necessary. How much of that is actually writing code?

• 2:19Speaker 05

  It depends on how good you... the people that are asking for stuff is. As a general rule, I would say maybe... Between 10% and 25%.

• 2:30Ed Zitron?

  Okay, just really want to be 10 to 20, even if we say 30% of the job, which is more than you said. That means the majority of this job is not actually writing code.

• 2:40Speaker 05

  Right now, that's that's largely for for folks that are farther up the chain, right? So if you're fresh out of school and you don't really, you're not in the the job in the you don't understand how to manage requirements or any of that kind of stuff yet. Someone's going to basically hand you a thing to do. And in that kind of case, you're going to be spending a lot more time writing code than that. But for me, it's, you know, it's far, far more talking to people and stuff than actually writing code.

• 3:06Ed Zitron?

  Right. The reason I asked that and the reason we're doing this as well is that there have been a lot of stories around like LLMs replacing coders, LLMs replacing engineers. Claiming that junior software engineers will be a thing of the past due to LLMs. How much validity is there in that?

• 3:23Speaker 05

  Well, when it comes to the really, really, really fresh out of school kids, right? That you have to basically break everything down and hand them little little chunks of work. An LLM can kind of do that, although the kid will get better over time and the LLM is pretty much fixed, right?

• 3:39Ed Zitron?

  Right.

• 3:40Speaker 05

  But past that, it doesn't do a good job of being able to do any kind of long term thinking. And that's largely the job, right? I mean, this is this is not a set of, you know, I come in today, I do a thing today, I come in tomorrow having no understanding of what happened yesterday. And do another self contained thing and so on and so forth, right? That's not the job. The job is a long sequence of building up on things day after day after day after day until we get to the point where the whole thing together works. And does what it's supposed to do.

• 4:15Ed Zitron?

  So I think that I think that I've known, and one of the reasons I had you on as well, is that there really, there are so many of these stories. They're claiming that like the software engineer's job is gone, that these companies will be writing all of their code with AI. And it doesn't even seem like that it's possible. One of your videos, you did a really good thing around like the 20 to 30% are linked to this in the notes, 20 to 30% of code. The behind Meta, and I think Google it was, is written by AI now. Again, how much validity is there to that?

• 4:44Speaker 05

  Well, I mean, so if.

• 4:47Speaker 05

  One of the quotes was something to the effect of 30% of the code is suggestions that were given by autocomplete that a human accepted, right?

• 4:54Ed Zitron?

  Right.

• 4:55Speaker 05

  Which could be as much as, you know, the, the, the thing said, oh wait, you spelled this wrong, let me give you a suggestion about how to spell it correctly, right?

• 5:02Ed Zitron?

  Right.

• 5:03Speaker 05

  I mean, how, how much of the, the actual text that you write is, you know, is corrected by a spell checker, right? If all that counts as AI, then what percentage of your stuff is written by AI, right?

• 5:14Ed Zitron?

  Right. In my, in my case, absolutely nothing, but that's just, I'm a freak. I'm just a complete freak. But no, I get your point. And it's, without being a coder myself, it's something I've really noticed across these stories where people just kind of blindly push them out and they say, oh yes, 20, 30% of the code is written by, but there's no verifying this.

• 5:34Speaker 05

  Right.

• 5:34Ed Zitron?

  And also, it feels like it might create a bigger problem, which is, say we accept this idea, even though I don't, and it sounds like a pretty spurious one, kind of silly to do so. At some point, isn't code not just the series of things that you write to make a program work? It's connected to a bazillion other things, which

• 5:53Speaker 05

  Right.

• 5:54Ed Zitron?

  If you don't know why that was written, because you had something generate it, is that not a huge problem?

• 6:00Speaker 05

  Yes, but worse, what we, what we're finding when code gets generated is that basically you end up doing the same thing in a bunch of different places, but in each one of those different places, you do it a different way.

• 6:13Ed Zitron?

  Can you give me an example?

• 6:15Speaker 05

  Um, so for example, um, when you need to go fetch a thing from a server, right? We, over here in this code, you fetch a thing from a server, over here in the code, you fetch a different thing from the server. Um, normally you'd be able to use the same block of code to do that, so that if there's a mistake in it, you can change it once and it's fixed everywhere, right?

• 6:31Ed Zitron?

  Right.

• 6:32Speaker 05

  But the way the LLMs work is you say, hey, I want to fetch a thing from the server, and it says, cool, and it writes a whole thing for you that may or may not work the same way as the previous one, right? And so now, you, you find, okay, under some circumstances, we're having a problem fetching things from the server. I don't know which one of these 12 implementations that go fetch from the server is the one that's actually causing the problem.

• 6:49Ed Zitron?

  Right. Also, isn't there, isn't there a security issue of having large language models? Like, like, wouldn't all the code be quite similar? Or at least more similar, depending on if everyone's using Claude or everyone's using, well, GitHub Copilot, I guess is Claude now?

• 7:05Speaker 05

  No, not really. It basically kind of picks a random number at the beginning and goes, okay, so that's the, I think of it kind of like you deal a deck of cards, right? Whichever deck of card gets turned over first, that's the beginning of the autocomplete that it starts. And so depending on which example it's, I don't want to say thinking of, but depending on which example represents that, I'm drastically oversimplifying, but depending on which example is represented by that card, it's going to go down one path or another.

• 7:29Ed Zitron?

  Right. And so what are they actually, what are these large language model coding tools actually good for? Cause I get a lot of people who, who respond by saying, this is proof that AI is a big deal. And I'm just kind of like, I'm not even looking for a particular answer, just truly what's useful about them.

• 7:45Speaker 05

  So they are decent at when you know what you want and what you want is a fairly simple self-contained thing. And you know how to tell whether or not the self-contained thing does what you want. It can type it faster than you can.

• 8:02Ed Zitron?

  Like autocorrect?

• 8:03Speaker 05

  Basically, yes. It's like autocomplete. If you, if you know exactly what you want, yeah. I mean, so I use it a lot because I program in a bunch of different programming languages a lot. Right? On different projects at the same time, or on the same day or the same week. And it's really easy for me to go, okay, wait, which language am I in right now? Okay. How do I do this in this language? Right? So it's kind of.

• 8:24Ed Zitron?

  You can actually understand the generation though, when it comes.

• 8:26Speaker 05

  Yeah, it's like, I, I, I know what kind of loop I want, but I don't remember the syntax for this particular language or I don't want to. So it's, I use it kind of like a, a Google Translate kind of thing to go from one programming language to another sometimes.

• 8:37Ed Zitron?

  But you wouldn't trust it to build a full software package?

• 8:41Speaker 05

  Oh, not at all.

• 8:42Ed Zitron?

  Why not?

• 8:43Speaker 05

  Uh, well, it wouldn't work to start with.

• 8:46Ed Zitron?

  Why wouldn't it work?

• 8:47Speaker 05

  Well, I mean, so I've done some experimentation on that where I've taken fairly complicated,

• 8:55Speaker 05

  challenges, challenges that were intended for programmers to basically get better at their craft and that kind of thing. And I've run AI, you know, told it step by step, okay. The, the, the challenge says, this is your next step, do this. The challenge says, this is your next step, do this. On really simple challenges in programming languages like Python, that it's got a lot and a lot of examples for, it does okay. Past the point where you're in the really simple kind of language things, they just, they sometimes get to the point where they can't even create anything that builds at all.

• 9:25Ed Zitron?

  Huh. Why is there, why do so many engineers swear by it then?

• 9:31Speaker 05

  Um, honestly, I'm not sure to what extent the engineers are swearing by it. Um, I've talked to a lot of folks who are like, you know, my group, you know, this big bank, you know, friend of mine, um, my group is getting co-pilot jammed on our throats whether we want it or not, and the executives are all really excited about it and none of us are.

• 9:51Ed Zitron?

  Interesting. So it's executive, I've, I've personally had this theory that it's like executive pushed. And that it's all about, it's all about what the bosses want to see rather than even do. Sorry, now I'm going to move my cat out of the way. There you go.

• 10:06Speaker 05

  There's, there's a lot of wish fulfillment. There's a lot of like, we want to not have to deal with these programmers anymore. So we would rather deal with the AI thing and we're just going to hope that the AI thing is going to be, you know, just as good as the programmers are close to is just as good as the programmers and not nearly as annoying.

• 10:21Ed Zitron?

  Seems like a definitional, well, maybe that's not the right word. Seems like the difference between a software engineer and a software developer almost because it's not just about flopping code out. It's about making sure the code does stuff.

• 10:34Speaker 05

  Yeah, I mean, those, those terms get.

• 10:37Ed Zitron?

  Mashed together.

• 10:38Speaker 05

  Yeah. I mean, so part of the problem is that in, it's like, I live in Texas and in Texas, you're not allowed to call yourself an engineer unless you pass the engineering exam.

• 10:45Ed Zitron?

  Oh.

• 10:46Speaker 05

  Um, right. So I, I can't literally, I literally can't call myself a software engineer legally in Texas as I understand it. I'm not a lawyer, but that's my understanding. So it's like the, the terms get all confused.

• 10:56Ed Zitron?

  Right. So somewhat related, what is it that people misunderstand about the job then?

• 11:02Speaker 05

  Well, I mean, so one of it is what you said earlier, which is that a very small percentage of the, the job is actually slinging code. A lot of it is basically trying to figure out what it is the code should do based on what you've been told that the problem, you know, that, that the solution to the problem that you're trying to solve. Um, another thing is that, um, a lot of the, the, the problem with the job is that every little decision builds up over time. And at some point, a bug is going to happen. They're inevitable. And when that happens, basically there's this process where what you need to do, if you're being competent. Is roll back through that series of decisions, figure out what caused that bug,

• 11:45Speaker 05

  and then figure out what other bugs are likely to have been caused by that same set of decisions, and then fix not just the bug you're working on, but the bugs that, you know, not just the bug that's been reported, but the bugs that might have also been caused by the same problem, right?

• 12:00Ed Zitron?

  Right.

• 12:00Speaker 05

  And that kind of long-term thinking is not a thing I've ever seen LLM exhibit at all. I talk about it like LLMs or, you know, generative AI is good at solving riddles, but actual software development is more like solving a murder.

• 12:13Ed Zitron?

  Yes, you said that in that wonderful video, yeah. I, and it almost feels as if we are building towards an actual calamity of sorts. Maybe not an immediate one, maybe it will be kind of sectioned off into areas, because you've got a new generation of young people coming into software engineering or what have you, learning to use AI tools rather than, and your videos definitely talk about this as well, actually how to develop software and make sure it works, and make sure that it has the infrastructural side in line, and also that you're building it with the long-term thinking of someone else might need to understand how this works, and they're not learning that. So you've just got a generation of kind of pumping the internet and organizations with sloppier code.

• 12:57Speaker 05

  Yes, although, I mean, one of the problems we're having at the moment is that the hiring process for really junior engineers is actually pretty broken at the moment. And a lot of people are not hiring people that are fresh out of school because they're expecting that the AI will be able to do, that basically a senior or a mid-level developer with the benefit of AI, with the benefit of AI, that's in air quotes, will be able to do the work of that person, plus a couple of fresh outs that they normally would have hired, but they're not hiring at the moment. There's some statistics about how the people that are fresh out of school these days are historically underemployed relative to the general population, at least in the US where I live.

• 13:42Ed Zitron?

  It also feels like there's no intention behind the code. Like, it's just if you're just generating it, you don't really know why you made any particular. You could say I chose these lines, but is that at some point, if you have large amounts of software developers using it, however large, but the young people in an organization using it to generate their code, they're neither learning to write better code, nor are they learning how to develop. They're just learning how to fill in blocks. They'll never grow within their job.

• 14:10Speaker 05

  Yeah, I mean, the, the, the trick is that those of us that have spent a whole lot of time debugging software, right? And like finding the problems and digging into them and trying to figure out what's going on. That kind of stuff, it's going to be really hard for younger folks to get hired into those jobs so that they have time to, to build the experience to be able to do that. And I'm afraid we're going to end up with basically an older generation or generations retiring and a newer generation that hasn't had the experience of doing that kind of debugging. And then it's going to be a real mess, especially since from what I can tell, the code that the AIs generated are a lot buggier and buggier in weirder, like,

• 14:54Speaker 05

  randomish kind of ways, stuff just kind of comes out of nowhere in a way that I don't, I mean, I've debugged code from people that don't speak the same languages as I do, you know, that kind of stuff. AI code is different. It's just like, okay, why would anyone want to put that block there? That doesn't have anything to do with what we're trying to do at the moment.

• 15:12Ed Zitron?

  And why, why is that? Is it just because it's probabilistic?

• 15:16Speaker 05

  I guess so. I mean, it's, it's hard to say why. I mean, the, the, the idea of why an LLM does what it does is kind of a, you know, anybody's guess.

• 15:26Ed Zitron?

  Yeah, it's just, I keep thinking of the word calamity because you sent me these studies as well about how they found like a downward pressure on the quality of code on GitHub. Would you mind walking me through what that means?

• 15:40Speaker 05

  Yeah. So basically what that study found, there were, there have been a couple of them, but what that particular study found is that there's a, what they call code churn has gone up. And code churn is basically when you push something, you, you like add a line of code, you push it into to test or to production. And then in a short period of time, like, I don't remember exactly what the, the definition was like in a month or two months, that line of code changes. Right. So basically, what that means is that the line of code that got created, somebody decided after it got put in, oh, wait, no, that doesn't work right. We don't, we're not happy with that. We're going to change it to be something else. Right?

• 16:17Ed Zitron?

  Right.

• 16:17Speaker 05

  And the percentage of lines or the number of lines that that get changed fairly quickly after they get submitted has gone way up since the since the implementation of GitHub Copilot. So this is across like most of the the giant, you know, millions of lines of codes on GitHub.

• 16:38Ed Zitron?

  And for simple to me, why does it being change? Why is changing it so often bad?

• 16:45Speaker 05

  Like, Well, I mean, so, I mean, if you do it right, the first time you can move on to the next thing.

• 16:50Ed Zitron?

  Ah.

• 16:51Speaker 05

  Right. If it's like, you know, if you're writing a document and you put, put the document in there and then you like, well, you're in, you're in, in Google Docs and you're like tracking changes. And it's like, okay, this sentence has changed 17 times. Obviously, the person isn't happy with the way that sentence is, right?

• 17:06Ed Zitron?

  So the generative code isn't good.

• 17:08Speaker 05

  Right.

• 17:08Ed Zitron?

  And so people see need to change it.

• 17:10Speaker 05

  That's the presumption. Yes.

• 17:12Ed Zitron?

  And so I it also said the code quality itself, is that the only way they is that the only way they measured it? Or is it there are other things as well?

• 17:22Speaker 05

  Um, so they measured that. Um, they measured, um, uh, like,

• 17:29Ed Zitron?

  Moved code?

• 17:31Speaker 05

  Yeah, the

• 17:31Ed Zitron?

  Less moved code.

• 17:32Speaker 05

  The thing I was talking about earlier, where the you've got a bunch of different places in the code that all do the same, you try to do the same function, but they do it in different ways. Normally, what would happen is you'd have your, you do, you do a thing here, right? And then at some point in the future, you need to do that thing again in a different place. And so what you do is you would move that original block that does the thing someplace else. And then you would call that block from both places.

• 18:01Ed Zitron?

  Right, because it already works.

• 18:02Speaker 05

  Right. And then that way, you've got, you know, however, you go fetch stuff from the server, you're fetching it the same way. But with this thing, basically, instead of doing that, you've got copy paste. Okay, let me put another one here. Let me put another one here. Let me put another one here. And it's, it's a maintenance nightmare.

• 18:24Speaker 06

  Cash Flow Crunch? OnDeck's Small Business Line of Credit gives your business immediate access to funds, up to $200,000, right when you need it. Cover seasonal dips, manage payroll, restock inventory, or tackle unexpected expenses without missing a beat. With flexible draws, transparent pricing, and control over repayment, get funded quickly and confidently. Apply today at ondeck.com. Funds could be available as soon as tomorrow. Depending on certain loan attributes, your business loan may be issued by OnDeck or Celtic Bank. OnDeck does not lend in North Dakota. All loans and amounts subject to lender approval.

• 18:55Speaker 02

  Empower is all about helping you invest well so you can go out and live a little. And their Free Empower Personal Dashboard shows you your full financial life in one place. You'll be able to see your net worth, monitor budgets, analyze your portfolio, set retirement goals, and more. Whether you're saving for something big, want to treat yourself, friends, or family, or meet long-term goals, Empower helps you see where you stand. You've worked hard for your money, and Empower can help you make the most of it. Download the Empower Personal Dashboard or visit empower.com. Not an Empower client paid or sponsored.

• 19:27Speaker 07

  Hi, I'm Jenna Ushkowitz. You might know me from Glee. This is At the Table, the food allergy podcast, a show about food, connection, and what it really looks like to live with food allergies. Each episode, we hear stories from real people like Daniel.

• 19:41Speaker 05

  People would always think I was lactose intolerant, so I just kind of shortened my explanation to I'm deathly allergic in a big way that defined a lot of my childhood.

• 19:52Speaker 07

  And while there are challenges, there are moments that remind you you're not alone.

• 19:57Speaker 03

  One of the best guys that I dated, he made a point to memorize all my food allergies.

• 20:03Speaker 07

  So join us and hear their stories and more because living with food allergies isn't just about what you can't eat. It's about still having your seat at the table. Brought to you by Genentech and Novartis. Listen to At the Table, the food allergy podcast on America's number one podcast network, iHeart. Follow At the Table and start listening on the free iHeart Radio app today.

• 20:27Ed Zitron?

  So for the for the audience as well, how does a software developer actually use GitHub? Like really simple stuff, I realize, but I think it's important for people to it just occurred to me that this may be something that most listeners don't know, which is good to, I think it's good.

• 20:40Speaker 05

  Yeah. So, so what we do is we basically make changes to code. We get to the point where we, the developer, are happy with the way it's set up on our machine. And then we do what's called a push and we basically send all that code, submit all that code up to GitHub. And then theoretically, you know, there can be automatic processes that kick in that like check that code for particular things and run tests on it and that kind of stuff. And then at some point, we have a thing called a pull request, which is basically a thing that says, okay, I would like this to go into production now, or more or less. I would like this to get promoted into the next phase now. And then someone theoretically will look at it and go, okay, that's fine. And then click the yes button or say, hey, you forgot about this, go look at this or that kind of thing.

• 21:21Speaker 05

  Right. And the pull request is kind of the unit of work, kind of.

• 21:26Ed Zitron?

  Right. So with GitHub, you almost use it like an organizational code dump. Or like where you centralize all the code, code, sorry, just for the, for me, I'm non-coding as well. And I think it's, I think that the LLM industry has done a really good job of dancing around these terms and selling them to people like me, while they weren't selling, they didn't work on me. I am too stupid, but it's where they've just like been like, okay, yeah, well, lots of people use Copilot. That's good. And this is good because code, software is coding. But it kind of feels like, I don't know, all of this is taking the one thing, like one major part out of software development and ruining it.

• 22:08Ed Zitron?

  And I don't even mean coding. I mean, it's the intentionality behind software design and infrastructure. And maintain like there's, it seems like they're removing intention in multiple parts.

• 22:21Speaker 05

  Um, I, so the way I would say it is when they talk about the AI being able to do the work of a programmer, what they're doing is they're devaluing all of the stuff that's not just. Hacking code, right? And so what they're saying is that basically the job of a developer is basically just, you know, typing, basically.

• 22:42Ed Zitron?

  Right.

• 22:43Speaker 05

  And that all of the work that we do to understand what the problem actually is and how it needs to work and, you know, what other problems are likely to show up when we try to do that and how to avoid those things as we go and that kind of thing. All that work is basically not important.

• 23:00Ed Zitron?

  And I mean, I'm gonna say two words which will probably annoy you. This is, I feel like vibe coding is the other part of this. So if I'm correct, correct me if I'm wrong, vibe coding is just typing stuff into an LLM and software comes out and hopefully it works?

• 23:17Speaker 05

  Yeah, vibe coding is basically when you intentionally try, well, I don't know about intentionally, but basically you make a point of not digging into the code and looking at what the LLM is doing. And you basically say, okay, I would like something that does X, right? I would like a game where I fly airplanes around a city or something, right? And then you get what it spits out and then you say, you know, okay, let me try it. Okay, well, can we have more airplanes and okay, can we have some balloons with, you know, signs on them now and can we do this kind of thing? And then you don't think about what the side effects are. You don't think about what things could go wrong. You don't think about air conditions, that kind of stuff. And you just hope that this, whatever you look at and has the right vibe and that, you

• 24:00Speaker 05

  know, if it, if it, if it looks like kind of what you wanted, that probably it's gonna be fine or hopefully it's gonna be fine.

• 24:07Ed Zitron?

  How do you feel about vibe coding?

• 24:09Speaker 05

  Um, so I do it sometimes. Vibe coding is great for a thing that you're going to do once and then throw away.

• 24:15Ed Zitron?

  Yeah.

• 24:16Speaker 05

  Right? So if it's like, you know, okay, I wanna, I wanna do a thing. I wanna translate this thing to, you know, I wanna make this table go into this format over here or that kind of thing. You do it, you get the output you want, you throw the code away, no big deal, right?

• 24:27Ed Zitron?

  Like a prototype almost.

• 24:28Speaker 05

  Yeah, basically. Um, and so, you know, we call them spikes or tracer bullets sometimes. It's like a, you know, let me get a thing that, that works at all, right? And then let me see what I can learn from that to, to move into my big maintainable project. But for anything that's like, you know, this thing needs to run for a while, this thing needs to not get hacked, this thing needs to, you know, not crash, it's a really bad idea.

• 24:54Ed Zitron?

  Yeah, and at some point, I feel like someone building a product that they don't really understand the workings of, it's kind of almost identical to generating a story with ChatGPT, except kind of more complex and more prone to errors.

• 25:09Speaker 05

  Yeah, and the other thing is that there's an adversarial component, right?

• 25:14Ed Zitron?

  So.

• 25:15Speaker 05

  People will intentionally try to go hack that thing that's sitting on the internet.

• 25:19Ed Zitron?

  Oh.

• 25:20Speaker 05

  Right, in a way that they don't intentionally try to go mess with the story that you wrote.

• 25:25Ed Zitron?

  Right.

• 25:25Speaker 05

  Right, and so even if it works all by itself, that doesn't mean it's going to work when somebody starts pounding on it intentionally trying to break it. And if they can break it, then that's a whole other set of problems that you now have.

• 25:37Ed Zitron?

  It feels like quality assurance is just never part. Oh, no, that, are they claiming they're going to do quality assurance with large language models yet? They must.

• 25:44Speaker 05

  That, some people are, yeah. I mean, to be honest, a lot of companies have just been getting rid of quality assurance over the years, right?

• 25:54Ed Zitron?

  Oh, really?

• 25:54Speaker 05

  When I worked at IBM, we didn't have quality assurance at all. They would, no, seriously, they would do this, I was in IBM's cloud group, and they would do these, these, what do they call them? Hackathon kind of things, they didn't call them that, I don't remember what they called it, but basically, everybody in all the other development groups would get together and basically bang on the code that was about to get released from some other group to try to see if they could break it.

• 26:17Ed Zitron?

  Right.

• 26:17Speaker 05

  But they didn't have dedicated testers anymore because they decided, I guess, that they didn't think they were worth the money, I don't know, but we had some issues because of that.

• 26:26Ed Zitron?

  When did that movement happen?

• 26:29Speaker 05

  Um, I was in, I don't know, so I was at IBM in like 2017, 2018.

• 26:35Ed Zitron?

  Right.

• 26:35Speaker 05

  So it would have been sometime prior to that. When I got there, they didn't have any QA folks.

• 26:39Ed Zitron?

  Really just feels like the, it's the management problem as well. It's the management gotten people.

• 26:44Speaker 05

  I would think so.

• 26:46Ed Zitron?

  It's a real shame as well, and I, forgive me if I'm forgetting exactly where, you've mentioned as well that there is like compound scar tissue from AI-generated code, a larger problem of lots of this code being generated with AI.

• 27:01Speaker 05

  Well, that's.

• 27:03Speaker 05

  That's my expectation, right?

• 27:05Ed Zitron?

  Yeah, just a potential worry.

• 27:07Speaker 05

  Right, right. So that the more of this we get and the more issues that we have, the more stuff we're gonna have to dig out of, right? And what I'm honestly envisioning at some point in the, I don't know how long this will take, the crypto bubble took way longer to pop than I expected. So I don't know how long it's gonna be before this one does. But I'm expecting that there's gonna be this big push to try to clean up a bunch of this crap here in a few years, once people realize that a lot of the code that's being written and generated right now is, has all of these vulnerabilities that nobody's bothering to check for at the moment.

• 27:39Ed Zitron?

  Right. And those vulnerabilities, again, non-technical way, I read that it was like they call upon things on GitHub that don't exist. So bad actors create something that resembles what it's pulling from.

• 27:50Speaker 05

  That's, so that's, that's a more specific kind of one. I mean, there are a lot of things, I mean, so there have been computer viruses since the 80s, right? Um, you know, the, the Morris worm and that kind of stuff. And basically, there are known ways that code, if you, you have to write it in a particular way in order for it to be secure, right? And even then, sometimes people come up with novel ways of making something not secure.

• 28:15Ed Zitron?

  And how, how do you have to write it to make it secure? If, if it's possible to explain?

• 28:19Speaker 05

  Well, I mean, there, there's a big, long list of rules, right? I mean, one thing you can do is you can use languages that are what they call safer. But still, you have to make sure that any input that you get from the network, you're really, really careful to make sure that it doesn't get to overwrite parts of your program that actually execute things.

• 28:36Ed Zitron?

  Right.

• 28:37Speaker 05

  Um, you have to make sure that it doesn't have the opportunity to be able to write to pieces, places on your disk that it shouldn't be able to write to. Um, you have to be able to make sure that it doesn't have access to, to read data that it shouldn't be able to read, you know, all that kind of stuff. Um, and when those things don't happen, you end up with, you know, so and so got hacked, you know, turns out that somebody we think maybe China is reading the email of the, you know, people in Congress. Um, you get another letter in the mail that says your social security number has been, you know, leaked by, you know, some credit checking firm or something like that.

• 29:14Ed Zitron?

  Even like, I think it was what the big hot target data breach from a while back was through the HVAC system. It was, it was, it's just, except now we've got, and that was with humans writing the code.

• 29:28Speaker 05

  Right.

• 29:28Ed Zitron?

  Imagine if we didn't know. Oh God, it really does feel like the young people are like the, actually now I take it back. You were talking about Agile the other day. I'm going to ask you to explain that in a second. But it's like, it sounds like for almost decades, they've been gnawing away at, management's been gnawing away at the sides of building good software and building good software culture.

• 29:52Speaker 05

  Yes, I mean, there's an argument that says that we never got it right in the first place, but I mean, I mean, if you think about it, software has been a thing for what 50 years, 60 years, 70 years, right? I mean, compare that to like, construction engineering or bridge building or that kind of stuff, right? We're still, you know, relatively speaking, in the infancy, in our infancy as a, as a industry. You know, it's been a, it's been a constant evolution and a lot of times, the things that were, the, the, the things that we did to solve a, a problem that we had ended up causing other problems, right? So going back to Agile, in the long, long ago, right? We used to manage software projects the same way we manage like build, you know, bridge building and building, building progress, you know, construction projects.

• 30:37Speaker 05

  And it turns out that when you're going to build a bridge, you know beforehand what you need to build the bridge to do. When you're building software, a lot of times people are changing their minds as you go, right? And you build a thing and you show it to them and they're like, oh, why don't we put this over here and why don't we change this and that kind of thing, right?

• 30:53Ed Zitron?

  Right.

• 30:54Speaker 05

  Because you don't have the same kind of constraints, physical constraints that you do when you're trying to build a bridge. And so we got in this problem where you would create these project plans about how you were going to build this thing and you would never be anywhere close to on time because things would change the whole time.

• 31:08Ed Zitron?

  Right.

• 31:08Speaker 05

  And so they created this thing called the Agile methodology. I'm drastically simplifying. There were steps in the middle, but basically, so this, this Agile thing is where we, instead of saying, okay, so this is what the whole project's going to look like. We're going to be doing, we're going to be done in six months and then things changing along the way. We basically block off a thing called a sprint. It's a week or two or a month, maybe it depends. And then, you know, everybody picks their own sprint length and then you go, okay, I'm only going to talk about what's going to happen in the next sprint or two, right? And then you get to the end of that two weeks and you go, okay, cool. This is what we got done. What do we want to do next? And then, okay, that's what we got going. What do we want to do next? And that kind of thing. And that way, as you go, you have the opportunity to change things. You have an opportunity to roll changes into the process, that kind of thing, right?

• 31:52Speaker 05

  And the problem with that is kind of the same way that dates always ran out in waterfall land. Projects can go way, way longer than they were expected to at the beginning because everybody's focused on just two weeks at a time. And you never kind of take a big step back like you ought to and go, okay, wait, you know, we were supposed to be done, you know, two months ago. When are we going to wrap this up?

• 32:15Ed Zitron?

  Right. And how has that led to things getting worse? Is it that just software culture, software development culture has been focused on short term perpetually is?

• 32:25Speaker 05

  The short term is part of it. Part of it is there are, you know, unscrupulous developers out there that basically want to extend the length of the project so they can get more money out of it.

• 32:37Ed Zitron?

  Right.

• 32:37Speaker 05

  Right. That's, that's always the case. But the other thing is that you end up with a real,

• 32:46Speaker 05

  a lot of times you end up with a real lack of like long-term planning and long-term understanding.

• 32:50Ed Zitron?

  Right.

• 32:50Speaker 05

  Right. Cause everybody's, you know, same kind of thing, you know, companies are only worried about what happens next quarter, right? If you're only worried about what's going to happen the next week or the next four weeks, the, the things that you look on, look at, you know, tends not to have the longer term implications that sometimes you need, right? And there are times you get close to the end and you're like, oh, you know, we didn't think about this.

• 33:14Ed Zitron?

  What are we building?

• 33:14Speaker 05

  Problem. Yeah.

• 33:16Ed Zitron?

  And also, if you're in a two or three week thing, you're probably not thinking even what you did last sprint. Like it.

• 33:24Speaker 05

  Maybe last one, but not like two or three, two or three ones ago.

• 33:28Ed Zitron?

  Is this a problem throughout organizations of all sizes? Is this a consultancy problem? Is, is it everywhere?

• 33:34Speaker 05

  Um, it's most places.

• 33:37Ed Zitron?

  Huh.

• 33:37Speaker 05

  Um, there, there are, there are some places that are, um, Usually in startups, we're a lot more ad hoc and we're a lot more focused on trying to get things done. Basically, the idea is the larger you get as an organization and the more money you're throwing at it and the more management control you want, the more of this overhead you put in place and the more complicated things get, just as a management structure kind of thing.

• 34:11Ed Zitron?

  And this in the bigger, so this is something you'd seen like a Google and an Amazon as well?

• 34:15Speaker 05

  Oh, absolutely.

• 34:17Ed Zitron?

  So do you think it has the same organizational effects or?

• 34:21Speaker 05

  Um, largely, yes. So those organizations tend to be, well, those organizations historically have tended to be, before the recent like in shitification wave, those, I'm assuming I can swear on this.

• 34:41Ed Zitron?

  Yeah.

• 34:43Speaker 05

  The, those organizations have historically been fairly more engineering driven, which means that you typically have people higher in the organization that are technical and have been programmers and who understand some of the implications. And so they tend to try, at least we try, to run interference with management and to try to, you know, make sure everybody's on the same page and that kind of stuff. A lot of, a lot, not all, but a lot of problems can get lessened if you have people in the organization that are at a higher level, whose job is not to manage people, but whose job is basically to keep track and coordinate between different groups that are doing different technical things.

• 35:26Ed Zitron?

  Right. To make sure people aren't building the same thing, I'm guessing, or are building the right thing in the right way.

• 35:31Speaker 05

  Yeah. And that, and that how, what this group is building is going to impact what this group is building at some point in the future. And making sure that when you get to the point where those two things need to talk to each other, they're both aware enough of what the other one is doing, that the two things hook together correctly.

• 35:46Ed Zitron?

  Yeah, so based on my analyses of these companies, that's definitely gone out the window. I mean, even with LLM integration, so there was a Johnson and Johnson story that went out Wall Street Journal a couple of weeks ago, where it was like, they had 890 LLM project, or generative AI projects, of which, take like the Pareto Principle wins again, 10%, 15% of them were actually useful. And the thing that stunned me about that, other than the fact it confirmed my biases, which I love, was the fact that there were 890 of the fucking things, and no one was like, should we have this many? That there was no like, like, software engineering culture that was like, hey, are we all chasing our tails? Is this useless? But it sounds like they were all focused on their little, the little boxes.

• 36:31Speaker 05

  Yeah, I mean, so the other thing, so I understand that, again, greatly oversimplifying, a lot of the new stuff that's happened with the large language machines, large language models and, and generative AI, people didn't expect, right? It was kind of a surprise when you throw a whole bunch more data at a large language model and it started spitting out text in a way that nobody really, there was no like, mathematical reason to expect it to be able to be as good at generating autocomplete stuff as it, as it was, right? And so there's this belief that if we did the thing, and we unexpectedly got more than we asked for, if we do more of the thing, maybe we'll unexpectedly get more of what we wanted, right?

• 37:15Speaker 05

  That hasn't seemed to really pan out the last couple of years, from what I can see, but, but that, that, we don't really understand enough about this to know whether it's going to work, so we might as well throw spaghetti at the wall and see if it sticks, because it might. Kind of mentality is kind of pervasive at the moment. And everybody's, there's a lot of FOMO, there's a lot of like, you know, well, our competitors are probably doing this, and so we, we don't want to get left behind. It's kind of reminds me of the, the rumors that they talked about back in the 80s, when the CIA was doing all this psychic research, because supposedly the Russians were doing psychic research, and it was all complete crap, but both sides were convinced that the other side was making some progress, and so everybody was dumping a ton of money into it.

• 37:58Ed Zitron?

  LLMK Ultra.

• 38:01Speaker 05

  Exactly.

• 38:01Ed Zitron?

  Yes. Title of the episode.

• 38:14Speaker 06

  OnDeck is built to back small businesses like yours. Whether you're buying equipment, expanding your team, or bridging cash flow gaps, OnDeck's loans up to $400,000 make it happen fast. Rated A+ by the Better Business Bureau and earning thousands of five-star TrustPilot reviews, OnDeck delivers funding you can count on. Apply in minutes at ondeck.com. Depending on certain loan attributes, your business loan may be issued by OnDeck or Celtic Bank. OnDeck does not lend in North Dakota. All loans and amounts subject to lender approval.

• 38:42Speaker 02

  Empower is all about helping you invest well so you can go out and live a little. And their Free Empower Personal Dashboard shows you your full financial life in one place. You'll be able to see your net worth, monitor budgets, analyze your portfolio, set retirement goals, and more. Whether you're saving for something big, want to treat yourself, friends, or family, or meet long-term goals, Empower helps you see where you stand. You've worked hard for your money, and Empower can help you make the most of it. Download the Empower Personal Dashboard or visit empower.com. Not an Empower client paid or sponsored.

• 39:14Speaker 07

  Hi, I'm Jenna Oshkowitz. You might know me from Glee. This is At the Table, the Food Allergy Podcast, a show about food, connection, and what it really looks like to live with food allergies. Each episode, we hear stories from real people like Daniel.

• 39:28Speaker 05

  People would always think I was lactose intolerant, so I just kind of shortened my explanation to I'm deathly allergic, in a big way that defined a lot of my childhood.

• 39:39Speaker 07

  And while there are challenges, there are moments that remind you you're not alone.

• 39:45Speaker 03

  One of the best guys that I dated, he made a point to memorize all my food allergies.

• 39:50Speaker 07

  So join us and hear their stories and more, because living with food allergies isn't just about what you can't eat, it's about still having your seat at the table. Brought to you by Genentech and Novartis. Listen to At the Table, the Food Allergy Podcast, on America's number one podcast network, iHeart. Follow At the Table and start listening on the free iHeartRadio app today.

• 40:14Ed Zitron?

  So, okay, LLM, Kai Ultra aside, is this something you're seeing in software development, though? Because I know I've seen it in management where it's just gonna like shut the shit in there. This seems like it's an important thing, right? Or is this, are you seeing it within software development?

• 40:29Speaker 05

  So I am seeing it within software planning, right? So when, when managers are sitting down and saying, okay, we need to build this new thing. We need to create a new group. We need to split this group apart. We need to decide what our headcount's gonna be for next year. There's a lot of, okay, and what do we think the AI is gonna do next year? And how many headcount do we think that's gonna save us and that kind of thing, right? There are some companies, Duolingo is one, Klarna is one.

• 40:54Ed Zitron?

  Yeah.

• 40:55Speaker 05

  OP, sorry, BP, the former British Petroleum, what, last year had a thing where they said they were cutting 70% of their contract software developers.

• 41:04Ed Zitron?

  And in most of these, they've kind of rolled them back as well.

• 41:07Speaker 05

  Um, I don't think Duolingo has yet, but.

• 41:09Ed Zitron?

  No, this, this is just being unfair to you. They like a day ago.

• 41:13Speaker 05

  Really?

• 41:14Ed Zitron?

  We're just like, ah, we're kinda, it's so fun, it's so funny. It's so funny that this just keeps happening in exactly the same way. It's like, oh, what a surprise, human beings can do stuff.

• 41:22Speaker 05

  Yeah.

• 41:23Ed Zitron?

  But it kind of gets back to, I think, what you've said about everything with LLMs. It's like, you can teach something to say, yeah, I think the right, the thing you're looking for is this, but you can't teach it context. And that's been a point you've made again and again. Like, it seems the job of a software engineer is highly contextual, unless you're like in the earlier days.

• 41:41Speaker 05

  Yeah, and I liken it sometimes to the, the Memento guy from the Memento movie, right? Where like can't form long-term memories. And then do you, do you really want the Memento guy to be the person that's building the, the software that makes the 737 Max be able to compensate for its control input?

• 41:59Ed Zitron?

  Yeah. The thing is, though, with that argument, they would argue, and I know that there is a better argument here. They would argue, well, what if we just give it everything that's ever happened? What if we just show every single thing we've ever done on GitHub? Surely then it would understand.

• 42:16Speaker 05

  So what the, what I have seen from the papers that I have read is that LLMs have a basically squishy middle context problem, kind of the way that you do, right? So if somebody gives you a big document to read, or a big long documentary to watch or something, and then they ask you questions, what they're gonna find is that you remember a lot more from the beginning of that and the end of that than you do from the middle of that, right? And LLMs have the same kind of problem, right? And the other problem that the LLMs seem to have is that when you give them a whole bunch of instructions, just instructions, follow on instructions, follow on instructions, they can either get confused and forget some of the instructions, or they deadlock, or they just start going, okay, I can't satisfy all of these, so I'm not even gonna bother

• 43:00Speaker 05

  to satisfy any of them, or they'll pick one or two. The fact that you can take a million tokens, and you can stick that in the memory block that the GPU is gonna process, doesn't necessarily mean that all of the tokens in that memory block are actually going to be treated equally and going to be understood, right? In theory, maybe if you could train your, if you could like custom train an LLM and

• 43:41Speaker 05

  modify all of its weights based on exactly what your stuff was, and do that like day after day after day after day as things changed, you would theoretically get better. I still don't think it would be, you know, I still don't think it would understand the context as well, but that would be ridiculously expensive.

• 44:00Ed Zitron?

  Yeah, and at that point, you could train a person.

• 44:03Speaker 05

  Yes, I mean, the person would probably be more annoying. That's, I mean, the point, I mean, a lot of this is, seems to be really, you know, we don't like dealing with the prima donna programmer kind of thing, right? There's this, you know, I mean, not just programmers, right? We don't, also don't wanna deal with the prima donna reporters, or the prima donna illustrators, or the prima donna.

• 44:27Ed Zitron?

  We just wanna get rid of these people.

• 44:29Speaker 05

  Yeah, right.

• 44:30Ed Zitron?

  These annoying, they ask for stuff, they want money.

• 44:32Speaker 05

  Yeah, and days off, and sick leave, and, you know, healthcare, and.

• 44:38Ed Zitron?

  This is disgusting, how dare they? So it's frustrating as well because it across software development and everything, but especially with software developers feels just very insulting. Because it doesn't seem like this stuff. Actually, here's a better question. Have you seen much of an improvement with like oh, one oh, three, like these reasoning? Do you think the reasoning models change things for the better? And if so, how?

• 45:04Speaker 05

  Um, so. A little, um. They don't make as many stupid mistakes. Um, it is basically what it what it boils down to. Um, going back to your your first thing, though, right? I mean, so there was a piece, actually a couple of pieces recently. Um, one of them was about, you know, tech workers are just like the rest of us. They're miserable. Um, there was I'll I'll give you links to these. The other one was a Corey Doctorow piece that was like.

• 45:32Ed Zitron?

  Oh, yeah.

• 45:32Speaker 05

  The the future of um, Amazon coders is the present of Amazon warehouse workers or vice versa.

• 45:38Ed Zitron?

  Ah.

• 45:39Speaker 05

  Um, there's, there's a lot of, um, there has been a lot of deference given to software developers. Um, over time, because, you know, we have been kind of the the engine that's made a lot of the the the last 20, 30 years work. Um, and there's a desire to make that not so anymore, right? And to make us just as interchangeable as everybody else. Um, I I guess, you know, from a, from a economic standpoint, I kind of don't blame them. I understand why they're trying to do what they're doing. I don't. I mean, I I don't think that the warehouse workers should be treated the way the warehouse workers are treated. You know, much less everybody else gets treated that way. Um, and it it's been a lot worse since um, the giant layoffs at Twitter.

• 46:25Speaker 05

  Now X, um, when that happened and the thing didn't crash the in in completely burn like everybody was. Or not everybody, but a lot of people were expecting it to. The the sentiment became, well, maybe all this, all these software developers aren't as important as they. You know, we've always thought they were. Um, and, you know, we will see over time what the end result of that is. My guess is it's going to be end up being a mess. Um, but, you know.

• 46:55Ed Zitron?

  They had a server.

• 46:56Speaker 05

  I'm a I'm a software developer, right? I'm gonna, it it behooves me for it to be a mess, right? So it might just be my bias that's getting in the way.

• 47:04Ed Zitron?

  I actually, I think that you're right, though, because I remember back in 2021 and onward, the kind of post-remote work, the remote works, there was the whole anti-remote work push. But there was this, the whole quiet quitting and things like that, 2022, whereas like, software engineer, they're just, they're, they expect to be treated so well because 2021 saw the insane hiring. We saw tech companies like parking software workers. I think that played into it as well, where all of these companies who chose to pay these software engineers, they, they were the ones that made the offers, got pissed off that they'd done so and thought, we should cut all labor down to size. And then along comes coding. Almost makes me wonder if most of these venture capitalists talking about this don't know how

• 47:47Ed Zitron?

  to code themselves. You gotta wonder.

• 47:51Speaker 05

  I don't, I don't know many that do.

• 47:53Ed Zitron?

  Yeah.

• 47:54Speaker 05

  I, I know some that have at some point, but, um.

• 47:59Ed Zitron?

  But that's the thing, it's at some point, it's like, they're not part of modern software development culture, which I know sounds kind of wanky, but I mean, just how an organization builds software feels like something they should know. But then again, they don't know how to build a real organization either. So who the fuck?

• 48:15Speaker 05

  Yeah. Well, I mean, honestly, a lot of it, I, I've been in organizations that VCs basically killed.

• 48:23Ed Zitron?

  Right.

• 48:23Speaker 05

  Because, you know, we built a thing, that thing was, you know, a, a reasonable business, but VCs don't want a reasonable business. They want either 100x return or they want a tax write-off. And they don't want anything in between, right?

• 48:38Ed Zitron?

  Yeah.

• 48:38Speaker 05

  So, I mean, what, what they're looking for is really, I mean, they're, they're not trying to run a regular business, right? They're not trying to do the normal process. They're trying to, to either, you know, hit one out of the park or throw it away and move on. Um, and so they're, they're, the rules for them are different because what they're trying to accomplish is not what the rest of us are trying to accomplish as a general rule.

• 48:59Ed Zitron?

  Constant theme of the fucking show. It's just like, it's just like you have these people that don't code saying how coders should code. Like Dario Amade the other day saying that this year, we're going to have the first one-person software company with a billion dollars revenue or something like that. And it's just. I feel like there are some people who should not be allowed to speak as much sometimes. It's just frustrating and insulting and it's, but now that you've got me thinking about it, it does feel like this is an attempt to reset the labor market finally coming for software developers. And I don't mean finally in a good way.

• 49:32Speaker 05

  Right. I mean, it feels like that being in the, being in that, being in that industry at the moment, it really feels like that.

• 49:41Ed Zitron?

  Is it scary right now? Is it scary right now?

• 49:45Speaker 05

  Um, not for me, um, cause I'm old enough to be semi-retired, right? Um, but I, I mean, I've been talking to a lot of folks. Um, I've been having a, interviewing a bunch of folks that are, that are listeners to my channel and kind of trying to get a feel for what's going on. Um, and I've talked to folks that are, you know, like I said, that I talked to some folks that were like, you know, I work for a big bank, they're cramming Copilot down our throat whether we want it or not. Um, I've talked to some folks that are like, every time I sit down with my boss, I'm thinking that, you know, this is going to be the day that I'm going to find out that my, my group is getting cut the way the other three groups in, in the company is getting cut. There's a lot of, um, uh, artificial productivity, uh, requirement increases kind of thing, which is.

• 50:29Ed Zitron?

  Like, like what?

• 50:31Speaker 05

  Um, just, you know, we, you know, we expect more tickets closed per, you know, two week period than, you know, we've had before because we've, we're giving you this AI now. So you ought to be more productive, that kind of thing.

• 50:43Ed Zitron?

  Would a ticket necessarily be something that you just write code for? Or was it more than just that?

• 50:48Speaker 05

  Well, so generally it's more than just that, but, but generally the, the, the ticket, that's kind of the, the way that we track the work that we do.

• 50:57Ed Zitron?

  Right.

• 50:57Speaker 05

  In, in a lot of organizations, right? And some tickets are like, I'm building a new thing and those are kind of easier to predict. And some tickets are this thing isn't behaving right. Go figure out where the bug is, and those are a lot harder to predict. But they, they, they have these things, Agile has this, this thing called a velocity graph, where basically you see how many tickets per person get closed over time. And people want to see the slope of that, that line change because they're giving you AI.

• 51:23Ed Zitron?

  Wow. And I'm guessing the people telling you to change that don't know what they're talking about.

• 51:28Speaker 05

  That seems to be the case.

• 51:29Ed Zitron?

  Great.

• 51:31Speaker 05

  So I mean, the good news in theory, right? I don't know to what extent this is going to happen. But in theory, if you if they keep telling people, you know, that slope of that line should be changing because you have AI now. Over time, if we see the slope of that line not changing, right, then theoretically, it will be proof that the the AI is not providing the return that people expected.

• 51:56Ed Zitron?

  Or you're not using it right.

• 51:57Speaker 05

  Well, yes, there's always the you're not prompting it, right?

• 52:00Ed Zitron?

  That is, that is basically what I am. People, the one of the many reasons why you want is like, I want to have people that actually code on to talk about this stuff because it's really easy as a layman myself and for others to just be like, oh, but this does replace coding, right? And it does. It sounds like it really doesn't like it can help. It can be like a a force multiplier to an extent. But even past the initial steps, it just isn't there.

• 52:28Speaker 05

  Well, I mean, so the the best analogy I've always found to writing code is actually just writing. Right? I mean, you can get chat GPT to spit out a few paragraphs for you. Right? But, you know, you end up with, you know, the legal briefs that have the story that's made up or the, you know, just things that aren't connected to reality or stuff that, you know, when people read them, they're like, I mean, you've you you can tell the difference between AI slop generated, you know, like the the stupid, um, the the insert from the Chicago Sun-Times.

• 53:00Ed Zitron?

  Oh, yes, yes.

• 53:01Speaker 05

  The Philadelphia Inquirer, you know, about all the all the things you can do this summer, right? That like made up books and all that kind of, I mean, like, but even the even the articles that weren't the ones that were making up stuff, you read the, you know, this is what's going to be happening this summer. This is what the weather is going to be like or whatever. And you're reading and you're like, this, this, there's no like insight here. There's no thought here. There's no, you know, there, there's nothing in here that I I get to the end of this. I've read the whole thing. I understand the whole thing, but I don't have anything I can walk away with.

• 53:30Ed Zitron?

  Right. And I AI agents aren't coming along to replace software. But you're not scared of Devon?

• 53:37Speaker 05

  I am not scared of Devon. Um, so I, well, actually, I kind of am. I am scared that Devon is going to make a mess of things and then more things are going to get hacked. And that's going to end up being worse for everybody on the internet, right?

• 53:49Ed Zitron?

  How would it do that?

• 53:51Speaker 05

  By like we were talking about before, right? So when you write code that isn't secure. Right? And you write code that, you know, uses a library that's got an old version of a thing that they that there's a known bug in it, but you don't bother to check to see if there's a fix for that bug. Or you don't use best practices when it comes to writing code and that kind of thing. And or you don't think about the the kinds of maintainability issues that you're going to have. And you do things like you ship out code in a in a Internet of Things thing, a light bulb, right? Or a Internet Wi-Fi router that cannot be patched over the Internet that has a bug in it. Right? And now it's like that thing is going to have a bug in it forever.

• 54:35Speaker 05

  And you're going to have to find all of the ones on the on the earth and turn them off. Before someone's not going to be able to take them and be able to hack them and use them to attack somebody else from there.

• 54:44Ed Zitron?

  I mean, IOT is a huge problem.

• 54:46Speaker 05

  Oh, yeah.

• 54:47Ed Zitron?

  But the cheaper ones have like the spy web stuff and crypto mining. It just.

• 54:52Speaker 05

  But yeah, the ones the ones that have that have like really nasty vulnerabilities and they have no way of being updated once they leave the factory. Right? And it's just as long as they're out there, they're going to be a problem, literally for everybody on the Internet.

• 55:06Ed Zitron?

  Jesus. Well, what can, to wrap us up? What can a a new engineer, someone new to software development, what can they learn right now? You've kind of done a video on this, but I think it's a good place to wrap us up. What can they start learning to actually get ahead, to actually prepare for all of this?

• 55:23Speaker 05

  That's a really good question. So you can't these days. You can't really be able to be an engineer. You can't get hired as an engineer without some ability to talk about being able to do prompts and use. You know, some kind of AI code editor or that kind of thing. It's just an expectation of the job now, whether it should be or not, it's a different thing. The, I mean, like I said before. There are situations where you tell it what you want and it will type faster than you possibly can. So, you know, that's not necessarily bad. You need to understand that. You need to figure out, well, okay, I'll get back to something else. You need to figure out basically how to test the thing, right?

• 56:07Speaker 05

  So how do you make sure that the code that it spits out does what you meant it to do? And what I'm expecting is that we're going to spend more time thinking about testing and thinking more about, you know, trying to find exceptions and that kind of thing than we have in the past. Because the code that's actually being generated is going to be less likely to be quality than it was in the past.

• 56:25Ed Zitron?

  Right.

• 56:26Speaker 05

  The, the problem is it has become the case in the, in the programming industry that the things you need to do to get through the interview to get hired have very little resemblance to the things that you actually do on the job that you need to actually do a good job.

• 56:40Ed Zitron?

  Right.

• 56:41Speaker 05

  And so that's a, that's a whole different, we could probably have a whole other podcast episode just about the interviewing problem. But the, the main thing right now, it's so, right now, the whole hiring thing, and this isn't, I don't think, true for just programmers, but it's especially true for programmers, is all, you know, bots that customize your resume and write a custom cover letter and then send them over to the, the, the, submit the, the thing to the bot that's screening the resume and screening the cover letter, right? And that, getting it to the point where you can actually talk to a human is a nightmare right now. So the whole hiring system is kind of broken. So that, that actually getting to the point where you can get hired is a, is a nightmare at the moment.

• 57:24Speaker 05

  But the, the thing that you can do is figure out what kinds of things that AI are good at, is good at. And one of the things that AI is pretty good at is things that don't matter as much, right? So like, you know, AI can pick the layout of a site potentially, right? And you could have it pick two or three of them and you can basically do what's called an A B test. And you can randomly assign people to it. You could figure out which one of them performs better and you can throw the rest of them away, right?

• 57:51Ed Zitron?

  And even then, at some point, you will probably want the design customized.

• 57:55Speaker 05

  Yeah, I mean, but, but.

• 57:58Speaker 05

  I think there will be a lot of things where people can kind of get something that's kind of good enough to get started.

• 58:07Ed Zitron?

  Right.

• 58:08Speaker 05

  Right? And I think that to some extent, this is going to be kind of a boon for the industry in the longer term, where somebody who can't program right now, but who has some idea of kind of what they want, can do like a vibe coding thing. They can validate that the market that they want to try to attack exists, right? And that people want to use the kind of thing that they built. And then they can bring in somebody to actually build it right. You know what I mean?

• 58:33Ed Zitron?

  Yeah.

• 58:34Speaker 05

  And those kinds of things wouldn't necessarily have been able to happen in the complete absence of AI. So it's not, I don't think, completely useless. And there are times when, as a developer, there are things that we're not good at, like, you know, writing marketing copy and that kind of stuff. That if we're trying to do a project for ourselves, you know, a lot of that stuff, we can just outsource to the AI because it's not the thing that keeps the project from actually breaking and getting hacked and that kind of thing, right? So it's kind of like, there's this concept where you need to keep the things that are part of your competitive advantage in-house and everything else you can kind of outsource to somebody else. The kinds of things you can outsource to somebody else are the kinds of things that you potentially you could throw an AI at because they're not core.

• 59:15Ed Zitron?

  But even then, it's like, it doesn't seem like that's a ton of things right now or will be.

• 59:21Speaker 05

  Um, again, it's, it's the, so it's basically two things. It's things that were, the, the quality of the thing doesn't matter really. Right? Which every business has those kinds of things, right? And there are the kinds of things where you can define a metric that you can test the AI against and let it try over and over and over and over and over again until it gets to the point where it's good enough.

• 59:44Ed Zitron?

  Yeah.

• 59:44Speaker 05

  So if your metric is more people click on this button than The button before, right, then you can have the AI create a whole bunch of different ways to skin that button, right? And then you can say, okay, so the one that tested best is the one we're going to keep. That's the thing you can throw an AI at, right? Because you've got a well-defined way of checking in, no telling how long it's going to take, but you have a well-defined way of checking to see if it's working right or not.

• 1:00:09Ed Zitron?

  So, yeah. I mean, for years, I've had the theory that this industry was a 20 to 25 billion dollar total addressable market, pretending to be a trillion dollar one. And everything you're saying really suggests that it's like you're describing things like platform as a service, like, like, things that you use in tandem with very real people and intentional ideas.

• 1:00:30Speaker 05

  Yeah, this is, I don't see a world in which this is a, we replace all the humans, you know, the, the, the whole like, you know, this is going to displace 80% of the white collar workers in the world. I, I just, you know, the, the, the only, the only people that are really going to be replaced anytime soon are people that either weren't doing a great job to start with, or people whose bosses don't understand what they were doing to the point that the boss thought that what they were doing mattered. And my guess is that there's going to be regret at that point, and that at some point they're going to have to bring those people back.

• 1:01:07Ed Zitron?

  Well, Cole, this has been such a wonderful conversation. Where can people find you?

• 1:01:13Speaker 05

  I am internetofbugs at YouTube is probably the easiest place to find me. And then there are links on that, that channel to point to other things.

• 1:01:21Ed Zitron?

  And you've been listening to me, Ed Zitron. You've been listening to Better Offline. Thank you, everyone, for listening. And yeah, we'll catch you next week. Thank you for listening to Better Offline. The editor and composer of the Better Offline theme song is Matt Osowski. You can check out more of his music and audio projects at mattosowski.com, M A T T O S O W S K I dot com. You can email me at [email protected] or visit betteroffline.com to find more podcast links and of course my newsletter. I also really recommend you go to chat dot where's your ed dot at to visit the Discord and go to r slash better offline to check out our Reddit.

• 1:02:06Ed Zitron?

  Thank you so much for listening.

• 1:02:08Speaker 03

  Better Offline is a production of Cool Zone Media. For more from Cool Zone Media, visit our website, coolzonemedia.com, or check us out on the iHeart Radio app, Apple Podcasts, or wherever you get your podcasts.

• 1:02:40Speaker 02

  Empower is all about helping you invest well, so you can go out and live a little. And their free Empower Personal Dashboard shows you your full financial life in one place. You'll be able to see your net worth, monitor budgets, analyze your portfolio, set retirement goals, and more. Whether you're saving for something big, want to treat yourself, friends, or family, or meet long-term goals, Empower helps you see where you stand. You've worked hard for your money, and Empower can help you make the most of it. Download the Empower Personal Dashboard or visit empower.com. Not an Empower client paid or sponsored.

• 1:03:11Speaker 01

  Cash flow crunch? OnDeck's small business line of credit gives your business immediate access to funds up to $200,000 right when you need it. Cover seasonal dips, manage payroll, restock inventory, or tackle unexpected expenses without missing a beat. With flexible draws, transparent pricing, and control over repayment, get funded quickly and confidently. Apply today at ondeck.com. Funds could be available as soon as tomorrow. Depending on certain loan attributes, your business loan may be issued by OnDeck or Celtic Bank. OnDeck does not lend in North Dakota. All loans and amounts subject to lender approval.

• 1:03:42Speaker 07

  She's been thinking about this sleepover all week, but I think about her food allergies all the time. Fortunately, her doctor prescribed Zolair, omalizumab. It's proven to significantly reduce allergic reactions if a food allergy accident happens. Zolir 150mg is a prescription medication used to treat food allergy in people one year of age and older to reduce allergic reactions due to accidental exposure to one or more foods. While taking Zolir, you should continue to avoid all foods to which you are allergic. Don't use if you are allergic to ZOLAR may cause a severe, life-threatening allergic reaction called anaphylaxis. Tell your doctor if you ever had anaphylaxis. Get help right away if you have trouble breathing or if you have swelling of your throat or tongue. ZOLAR should not be used for the emergency treatment of allergic reactions, including anaphylaxis. ZOLAR is for maintenance use to reduce allergic reactions, including anaphylaxis, while avoiding food allergens.

• 1:04:27Speaker 07

  Serious side effects such as cancer, fever, muscle aches and rash, parasitic infection, or heart and circulation problems have been reported. Please see zolar.com for full prescribing information. Ask an allergist about ZOLAR. This is an advertisement for ZOLAR, paid for by Genentech and Novartis.

• 1:04:42Speaker 00

  This is an iHeart Podcast. Guaranteed Human.