The Truth About Software Development with Carl Brown

Summary

Podcast Summary: Better Offline – "The Truth About Software Development with Carl Brown"

Podcast Information:

• Title: The Truth About Software Development with Carl Brown
• Host: Ed Zitron (Cool Zone Media and iHeartPodcasts)
• Guest: Carl Brown, Veteran Software Engineer and Host of the YouTube Channel Internet of Bugs
• Release Date: June 4, 2025

---

1. Introduction

In this episode of Better Offline, host Ed Zitron engages in a comprehensive discussion with Carl Brown, a seasoned software engineer and the mind behind the popular YouTube channel Internet of Bugs. The conversation delves deep into the intricacies of software development, the evolving role of developers, and the burgeoning influence of Artificial Intelligence (AI) and Large Language Models (LLMs) in the tech industry.

---

2. Understanding the Role of a Software Developer

Ed initiates the conversation by seeking clarity on the true nature of a software developer’s role.

• Carl Brown [03:08]:
  “We take ideas about problems that people want to solve and write software, code that tells computers instructions to solve those problems.”

Ed probes further, questioning how much of a developer’s job is actual code writing.

• Carl Brown [03:47]:
  “It depends on how good the people that are asking for stuff is. As a general rule, maybe between 10% and 25%.”

Ed emphasizes that even at the higher end, coding constitutes a minority of the role, highlighting that the bulk involves problem-solving, communication, and system design.

---

3. The Impact of AI and LLMs on Software Development

Ed raises concerns about the prevalent narratives suggesting that AI and LLMs might render software engineers obsolete.

• Ed Zitron [04:34]:
  “There have been a lot of stories around LLMs replacing coders... How much validity is there in that?”

Carl Brown provides a nuanced perspective:

• Carl Brown [04:51]:
  “LLMs can assist fresh graduates by handling small chunks of work, but they lack the ability for long-term thinking essential for complex projects.”

He underscores the limitation of LLMs in maintaining context over extended projects, a crucial aspect where human developers excel.

---

4. Challenges with AI-Generated Code

The conversation shifts to the practical challenges posed by AI-generated code. Carl Brown highlights several issues:

• Redundancy and Inconsistency:
  “LLMs tend to generate repetitive code blocks that differ slightly each time, making debugging a nightmare.” [07:28]

• Security Vulnerabilities:
  “AI-generated code often lacks robust security measures, leading to potential vulnerabilities.” [16:43]

Carl references studies indicating increased Code Churn—frequent changes to code after initial deployment—suggesting deteriorating code quality with the integration of tools like GitHub Copilot.

• Carl Brown [17:09]:
  “Since implementing GitHub Copilot, Code Churn has significantly increased across millions of lines of code on GitHub.”

This surge in code modifications implies that AI-generated code may require more oversight and revision, contrary to the promise of enhanced productivity.

---

5. Agile Methodology and Its Effects on Software Quality

Carl provides insights into Agile methodologies, explaining both their benefits and unintended consequences.

• Carl Brown [33:27]:
  “Agile allows for flexibility by focusing on short-term sprints, but it can lead to a lack of long-term planning and understanding.”

Ed echoes these sentiments, noting that perpetual focus on short-term goals can obscure overarching project objectives and impede comprehensive problem-solving.

---

6. The Future of Software Development

The discussion explores the broader implications of AI integration on the software development landscape.

• Carl Brown [38:21]:
  “Organizations may face a backlash as AI-generated code introduces vulnerabilities, necessitating extensive cleanup efforts in the future.”

Ed draws parallels with historical tech bubbles, suggesting that the AI-driven transformation in software development might culminate in a significant industry upheaval akin to the crypto bubble.

• Carl Brown [40:37]:
  “We might see a push to clean up AI-generated code vulnerabilities in a few years, similar to the delayed collapse of the crypto bubble.”

The conversation also touches upon management practices that prioritize short-term gains over sustainable development, exacerbated by AI’s superficial enhancements.

---

7. Advice for New Engineers

As the episode nears its conclusion, Ed seeks Carl’s guidance for aspiring software developers navigating this evolving landscape.

• Carl Brown [59:29]:
  “New engineers should focus on mastering AI tools to enhance their productivity while honing skills in testing and debugging AI-generated code.”

He emphasizes the importance of understanding AI's strengths and limitations, advocating for a symbiotic relationship where AI acts as a force multiplier rather than a replacement.

---

8. Conclusion

Ed wraps up the episode by reflecting on the critical takeaways from his conversation with Carl Brown. The integration of AI and LLMs in software development presents both opportunities and challenges. While AI can expedite certain aspects of coding, the essence of software engineering—long-term planning, contextual understanding, and robust problem-solving—remains irreplaceable by current AI capabilities.

Carl Brown’s insights serve as a cautionary tale for the tech industry, urging a balanced approach to AI adoption that preserves the foundational values of software development. Aspiring and current developers alike are encouraged to embrace AI as a tool for augmentation rather than a threat to their professional roles.

---

Notable Quotes:

• “Most software development is about communicating with people and understanding problems, not just writing code.” – Carl Brown [03:39]

• “LLMs lack the ability for long-term thinking essential for complex projects.” – Carl Brown [04:51]

• “AI-generated code often lacks robust security measures, leading to potential vulnerabilities.” – Carl Brown [16:43]

• “Agile allows for flexibility by focusing on short-term sprints, but it can lead to a lack of long-term planning and understanding.” – Carl Brown [33:27]

• “New engineers should focus on mastering AI tools to enhance their productivity while honing skills in testing and debugging AI-generated code.” – Carl Brown [59:29]

---

Listeners are encouraged to explore more insights from Carl Brown on his YouTube channel Internet of Bugs and stay updated with future episodes of Better Offline for in-depth analyses of the tech industry's influence on society.

Transcript

[iHeart Podcast]

This is an iHeart podcast.

[Oracle Representative]

AI is rewriting the business playbook with productivity boosts and faster decision making coming to every industry. If you're not thinking about AI, you can bet your competition is this is not where you want to drop the ball, but AI requires a lot of compute power and with most cloud platforms, the cost for your AI workloads can spiral. That is, unless you're running on oci. Oracle Cloud Infrastructure this was the cloud built for AI, a blazing, fast, enterprise grade platform for your infrastructure, database, apps and all your AI workloads. OCI costs 50% less than other major hyperscalers for compute, 70% less for storage and 80% less for networking. Thousands of businesses have already scored with oci, including Vodafone, Thomson Reuters and sunoai. Now the ball's in your court.

[Carl Brown]

Right now, Oracle can cut your current cloud bill in half if you move to OCI. Minimum financial commitment and other terms apply. Offer ends March 31st. See if your company qualifies for this special [e-mail] strategic that's oracle.com strategic strategic.

[Ed Zitron]

Are you still quoting 30 year old movies? Have you said cool beans in the past 90 days? Do you think Discover isn't widely accepted? If this sounds like you, you're stuck in the past. Discover is accepted at 99 of places that take credit cards nationwide and every time you make a purchase with your card, you automatically earn cash back. Welcome to the now it pays to Discover. Learn [e-mail] credit card based on the February 2024 Nielsen report this season, let.

[Carl Brown]

Your shoes do the talking. Designer Shoe Warehouse is packed with fresh styles that speak to your whole vibe without saying a word. From cool sneakers that look good with everything. The easy sandals you'll want to wear on repeat. DSW has you covered. Find a shoe for everywhel from the brands you love like Birkenstock, Nike, Adidas, New Balance and more. Head to your DSW store or visit dsw.com today. Pro Paint Days are back at Lowes and Mylo's Pro Rewards. Members can save even more with limited time deals right now. Buy one, get one half off Select HGTV Home by Sherwin Williams Primer and Ceiling Paint. Plus get free same day delivery to your job site when you order by 2pm Offer valid through 6 13. Delivery by 8pm Subject to driver availability. Additional terms apply. C loads.com SameDay Delivery for details.

[Zone Media]

Call Zone Media.

[Ed Zitron]

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

Better Offline.

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.

[Carl Brown]

Thanks for having me.

[Ed Zitron]

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

[Carl Brown]

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 asked us to solve.

[Ed Zitron]

Right.

[Carl Brown]

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

[Ed Zitron]

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

[Carl Brown]

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

[Ed 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.

[Carl Brown]

Right now that's largely for folks that are farther up the chain. Right?

[Ed Zitron]

Right.

[Carl Brown]

So if you're fresh out of school and you don't really, you're not in the job, 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 far, far more talking to people and stuff than actually writing code.

[Ed Zitron]

Right. The reason I ask that and the reason we're doing this as well is that there have been a lot of stories around 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?

[Carl Brown]

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 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?

[Ed Zitron]

Right.

[Carl Brown]

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 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.

[Ed Zitron]

So I think that, I think that I've noticed 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 on, that these companies will be writing all of their code with AI, and it doesn't even seem like that is possible. One of your videos, you did a really good thing around like the 20 to 30%. I'll link to this in the notes. 20 to 30% of code that behind Meta and I think Google it was, is written by AI. Now again, how much validity is there to that?

[Carl Brown]

Well, I mean, so if 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, Right. 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. I mean, 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, right.

[Ed Zitron]

In my, in my case, absolutely nothing. But that's just because 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 to 30% of the code is written by. But there's no verifying this. 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 if you don't know why that was written because you had something generate it, is that not a huge problem?

[Carl Brown]

Yes. But worse, 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.

[Ed Zitron]

Can you give me an example?

[Carl Brown]

So, for example, when you need to go fetch a thing from a server. Right. Well, 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. 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?

[Ed Zitron]

Right.

[Carl Brown]

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. Now 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.

[Ed Zitron]

Right. Also, isn't there a security issue of having large language models? 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?

[Carl Brown]

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.

[Ed Zitron]

Right. And so what are they actually? What are these large language model coding tools actually good for? Because 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. I'm just truly what's useful about them.

[Carl Brown]

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.

[Ed Zitron]

Like autocorrect.

[Carl Brown]

Basically, yes. It's like autocomplete 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. 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.

[Ed Zitron]

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

[Carl Brown]

Yeah, it's like, 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 I use it kind of like a Google Translate kind of thing to go from one programming language to another sometimes.

[Ed Zitron]

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

[Carl Brown]

Oh, not at all.

[Ed Zitron]

Why not?

[Carl Brown]

Well, it wouldn't work to start with.

[Ed Zitron]

Why wouldn't it work?

[Carl Brown]

Well, I mean, so I've done some experimentation on that where I've taken fairly complicated 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 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, a lot of examples for. It does. Okay. Past the point where you're in the really simple kind of language things, they sometimes get to the point where they can't even create anything that builds at all.

[Ed Zitron]

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

[Carl Brown]

Honestly, I'm not sure to what extent the engineers are swearing by it. 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, 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 interesting.

[Ed Zitron]

So it's executive. I've, I've personally had this theory that it's like executive pushed and that it's all about what the bosses want to see rather than even do. Sorry to move my cat out the way.

[Carl Brown]

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 or close to is just as good as the programmers and not nearly as annoying.

[Ed 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.

[Carl Brown]

Yeah, I mean, those terms get.

[Ed Zitron]

Mashed together.

[Carl Brown]

Yeah. I mean, so part of the Problem is that I live in Texas. And in Texas you're not allowed to call yourself an engineer unless you've passed the engineering exam. Right. So 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, like the terms get all confused.

[Ed Zitron]

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

[Carl Brown]

Well, I mean, so one of it is what you said earlier, which is that a very small percentage of 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, the solution to the problem that you're trying to solve. Another thing is that a lot of 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, 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, right. 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.

[Ed 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'll 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 your videos. Definitely talk about this as well, actually. How to develop software and make sure it works and make sure that 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.

[Carl Brown]

Yes, although 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 basically a senior or a mid level developer 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.

[Ed 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 know how to grow within their job.

[Carl Brown]

Yeah, I mean 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 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 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 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?

[Ed Zitron]

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

[Carl Brown]

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

[Ed 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?

[Carl Brown]

Yeah. So basically what that study found, there have been a couple of them, but what that particular study found is that there's what they call Code Churn has gone up. And Code Churn is basically when you push something, you add a line of code, you push it into test or to production, and then in a short period of time, like, I don't remember exactly what 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're not happy with that. We're going to change it to be something else. Right, right. And the percentage of lines or the number of lines that get changed fairly quickly after they get submitted has gone way up since the implementation of GitHub Copilot. And this is across like most of the giant, you know, millions of lines of codes on GitHub.

[Ed Zitron]

And first, simpleton me, why does it being changed? Why is changing it so often bad?

[Carl Brown]

Like, well, I mean, so I mean, if you do it right the first time, you can move on to the next thing. Ah, 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 you're in, in Google Docs and you're like tracking changes and it's like, okay, this sentence has changed times. Obviously the person isn't happy with the way that sentence is. Right.

[Ed Zitron]

So the generative code isn't good.

[Carl Brown]

Right.

[Ed Zitron]

And so people see need to change it.

[Carl Brown]

That's the presumption.

[Trey Farrow]

Yes.

[Ed 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.

[Carl Brown]

So they measured that. They measured.

[Ed Zitron]

Like moved code? Yeah, less moved code.

[Carl Brown]

The thing I was talking about earlier, where you've got a bunch of different places in the code that all do the same, try to do the same function, but they do it in different ways. Normally what would happen is you do a thing here and then at some point in the future you need to do that thing again in a different place. 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 place right?

[Ed Zitron]

Because it already works right?

[Carl Brown]

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. Ryan Reynolds here from Mint Mobile. I don't know if you knew this, but anyone can get the same Premium Wireless for $15 a month plan that I've been enjoy enjoying. It's not just for celebrities. So do like I did and have one of your assistant's assistants switch you to Mint Mobile today. I'm told it's super easy to do.

[Zone Media]

@Mintmobile.Com Switch upfront payment of $45 for 3 month plan equivalent to $15 per month Required intro rate first 3 months only, then full price plan options available, taxes and fees extra fee full [e-mail].

[Ryan Reynolds]

Trust isn't just earned, it's demanded. Whether you're a startup founder navigating your first audit or a seasoned security professional scaling your gr, proving your commitment to security has never been more critical or more complex. That's where Vanta comes in. Businesses use Vanta to establish trust by automating compliance needs. Over 35 frameworks like SOC2 and ISO 27001 centralize security workflows, complete questionnaires up to five times faster, and proactively manage vendor risk. Vanta can help you start or scale your security program by connecting you with auditors and experts to conduct your audit and set up your security program quickly. Plus, with automation and AI throughout the platform, Vanta gives you time back so you can focus on building your company. Join over 9,000 global companies like Atlassian, Quora and Factory who use Vanta to manage risk and prove security in real time. For a limited time, our audience gets $1,000 off [e-mail] special. That's V-A N T A.com special for $1,000 off.

[Carl Brown]

Think advertising on TikTok isn't for your business? Think again. We've generated over 100,000 DOL, which has converted into over 40,000 sales for our pet insurance policies. My name is Trey Farrow. I am the CEO of spot pet insurance, TikTok smart plus AI powered automation takes the guesswork out of targeting, bidding and optimizing creative. If I can advertise on TikTok, you can too. Drive more leads and scale your business. Today only on TikTok. Head over to get started.TikTok.com TikTok ads.

[iHeart Podcast]

It'S Wednesday night after a long day and the last thing you want to do is cook dinner from scratch. But you still want a satisfying, tasty meal without the guilt. Enter your freezer's sidekick, caulifwr. From thin and crispy cauliflower crust pizzas to all natural white meat chicken tenders and crowd pleasing snacks, Cauliflower satisfies every craving. Cauliflower's products are your favorite comfort foods but made better for you and gluten free. Always the best part. You don't have to sacrifice taste or time so you can honor your cravings without compromising craving. Pizza. You can enjoy Cauley Power's delicious Margherita Pizza for only 370 calories for half the pizza. Looking for easy snacks that kids and adults alike will love, Cauli Power's Baked Never Fried pizza snacks are nostalgia reimagined and ready in five minutes. CauliPower's products are available in freezer aisles nationwide. Visit eatcollipower.com wheretobuy to find a store near you.

[Ed Zitron]

So for the audience as well, how does the 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.

[Carl Brown]

Yeah. 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, look at this. Or that kind of thing, right? And the pull request is kind of the unit of work kind of.

[Ed Zitron]

So with GitHub you almost use it like an organizational code dump or where you centralize all the code. Sorry, just for the. For me. And 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. Well, 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 software's 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. And I don't even mean coding. I mean it's the intentionality behind software design and infrastructure and maintenance. It seems like they're removing intention in multiple parts.

[Carl Brown]

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 typing, basically. And that all of the work that we do to understand what the problem actually is and how it needs to work and 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.

[Ed Zitron]

And I mean, I'm going to 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.

[Carl Brown]

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, 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 know, if it, if it, if it looks like kind of what you wanted, that probably it's going to be fine or hopefully it's going to be fine.

[Ed Zitron]

How do you feel about vibe coding?

[Carl Brown]

So I do it. Sometimes vibe coding is great for a thing that you're going to do once and then throw away. Yeah. Right. So if it's like, you know, okay, I want to do a thing, I want to translate this thing to, you know, I want to 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.

[Ed Zitron]

Like a prototype, almost.

[Carl Brown]

Yeah, basically. And so, you know, we call them spikes or tracer bullets. Sometimes it's like a, you know, let me get a thing that works at all. Right. And then let me see what I can learn from that 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 not crash. It's a really bad idea.

[Ed 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.

[Carl Brown]

Yeah. And the other thing is that there's an adversarial component. Right. People will intentionally try to go hack that thing that's sitting on the Internet. Oh, right. In a way that they don't intentionally try to go mess with the story that you wrote. Right, 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.

[Ed Zitron]

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

[Carl Brown]

Some people are, yeah. I mean, to be honest, a lot of companies have just started been getting rid of quality assurance over the years. Right.

[Ed Zitron]

Oh, really?

[Carl Brown]

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, what do they call them? Hackathon kind of things. They didn't call them that. I don't know 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. 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.

[Ed Zitron]

When did that movement happen?

[Carl Brown]

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

[Ed Zitron]

Right.

[Carl Brown]

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

[Ed Zitron]

Folks really just feels like it's the management problem as well. It's the management company people, I would think. So it's a real shame as well. And 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.

[Carl Brown]

Well, that's my expectation. Right?

[Ed Zitron]

Yeah. Just a potential worry.

[Carl Brown]

Right, right. So the more of this we get and the more issues that we have, the more stuff we're going to have to dig out of. Right. And what I'm honest 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 going to be before this one does. But I'm expecting that there's going to 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 has all of these vulnerabilities that nobody's bothering to check for at the moment.

[Ed 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.

[Carl Brown]

So 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. You know, 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, right. And even then, sometimes people come up with novel ways of making something not secure.

[Ed Zitron]

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

[Carl Brown]

Well, I mean, 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 right. You have to make sure that it doesn't have the opportunity to be able to write to places on your disk that it shouldn't be able to write to. You have to be able to make sure that it doesn't have access to read data that it shouldn't be able to read, you know, all that kind of stuff. 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. 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.

[Ed Zitron]

Even, even like, I think it was what the big target data breach from a while back was through the H Vac system. It's just. Except now we've got. And that was with humans writing the code, right? Imagine if we didn't know. Oh God, it really does feel like the, the young people are going like the. Actually, no, 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 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.

[Carl Brown]

Yes. I mean, there's an argument that says we never got it right in the first place. But 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, relatively speaking, in our infancy as an industry. It's been a constant evolution and a lot of times the things that we did to solve a problem that we had ended up causing other problems. So going back to Agile in the long, long ago we used to manage software projects the same way we managed build bridge building and building progress construction projects. 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. 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, right. 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 who time. And so they created this thing called the Agile methodology. I'm drastically simplifying. There were steps in the middle, but basically. So 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 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 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. 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. 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?

[Ed 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.

[Carl Brown]

Is 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, the length of the project so they can get more money out of it. Right, right, that's, that's always the case. But the other thing is that you end up with a real, a lot of times you end up with a real lack of like long term planning and long term understanding. Right, right. Because 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 things that you look at tend 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, we didn't think about this, what do we do? Problem. Yeah.

[Ed Zitron]

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

[Carl Brown]

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

[Ed Zitron]

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

[Carl Brown]

It's most places. There are some places that are 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.

[Ed Zitron]

Thing and in the big. So this is something you'd seen like a Google and an Amazon as well?

[Carl Brown]

Oh, absolutely.

[Ed Zitron]

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

[Carl Brown]

Largely, yes. So those organizations tend to be. Well, those organizations historically have tended to be. Before the recent initiatification wave. I'm assuming I can swear on this.

[Ed Zitron]

Yeah, yeah, yeah. Fuck. Shit, it's all fine.

[Carl Brown]

Those organizations have historically been fairly more engineering driven, which means that, you know, 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 make sure everybody's on the same page and that kind of stuff. A lot. Not all, but a lot of problems can get lessened if you have people in the organization that are at higher level whose job is not to manage people, but whose job is basically to keep track and core coordinate between different groups that are doing different technical things.

[Ed 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.

[Carl Brown]

Yeah. And that 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.

[Ed Zitron]

Yes. So based on my analyses of these companies, that's definitely gone out there, the window. I mean, even with LLM integration. So there was a Johnson and Johnson story that went out Wall Street Journal a couple weeks ago where it was like they had 890llm generative AI projects of which 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 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 boxes.

[Carl Brown]

Yeah, I mean, so the other thing. So understand that. Again, greatly oversimplifying a lot of the new stuff that's happened with 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 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. That hasn't seemed to really pan out the last couple of years from what I can see, but 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, well, our competitors are probably doing this and so we don't want to get left behind. It kind of reminds me of the rumors that they talked about back in the 80s when the CIA 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.

[Ed Zitron]

LL MK Ultra.

[Carl Brown]

Exactly, yes.

[Ed Zitron]

Title of the episode.

[Trey Farrow]

You're great at protecting your own personal information. You probably even use things like two factor authentication, strong passwords and a vpn. But as much as you try to be in control of how your information is protected, there are lots of places that also have it and they might not be as careful as you are. That's why LifeLock monitors millions of data points every second for identity threats. If your identity is stolen, a LifeLock US based restoration specialist list will help solve identity theft issues on your behalf, guaranteed or your money back. Plus, all LifeLock plans are backed by the million dollar protection package, meaning LifeLock will reimburse you up to the limits of your plan if you lose money due to identity theft. You might not be able to control how others handle your personal information, but you can help protect it with LifeLock. Save up to 40% your first year. Call 1-800-LIFELOCK and use promo code IHEARTRA IHEART or go to lifelock.com iheart for 40% off.

[iHeart Podcast]

Terms apply it's Wednesday night after a long day and the last thing you want to do is cook dinner from scratch. But you still want a satisfying, tasty meal without the guilt. Enter your freezer's sidekick Caulipwer. From thin and crispy cauliflower crust pizzas to all natural white meat, chicken tenders and crowd pleasing snacks, Cauliflower satisfies every craving. Cauliflower's products are your favorite comfort food foods but made better for you and gluten free. Always the best part. You don't have to sacrifice taste or time so you can honor your cravings without compromising craving. Pizza. You can enjoy Caulifower's delicious Margherita pizza for only 370 calories for half the pizza. Looking for easy snacks that kids and adults alike will love. Cauli Power's baked never fried pizza snacks are nostalgia reimagined and ready in 5 minutes. Minutes. Cauliflower's products are available in freezer aisles nationwide. Visit eatcaulypower.com where to buy to find a store near you.

[Ed Zitron]

Hello, it is Ryan and we could all use an extra bright spot in our day, couldn't we? Just to make up for things like sitting in traffic, doing the dishes, counting your steps. You know all the mundane stuff. That is why I'm such a big fan of Chumba Casino. Chumba Casino has all your favorite social casino style games that you can play for free. Free anytime, anywhere with daily bonuses. So sign up [e-mail] that's chumbacasino.com no.

[Carl Brown]

Purchase necessary VGW Group void. We're prohibited by law 21/ terms and conditions apply.

[Zone Media]

Now I'd like to introduce you to Meaningful Beauty, the famed skincare brand created by iconic supermodel Cindy Crawford. It's her secret to absolutely gorgeous skin Meaningful Beauty makes powerful and effective skin care simple and it's less loved by millions of women. It's formulated for all ages and all skin tones and types. And it's designed to work as a complete skin care system, leaving your skin feeling soft, smooth and nourished. I recommend starting with Cindy's full regimen which contains all five of her best selling products including the amazing Youth Activating Melon Serum. This next generation serum has the power of melon leaf stem cell technology. Its melon leaf stem cells encapsulated for freshness and release onto the skin to support a visible reduction in the appearance of wrinkles. With thousands of glowing five star reviews, why not give it a try? Subscribe today and you can get the Amazing Meaningful Beauty system for just $49.95. That includes our introductory five piece system, free gifts, free shipping and a 60 day money back guarantee. All of that available@meaningful beauty.com.

[Ed Zitron]

So, okay, LMK 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 shove the shit in there. This seems like it's an important thing, right? Or is this, are you seeing it within software development?

[Carl Brown]

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 going to do next year and how many headcount do we think that's going to save us and that kind of thing. Right? There are some companies, Duolingo is one, Klarna is one. Bp, the former British Petroleum, what last year had a thing where they said they were cutting 70% of their contract.

[Ed Zitron]

Software developers and in most of these they've kind of rolled them back as well.

[Carl Brown]

I don't think Duolingo has yet.

[Ed Zitron]

No. This is just being unfair to you. They like a day ago really just like ah, we're kind of. 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 do stuff.

[Carl Brown]

Yeah.

[Ed 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, is highly contextual. Unless you're like in the earlier days.

[Carl Brown]

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

[Ed Zitron]

Yeah. Well, 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.

[Carl Brown]

So 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 going to find is that you remember, 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 piled on instructions piled 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 going to bother 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 going to 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 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.

[Ed Zitron]

Yeah. And at that point you could train a person.

[Carl Brown]

Yes. I mean, the person would probably be more Annoying. A lot of this seems to be really. We don't like dealing with the prima donna programmer kind of thing. Right. There's this. I mean, not just programmers, right. We also don't want to deal with the prima donna reporters or the prima donna illustrators or the prima donna get.

[Ed Zitron]

Rid of these people.

[Carl Brown]

Right.

[Ed Zitron]

He's annoying. They ask for stuff. They want money.

[Carl Brown]

Yeah. And days off and sick leave and, you know, health care and this is disgusting. How dare. It's.

[Ed Zitron]

It's 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 0103, like these reasoning. Do you think the reasoning models change things for the better? And if so, how so?

[Carl Brown]

A little they don't make as many stupid mistakes is basically what it boils down to. Going back to your first thing though, right? I mean, so there was a piece, actually a couple pieces recently. One of them was about tech workers are just like the rest of us. They're miserable. I'll give you links to these. The other one was a Cory Doctorow piece that was like, the future of Amazon coders is the present of Amazon warehouse workers, or vice versa. There has been a lot of deference given to software developers over time because we have been kind of the engine that's made a lot of the last 20, 30 years work. And there's a desire to make that not so anymore. Right. And to make us just as interchangeable as everybody else. I guess from a economic standpoint, I kind of don't blame them. I understand why they're trying to do what they're doing. I mean, I don't think that the warehouse workers should be treated the way the warehouse workers are treated. Much less everybody else gets treated that way, way. And it's been a lot worse since the giant layoffs at Twitter. Now X when that happened and the thing didn't crash and completely burn like everybody was, or not everybody, but a lot of people were expecting it to, the sentiment became, well, maybe all these software developers aren't as important as they, you know, we've always thought they were. And you know, we will see over time what the end result of that is. My guess is it's going to end up being a mess. But, you know, I'm a software developer, right. I'm gonna. It behooves me for it to be a mess, right. So it might just be My bias that's getting in the way.

[Ed 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 work, there was the whole anti remote work push, but there was this, the whole quiet quitting and things like that. 2022. Whereas like software engineering, they're just, they expect to be treated so well because 2021 saw the insane hiring. You 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 were the ones that made the offer, 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 to code themselves. You gotta wonder.

[Carl Brown]

I don't know many that do. Yeah, I know some that have at some point, but that's the thing, at.

[Ed Zitron]

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?

[Carl Brown]

Yeah, well, I mean, honestly, a lot of it I've been in organizations that VCs basically killed because, you know, we built a thing, that thing was, you know, 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?

[Ed Zitron]

Yeah.

[Carl Brown]

So I mean what they're looking for is really, I mean, they're not trying to run a regular business, right? They're not trying to do the normal process. They're trying to either hit one out of the park or throw it away and move on. And so 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.

[Ed Zitron]

Constant theme of the fucking show. It's just like you have these people that don't code saying how coders should code, like Dario Amadei 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. But 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 market finally coming for software developers. And I don't mean finally in a good way.

[Carl Brown]

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

[Ed Zitron]

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

[Carl Brown]

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

[Ed Zitron]

Like what?

[Carl Brown]

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

[Ed Zitron]

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

[Carl Brown]

Well, so generally it's more than just that, but generally the ticket, that's kind of the way that we track the work that we do 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 have these things. Agile has this thing called a velocity graph where basically you see how many tickets per person get closed over time. And people want to see this of that line change because they're giving you.

[Ed Zitron]

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

[Carl Brown]

That seems to be the case.

[Ed Zitron]

Great.

[Carl Brown]

The good news in theory, right. I don't know to what extent this is going to happen. But in theory, if they keep telling people the 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 AI is not providing the return that people expected.

[Ed Zitron]

Or you're not using it, right?

[Carl Brown]

Well, yes, there's always that. You're not prompting it, right?

[Ed Zitron]

That is basically what I am, people. One of the many reasons I want you on 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 sounds like it really doesn't. Like, it can help. It can be like a force multiplier to an extent, but even past the initial steps, it just isn't there.

[Carl Brown]

Well, I mean, so the best analogy I've always found to writing code is actually just writing, right? I mean, you can get ChatGPT 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've, you can tell the difference between AI slop generated, you know, like the, the stupid, the. The insert from the Chicago Sun Times, the Philadelphia Inquirer, you know, all the things you can do this summer, right, that, like, made up books and all that kind of. I mean, like. But even, even the articles that weren't the ones that were making up stuff, you read the. This is what's gonna be happening this summer. This is what the weather's gonna be like or whatever. And you're reading and you're like, there's no, like, insight here. There's no thought here. There's no, you know, there's nothing in here that 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, right?

[Ed Zitron]

And AI agents aren't coming along to replace software development. You're not scared of Devin.

[Carl Brown]

I am not scared of Devin. Devin. So I. Well, actually, I kind of am. I am scared that Devin 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?

[Ed Zitron]

How would it do that?

[Carl Brown]

By. I mean, 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, a fix for that bug, or you don't use best practices when it comes to writing code and that kind of thing, or you don't think about the kinds of maintainability issues that you're going to have. And you do things like you ship out code in an Internet of Things thing, a light bulb or 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 and you're going to have to find all of the ones 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.

[Ed Zitron]

I mean, Iot is a huge problem. The cheaper ones have the spyware stuff.

[Carl Brown]

And crypto mining, but yeah, the ones that have 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.

[Ed Zitron]

Jesus. Well, what can, to wrap us up? What can. 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?

[Carl Brown]

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 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 is a different thing. Like I said before, there are situations where you tell it what you want and it will type faster than you possibly can. So 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? 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, 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. Right. 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. 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. But the main thing right now, right now, the whole hiring thing, and this is, I don't think true for just programmers, but it's especially true for programmers, is all bots that customize your resume and write a custom cover letter and then send them over to submit the thing to the bot that's screening the resume and screening the COVID 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 the actually getting to the point where you can get hired is a nightmare at the moment. But the thing that you can do is figure out what kinds of things that AI 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 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. You can figure out which one of them performs better and you can throw the rest of them away.

[Ed Zitron]

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

[Carl Brown]

Yeah, I mean, but. But 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. Right, 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 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? 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 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 you potentially you could throw an AI at because they're not.

[Ed Zitron]

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

[Carl Brown]

It's basically two things. It's things that the quality of the thing doesn't matter really, which every business has those kinds of things. Right. And they're 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. So if your metric is more people, 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 and 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.

[Ed Zitron]

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

[Carl Brown]

Yeah, this is, I don't see a world in which this is a. We replace all the humans. You know, the whole like, you know, know this is going to displace 80% of the white collar workers in the world. I just, you know, 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.

[Ed Zitron]

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

[Carl Brown]

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

[Ed 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. Thank you for listening to Better Offline. The editor and composer of the Better Offline theme song is Mattasowski. You can check out more of his music and audio [e-mail] m a t t o s o w s k-I.com you can email me at ezetteroffline.com or visit betteroffline.com to find more podcast links and of course my newsletter. I also want really recommend you go to Chat wheresyoured app to visit the Discord and go to R betteroffline to check out our Reddit. Thank you so much for listening.

[Carl Brown]

Better Offline is a production of Cool Zone Media.

[Zone Media]

For more from Cool Zone Media, Visit our website coolzonemedia.com or check us out on the iHeartRadio app, Apple Podcasts or.

[Carl Brown]

Wherever you get your podcast.

[Ed Zitron]

Are you still quoting 30 year old movies? Have you said cool beans in the past 90 days? Do you think Discover isn't widely accepted? If this sounds like you, you're stuck in the past. Discover is accepted at 99% of places that take credit cards nationwide and every time you make a purchase with your card, you automatically earn cash back. Welcome to the now it pays to Discover. Learn [e-mail] credit card based on the February 2024 Nielsen report.

With a team.

[Carl Brown]

Ready to conquer the grandest stage immortality rate.

[Ed Zitron]

The stakes do not get any higher. The two very best in the NBA.

[Carl Brown]

An unforgettable journey is nearing its finale. The NBA finals. Presented by YouTube TV Pacers Thunder game one Thursday on ABC.

[Zone Media]

Does friendly have a taste? If it does, it's probably like hello's Peppermint flavored anti Plaque and Whitening toothpaste. Brush away plaque, show tartar who's boss and remove surface stains to naturally whiten. Hello's thoughtful and flavor forward products make brushing your teeth feel like a confetti filled bathroom dance party. So say hello to hello with the always cruelty free, never tested on animals toothpaste that's made to spread smiles. Visit helloproducts.com and let hello add some everyday yay into your life.

[Ed Zitron]

Here at the Almond Joy Factory, where.

[Carl Brown]

Tropical vibes abound, we use soft, fresh taste, the crunchiest almonds, and delicious chocolate candy. Ah, but do you know what our most important ingredient is? Sometimes you feel like a nut, sometimes you don't. Almond Joy's got nuts.

[Ed Zitron]

And something even way better than that.

[Carl Brown]

Yes, Almond Joy is made with almonds. And Jo.

[iHeart Podcast]

This is an I heart podcast.