328. Do We Still Need QA In Light Of AI

With AI writing so much code, do we even With AI writing so much code, do we even need a quality assurance department? If need a quality assurance department? If need a quality assurance department? If I can ask my AI to evaluate code, what's I can ask my AI to evaluate code, what's I can ask my AI to evaluate code, what's the purpose of having a QA person the purpose of having a QA person the purpose of having a QA person around? around? around? Now, right up front I'm going to tell Now, right up front I'm going to tell Now, right up front I'm going to tell you that yes, QA is absolutely valuable you that yes, QA is absolutely valuable you that yes, QA is absolutely valuable and not replaced by AI. and not replaced by AI. and not replaced by AI. And as an aspiring developer going into And as an aspiring developer going into And as an aspiring developer going into a QA role might be a good choice for a QA role might be a good choice for a QA role might be a good choice for you. But let's talk about why QA is you. But let's talk about why QA is you. But let's talk about why QA is valuable still and why AI can't just valuable still and why AI can't just valuable still and why AI can't just replace them in today's episode of Dev replace them in today's episode of Dev replace them in today's episode of Dev Questions. >> Software development is more than just >> Software development is more than just writing code. So, let's talk about the writing code. So, let's talk about the writing code. So, let's talk about the rest of it. Specifically, let's talk rest of it. Specifically, let's talk rest of it. Specifically, let's talk about quality assurance team members and about quality assurance team members and about quality assurance team members and why they are still valuable. why they are still valuable. why they are still valuable. And let me start off by saying that not And let me start off by saying that not And let me start off by saying that not every company can afford a dedicated QA every company can afford a dedicated QA every company can afford a dedicated QA person or team. I've been a number of person or team. I've been a number of person or team. I've been a number of those teams. But in that case, you those teams. But in that case, you those teams. But in that case, you absolutely need someone who can fill absolutely need someone who can fill absolutely need someone who can fill that role.

that role. that role. So, the question becomes what does a So, the question becomes what does a So, the question becomes what does a good QA person do? And I did say good, good QA person do? And I did say good, good QA person do? And I did say good, because not every person QA does a good because not every person QA does a good because not every person QA does a good job. Just like not every developer does job. Just like not every developer does job. Just like not every developer does a good job. But let's talk about what a a good job. But let's talk about what a a good job. But let's talk about what a good QA person does. I've put it into good QA person does. I've put it into good QA person does. I've put it into four categories. The first category is four categories. The first category is four categories. The first category is ensure software quality. ensure software quality. ensure software quality. Not necessarily make software quality. Not necessarily make software quality. Not necessarily make software quality. Again, QA people are not necessarily Again, QA people are not necessarily Again, QA people are not necessarily developers. developers. developers. They can be and I find it's often They can be and I find it's often They can be and I find it's often valuable if they have some development valuable if they have some development valuable if they have some development skills. But they're ensuring software skills. But they're ensuring software skills. But they're ensuring software quality by doing things like testing. quality by doing things like testing. quality by doing things like testing. They're looking at regression, making They're looking at regression, making They're looking at regression, making sure that they prevent regression in the sure that they prevent regression in the sure that they prevent regression in the code. By way, if you don't know what code. By way, if you don't know what code. By way, if you don't know what regression is, it means maybe you fixed regression is, it means maybe you fixed regression is, it means maybe you fixed one problem, but you solved or you you one problem, but you solved or you you one problem, but you solved or you you caused other problems while you do so. caused other problems while you do so. caused other problems while you do so. That's regression. That's regression. That's regression. Um something that was working isn't Um something that was working isn't Um something that was working isn't working anymore. So they they work on working anymore. So they they work on working anymore. So they they work on testing, they work on preventing testing, they work on preventing testing, they work on preventing regression, they work on identifying regression, they work on identifying regression, they work on identifying defects. They try and pick apart your defects. They try and pick apart your defects. They try and pick apart your code, how it works, and find all the code, how it works, and find all the code, how it works, and find all the issues. So they ensure software quality.

issues. So they ensure software quality. issues. So they ensure software quality. That's number one category. Number two That's number one category. Number two That's number one category. Number two is they understand the requirements. is they understand the requirements. is they understand the requirements. Which sounds weird, right? That's That's Which sounds weird, right? That's That's Which sounds weird, right? That's That's one of their jobs? Yes, absolutely. They one of their jobs? Yes, absolutely. They one of their jobs? Yes, absolutely. They need to be the ones that really need to be the ones that really need to be the ones that really understand the requirements. Now, understand the requirements. Now, understand the requirements. Now, developers, we should know the developers, we should know the developers, we should know the requirements backwards and forwards. requirements backwards and forwards. requirements backwards and forwards. But the QA person needs to know from a But the QA person needs to know from a But the QA person needs to know from a user perspective what the requirements user perspective what the requirements user perspective what the requirements are. And a lot of times the requirements are. And a lot of times the requirements are. And a lot of times the requirements don't get put into a document. And yes, don't get put into a document. And yes, don't get put into a document. And yes, I know some people love to have these I know some people love to have these I know some people love to have these huge long documents that explain huge long documents that explain huge long documents that explain everything about the the system. everything about the the system. everything about the the system. It's never enough. It's never enough, It's never enough. It's never enough, It's never enough. It's never enough, it's never right, uh it's never it's never right, uh it's never it's never right, uh it's never complete. complete. complete. Understanding the requirements from the Understanding the requirements from the Understanding the requirements from the user's perspective is really important user's perspective is really important user's perspective is really important for QA. Now, this may be where for QA. Now, this may be where for QA. Now, this may be where there's a a hybrid role with a business there's a a hybrid role with a business there's a a hybrid role with a business analyst. Business analysts and QA people analyst. Business analysts and QA people analyst. Business analysts and QA people are different sometimes and sometimes are different sometimes and sometimes are different sometimes and sometimes the same person. Um I've I've seen pros the same person. Um I've I've seen pros the same person. Um I've I've seen pros and cons for both. But if they're in a and cons for both. But if they're in a and cons for both. But if they're in a hybrid role, this is where they also hybrid role, this is where they also hybrid role, this is where they also have gathered the requirements in the have gathered the requirements in the have gathered the requirements in the first place. They're the person that first place. They're the person that first place. They're the person that sits between the the user and the sits between the the user and the sits between the the user and the developer, and they know the role really developer, and they know the role really developer, and they know the role really well.

well. well. So either way, they understand the So either way, they understand the So either way, they understand the requirements. This is really important requirements. This is really important requirements. This is really important because they're the ones that are going because they're the ones that are going because they're the ones that are going to test the requirements. They're the to test the requirements. They're the to test the requirements. They're the ones that are going to validate if the ones that are going to validate if the ones that are going to validate if the requirements are being met. They're a a requirements are being met. They're a a requirements are being met. They're a a person outside of the developer who person outside of the developer who person outside of the developer who knows what should happen and verifies it knows what should happen and verifies it knows what should happen and verifies it does happen. Cuz too often as developers does happen. Cuz too often as developers does happen. Cuz too often as developers we're really close to the issue. And you we're really close to the issue. And you we're really close to the issue. And you know, we've got our nose right next to know, we've got our nose right next to know, we've got our nose right next to the code, and we're we're working on the code, and we're we're working on the code, and we're we're working on making the code, we kind of lose track a making the code, we kind of lose track a making the code, we kind of lose track a bit of the overall goal sometimes. Or we bit of the overall goal sometimes. Or we bit of the overall goal sometimes. Or we get, you know, working on our feature get, you know, working on our feature get, you know, working on our feature and somebody else working on their and somebody else working on their and somebody else working on their feature and we kind of mash all together feature and we kind of mash all together feature and we kind of mash all together and say, "Hey, there you go." And and say, "Hey, there you go." And and say, "Hey, there you go." And there's no one looking at it saying, there's no one looking at it saying, there's no one looking at it saying, "Wait, wait, wait. Here's the overall "Wait, wait, wait. Here's the overall "Wait, wait, wait. Here's the overall requirements. We're missing some." Or requirements. We're missing some." Or requirements. We're missing some." Or these things work, but they don't work these things work, but they don't work these things work, but they don't work well together. Like, understanding the well together. Like, understanding the well together. Like, understanding the requirements is really important. And requirements is really important. And requirements is really important. And then understanding how to evaluate if then understanding how to evaluate if then understanding how to evaluate if you're meeting those requirements is you're meeting those requirements is you're meeting those requirements is really important. really important. really important. Number three kind of goes with number Number three kind of goes with number Number three kind of goes with number two, but number three category is they two, but number three category is they two, but number three category is they represent the user.

represent the user. represent the user. And that means they're looking for And that means they're looking for And that means they're looking for things like is the is the application things like is the is the application things like is the is the application intuitive? intuitive? intuitive? Your application can work. It can meet Your application can work. It can meet Your application can work. It can meet all the requirements all the requirements all the requirements and it might not be intuitive, which and it might not be intuitive, which and it might not be intuitive, which means it really should fail to QA. means it really should fail to QA. means it really should fail to QA. Because the user has to be able to use Because the user has to be able to use Because the user has to be able to use it. I was talking to a person on YouTube it. I was talking to a person on YouTube it. I was talking to a person on YouTube today about this, where they said, "Hey, today about this, where they said, "Hey, today about this, where they said, "Hey, I think I've built the the right user I think I've built the the right user I think I've built the the right user interface, but the user says they want interface, but the user says they want interface, but the user says they want something different. What do I do?" something different. What do I do?" something different. What do I do?" Well, at the end of the day, the user is Well, at the end of the day, the user is Well, at the end of the day, the user is the one using your application. the one using your application. the one using your application. I've built systems that that worked and I've built systems that that worked and I've built systems that that worked and that were logical and that had all the that were logical and that had all the that were logical and that had all the right pieces and they weren't intuitive right pieces and they weren't intuitive right pieces and they weren't intuitive or they didn't behave as expected. or they didn't behave as expected. or they didn't behave as expected. That's another part of this. Is it That's another part of this. Is it That's another part of this. Is it checked to make sure it behaves as checked to make sure it behaves as checked to make sure it behaves as expected? For example, expected? For example, expected? For example, tab order. This is one I used to get tab order. This is one I used to get tab order. This is one I used to get wrong every once in a while when I was a wrong every once in a while when I was a wrong every once in a while when I was a young developer. young developer. young developer. I was using I was using I was using VB6 when I was I was first building VB6 when I was I was first building VB6 when I was I was first building applications and you would drag things applications and you would drag things applications and you would drag things out of the form, but if you drag things out of the form, but if you drag things out of the form, but if you drag things on the form in the wrong order, well, it on the form in the wrong order, well, it on the form in the wrong order, well, it would assign tab order based upon what would assign tab order based upon what would assign tab order based upon what the last tab item was that was put in the last tab item was that was put in the last tab item was that was put in the form. So, I'd I'd put things in the the form. So, I'd I'd put things in the the form. So, I'd I'd put things in the form and then drag and rearrange them, form and then drag and rearrange them, form and then drag and rearrange them, but the tab order wouldn't rearrange but the tab order wouldn't rearrange but the tab order wouldn't rearrange with it.

with it. with it. So, maybe, you know, a simple example, So, maybe, you know, a simple example, So, maybe, you know, a simple example, you might be in a you might be in a you might be in a a field that asks you for your address. a field that asks you for your address. a field that asks you for your address. So, it's street address, city, state, So, it's street address, city, state, So, it's street address, city, state, zip. And you go from street address and zip. And you go from street address and zip. And you go from street address and you hit tab, it puts in the zip code you hit tab, it puts in the zip code you hit tab, it puts in the zip code field. Then you hit tab, it goes back to field. Then you hit tab, it goes back to field. Then you hit tab, it goes back to to state. Then you hit tab, it goes to to state. Then you hit tab, it goes to to state. Then you hit tab, it goes to street address, too. Or like it's all street address, too. Or like it's all street address, too. Or like it's all over the place. You're like, "What's over the place. You're like, "What's over the place. You're like, "What's going on here?" That's not behaving as going on here?" That's not behaving as going on here?" That's not behaving as expected. Checking tab order is not expected. Checking tab order is not expected. Checking tab order is not necessarily something that developers necessarily something that developers necessarily something that developers often do. We say, "Yeah, they're all often do. We say, "Yeah, they're all often do. We say, "Yeah, they're all there." there." there." But But But the QA person goes, "Yes, but it's not the QA person goes, "Yes, but it's not the QA person goes, "Yes, but it's not behaving as expected." behaving as expected." behaving as expected." And then with this, they represent the And then with this, they represent the And then with this, they represent the user when it comes to performance, where user when it comes to performance, where user when it comes to performance, where they go, "Yeah, it all works, but it they go, "Yeah, it all works, but it they go, "Yeah, it all works, but it takes 5 seconds to load a new page and takes 5 seconds to load a new page and takes 5 seconds to load a new page and they need to move." they need to move." they need to move." I've worked with with people who have I've worked with with people who have I've worked with with people who have worked on heads-down program, I call worked on heads-down program, I call worked on heads-down program, I call them, where they're not using their them, where they're not using their them, where they're not using their mouse. They're just mouse. They're just mouse. They're just putting as much information in as putting as much information in as putting as much information in as possible. They're just taking the data possible. They're just taking the data possible. They're just taking the data from paper and putting it in the from paper and putting it in the from paper and putting it in the computer, or computer, or computer, or they're filling out information as fast they're filling out information as fast they're filling out information as fast as possible, and they want to make sure as possible, and they want to make sure as possible, and they want to make sure their system doesn't hold them back.

their system doesn't hold them back. their system doesn't hold them back. And I built systems where they held them And I built systems where they held them And I built systems where they held them back, and they're like, "You're killing back, and they're like, "You're killing back, and they're like, "You're killing me because my job is dependent on how me because my job is dependent on how me because my job is dependent on how fast I do things, and your software is fast I do things, and your software is fast I do things, and your software is making me go slower." making me go slower." making me go slower." That's a problem. QAs have to step in That's a problem. QAs have to step in That's a problem. QAs have to step in and say, "Hey, you know what? No. This and say, "Hey, you know what? No. This and say, "Hey, you know what? No. This is not performing. This is not is not performing. This is not is not performing. This is not doing the right thing for the user. This doing the right thing for the user. This doing the right thing for the user. This is not to represent the user and saying, is not to represent the user and saying, is not to represent the user and saying, 'Hey, they need better.'" 'Hey, they need better.'" 'Hey, they need better.'" So, that's category number three. So, that's category number three. So, that's category number three. Category number four is they improve the Category number four is they improve the Category number four is they improve the process. process. process. So, the process of getting the So, the process of getting the So, the process of getting the requirements to the developers, getting requirements to the developers, getting requirements to the developers, getting the requirements turned into code, the requirements turned into code, the requirements turned into code, getting the code tested, and getting the getting the code tested, and getting the getting the code tested, and getting the code back out to the user, that whole code back out to the user, that whole code back out to the user, that whole process can be improved by QA. That process can be improved by QA. That process can be improved by QA. That means they might create automated tests. means they might create automated tests. means they might create automated tests. It might mean they improve procedures in It might mean they improve procedures in It might mean they improve procedures in how they do things. That might mean they how they do things. That might mean they how they do things. That might mean they train the developers on where the bugs train the developers on where the bugs train the developers on where the bugs live or what the users actually want live or what the users actually want live or what the users actually want from their application so they can just from their application so they can just from their application so they can just do it the next time instead of having to do it the next time instead of having to do it the next time instead of having to have it come back from QA as a fail. And have it come back from QA as a fail. And have it come back from QA as a fail. And they build better test cases where they they build better test cases where they they build better test cases where they say, "Hey, you know what? There's some say, "Hey, you know what? There's some say, "Hey, you know what? There's some things that I've seen in when the users things that I've seen in when the users things that I've seen in when the users are using these things that we hadn't are using these things that we hadn't are using these things that we hadn't accounted for and let's let's account accounted for and let's let's account accounted for and let's let's account for those things." So, QA does a lot of for those things." So, QA does a lot of for those things." So, QA does a lot of great work.

great work. great work. And And And there's a there's a difference between there's a there's a difference between there's a there's a difference between working working working on software and working on good on software and working on good on software and working on good software, right? There's a difference software, right? There's a difference software, right? There's a difference between saying, "Hey, it works." and it between saying, "Hey, it works." and it between saying, "Hey, it works." and it works well. works well. works well. And QA is often the group that brings And QA is often the group that brings And QA is often the group that brings out that difference. out that difference. out that difference. So, let's ask a question here. Why can't So, let's ask a question here. Why can't So, let's ask a question here. Why can't AI do this? Because it seems like that's AI do this? Because it seems like that's AI do this? Because it seems like that's a role for AI, right? No, because AI a role for AI, right? No, because AI a role for AI, right? No, because AI doesn't actually fully test its own doesn't actually fully test its own doesn't actually fully test its own code. You might see, you know, AI writes code. You might see, you know, AI writes code. You might see, you know, AI writes code and goes, "Oh, I've also written code and goes, "Oh, I've also written code and goes, "Oh, I've also written 150 tests." 150 tests." 150 tests." Yeah, but those tests are written by the Yeah, but those tests are written by the Yeah, but those tests are written by the same person who created the the code in same person who created the the code in same person who created the the code in the first place. They I'll often find the first place. They I'll often find the first place. They I'll often find the tests are really bad because they the tests are really bad because they the tests are really bad because they have the same assumptions as the code have the same assumptions as the code have the same assumptions as the code does. does. does. And so, they're not actually testing And so, they're not actually testing And so, they're not actually testing that the functionality works the way it that the functionality works the way it that the functionality works the way it should, they're testing the same should, they're testing the same should, they're testing the same assumptions they had that were assumptions they had that were assumptions they had that were incorrect. So, that's a problem, but it incorrect. So, that's a problem, but it incorrect. So, that's a problem, but it doesn't even understand all the code.

doesn't even understand all the code. doesn't even understand all the code. And so, it doesn't understand the And so, it doesn't understand the And so, it doesn't understand the greater context because it doesn't even greater context because it doesn't even greater context because it doesn't even have enough have enough have enough context window to put the entire code context window to put the entire code context window to put the entire code base in. And so, what it does instead is base in. And so, what it does instead is base in. And so, what it does instead is it makes assumptions. it makes assumptions. it makes assumptions. And we all know that assumptions aren't And we all know that assumptions aren't And we all know that assumptions aren't good when it comes to code. good when it comes to code. good when it comes to code. Uh number two, AI only understands what Uh number two, AI only understands what Uh number two, AI only understands what you tell it. you tell it. you tell it. And even then, And even then, And even then, not actually all what you tell it. So, not actually all what you tell it. So, not actually all what you tell it. So, when it comes to requirements, when it comes to requirements, when it comes to requirements, somebody has to gather those. And the somebody has to gather those. And the somebody has to gather those. And the user saying, "Here's my requirements." user saying, "Here's my requirements." user saying, "Here's my requirements." isn't going to be good enough. And the isn't going to be good enough. And the isn't going to be good enough. And the developer saying, well, I'm going to developer saying, well, I'm going to developer saying, well, I'm going to give it better requirements give it better requirements give it better requirements unless you're good at QA, unless you're good at QA, unless you're good at QA, you're probably going to give it great you're probably going to give it great you're probably going to give it great instructions, either. You'll get better instructions, either. You'll get better instructions, either. You'll get better instructions, much better instructions, instructions, much better instructions, instructions, much better instructions, but there is something to understanding but there is something to understanding but there is something to understanding fully what the user actually wants, fully what the user actually wants, fully what the user actually wants, how it actually needs to work, not just how it actually needs to work, not just how it actually needs to work, not just what they say, what they say, what they say, and then translating that into something and then translating that into something and then translating that into something that can be easier to understand as a that can be easier to understand as a that can be easier to understand as a developer. developer. developer. That's just something that AI can't do. That's just something that AI can't do. That's just something that AI can't do. Also, AI does not represent the user.

Also, AI does not represent the user. Also, AI does not represent the user. It It It it doesn't understand the user. It it doesn't understand the user. It it doesn't understand the user. It doesn't understand where they're coming doesn't understand where they're coming doesn't understand where they're coming from. It doesn't empathize with how from. It doesn't empathize with how from. It doesn't empathize with how they've done the work. It hasn't they've done the work. It hasn't they've done the work. It hasn't actually done the job. It hasn't learned actually done the job. It hasn't learned actually done the job. It hasn't learned because AIs don't learn. because AIs don't learn. because AIs don't learn. And so, yeah, even the memory files, not And so, yeah, even the memory files, not And so, yeah, even the memory files, not good enough. So, good enough. So, good enough. So, it doesn't represent the user to go, it doesn't represent the user to go, it doesn't represent the user to go, "Hey, this needs to be more performant "Hey, this needs to be more performant "Hey, this needs to be more performant because this user does it things this because this user does it things this because this user does it things this way." It doesn't know about that unless way." It doesn't know about that unless way." It doesn't know about that unless you told it, which again comes back to you told it, which again comes back to you told it, which again comes back to it doesn't understand anything you don't it doesn't understand anything you don't it doesn't understand anything you don't tell it. tell it. tell it. And number four, AI isn't good And number four, AI isn't good And number four, AI isn't good performing or improving procedures. Yes, performing or improving procedures. Yes, performing or improving procedures. Yes, if you push and ask it and and work with if you push and ask it and and work with if you push and ask it and and work with it, it can give you better procedures it, it can give you better procedures it, it can give you better procedures sometimes if it actually understands the sometimes if it actually understands the sometimes if it actually understands the problem, but more often than not, it's problem, but more often than not, it's problem, but more often than not, it's basically you basically you basically you like frog marching it until it gets to like frog marching it until it gets to like frog marching it until it gets to the point where it's the point where it's the point where it's like gives you back what you were asking like gives you back what you were asking like gives you back what you were asking for in the first place, right? So, for in the first place, right? So, for in the first place, right? So, it's not good at improving procedures. it's not good at improving procedures. it's not good at improving procedures. So, you need QA. So, you need QA. So, you need QA. As a developer, if you haven't worked As a developer, if you haven't worked As a developer, if you haven't worked with a good QA department or you you with a good QA department or you you with a good QA department or you you don't have access to one, don't have access to one, don't have access to one, I would encourage you to work on I would encourage you to work on I would encourage you to work on building up your own skills in this area building up your own skills in this area building up your own skills in this area because this is going to make you a because this is going to make you a because this is going to make you a better developer. The more you better developer. The more you better developer. The more you understand the QA role, the better you understand the QA role, the better you understand the QA role, the better you guys, the better you will be as a guys, the better you will be as a guys, the better you will be as a developer. And which is also why I developer. And which is also why I developer. And which is also why I encourage new developers who are encourage new developers who are encourage new developers who are struggling to find development roles to struggling to find development roles to struggling to find development roles to look into at the roles. They aren't the look into at the roles. They aren't the look into at the roles. They aren't the same same same and they often don't include and they often don't include and they often don't include development. So, it's not like you're development. So, it's not like you're development. So, it's not like you're just you know, developer in waiting just you know, developer in waiting just you know, developer in waiting necessarily. They can be. But, what it

necessarily. They can be. But, what it necessarily. They can be. But, what it does do is it gives you the skills and does do is it gives you the skills and does do is it gives you the skills and experience you're going to need to be a experience you're going to need to be a experience you're going to need to be a better developer when your time comes. better developer when your time comes. better developer when your time comes. The The role of a QA developer is The The role of a QA developer is The The role of a QA developer is something that is badly needed in a lot something that is badly needed in a lot something that is badly needed in a lot of organizations. I see a lot of of organizations. I see a lot of of organizations. I see a lot of companies that are kind of skipping that companies that are kind of skipping that companies that are kind of skipping that because it Who needs quality anymore, because it Who needs quality anymore, because it Who needs quality anymore, right? We can We have quantity. Quantity right? We can We have quantity. Quantity right? We can We have quantity. Quantity is not the solution. Quality is the is not the solution. Quality is the is not the solution. Quality is the solution. That's where you get the solution. That's where you get the solution. That's where you get the sticking power in application. That's sticking power in application. That's sticking power in application. That's where things go from they work to they where things go from they work to they where things go from they work to they work well. So, work well. So, work well. So, if you have your QA people on your team, if you have your QA people on your team, if you have your QA people on your team, give them a hug. They're awesome. Um give them a hug. They're awesome. Um give them a hug. They're awesome. Um learn from them. And if you don't, learn learn from them. And if you don't, learn learn from them. And if you don't, learn how to be them. And even if you do, how to be them. And even if you do, how to be them. And even if you do, learn from them. Learn how to be a learn from them. Learn how to be a learn from them. Learn how to be a better developer because you learn from better developer because you learn from better developer because you learn from your QA people and get better at your QA people and get better at your QA people and get better at understanding what they do, why they do understanding what they do, why they do understanding what they do, why they do it, and how you can incorporate some of it, and how you can incorporate some of it, and how you can incorporate some of those same techniques into your those same techniques into your those same techniques into your development experience, okay? development experience, okay? development experience, okay? QA is important. AI can't replace it. It QA is important. AI can't replace it. It QA is important. AI can't replace it. It is a necessary role to put out good is a necessary role to put out good is a necessary role to put out good software, not just working software. All software, not just working software. All software, not just working software. All right? Thanks for listening. As always, right? Thanks for listening. As always, right? Thanks for listening. As always, I am Tim Corey.