TRASCRIZIONE 🔗
speaker-0: I went through this long interview process and I got feedback from them and they were like, you know, you know the why you're good with that, but we want somebody who's more focused on the how. That was when I realized that the how is an advantage to a person in the field. With the AI agents, I was able to say, you know, here is the user intent. And so that's why it kind of changed my mindset around it. That's why I like the whole concept of Centaur mode. That's how I'm sharing it with my teams and with others that I talk to now. The human and AI, when they put them together, they tend to do better together than alone. And that's the kind of visualization I'm bringing to the QA field. Mind mapping is still my answer for this. So many years later, it's still what I pull on because... you
speaker-1: Welcome to Browser Stack Talk, conversations that turn testing pain points into playbooks. I'm your host David, and today we're joined by someone whose path into tech is as inspiring as her current work in AI. Brittany Stewart has done amazing work. ⁓ But before I tell you all about it, let's ask Brittany to introduce herself.
speaker-0: Thanks David, thanks for having me today. I've really been looking forward to this one. So for those of you who don't know me, I'm Brittany Stewart. I am a senior QA specialist and engineer. I work with the Quality Works team currently and ⁓ I'm based in Kingston, Jamaica, which is a interesting fact, I think for a lot of people. But yeah, I've been in the field for over eight years. I'm very passionate about this QA field, but even more AI with QA. ⁓ And so I'm excited to share whatever is helpful to the audience today.
speaker-1: Awesome. ⁓ So Brittany, you didn't take a traditional path into computer science. ⁓ When I was doing my research, I noticed that you did a lot of graphic design and then kind of interior design. Did I see that correct? And then you've moved into software testing. ⁓ So the first thing that comes to mind is how does the design mindset, because you're clearly very good at it,
speaker-0: Yes, that's correct.
speaker-1: change the way you look at software products during testing?
speaker-0: Yeah, nice question. So I think it changes or impacts it in different ways, honestly. The first one that comes to mind is user personas. So in my graphics and interior design work, we focus heavily on who the end user is, who the user persona is, and we go in detail as much as like creating ⁓ a persona profile where you can visualize the person. I do the same thing in testing where I think about who the end users are. ⁓ I like to get in rooms where customers are and with other teammates who are actually using the tools hands on, day to day, because then I get a better understanding of how they're using the application, what frustrations they might have, their mindsets when they're actually doing the thing. And I just try to replicate that. ⁓ The other area is communication. So whether it's visual or
Load full transcript
⁓ I think ⁓ communication is very important. I mean, simple example is just last week, my team called me the Miro or Miroqueen, know, Miro the drawing tool. Yeah. Because I just... I like to visualize things. So we were talking about using AI and like we're trying to align on what AI looks like in our workflow. And I went ahead and created a AI touch points workflow diagram that everybody was amazed with. ⁓ and so, you know, I'm still using my design eye and design skills to communicate clearly to people on the team. The other thing is mind maps. So I talk about this a lot. might've seen my blogs out there on mind mapping. It's a very good visualization tool coming from design. fits right. I use it to help me with test planning and test coverage and communicating that to the clients as well. It's been a game changer for me in my career. So that's just another way that I integrate the design. And then the final thing coming from, you know, being in design is I'm used to working with clients and having this iterative mindset. where, you know, I give them a first draft, we get feedback, we refine, we repeat. It's the same approach that I take with testing. So I love doing the testing and I understand that, you know, this is just the first part. There might be things that are missed, it's version one and that's okay. We can keep working and iterating together. And so I think this is how that mindset from design translates into testing very well.
speaker-1: Yeah, that's awesome. So, ⁓ one of the things that you said there, it just reminded me of the conversation that I had when I did this podcast with Alan Page is that like, one of the key things that you are aiming for is making sure you're delivering, ⁓ feature, you're helping make sure that features work in the way people want it, right? You're delivering value rather than going, this PRD product requirement document is correct. right? Just like does my application actually work the way people are intending to do it? How do you like when you're doing that because it sounds like you do that like as a just matter of course what are the kind of steps that you do to go like from there to your mind mapping that you saying that like that's your productivity hack like Like I'm struggling to see, like I can see the individual parts, but like I'm struggling to see how you connect them because I think once I get that, I think there's something amazing there. So could you explain that a bit deeper?
speaker-0: I think so. So maybe I could talk about the mind mapping specifically, right?
speaker-1: Yeah.
speaker-0: Mind mapping is something that came naturally to me ⁓ because of design, yes. But honestly, I didn't know that it was something I could use in testing until I read Lisa and Janet's ⁓ Agile Testing book where they spoke about the actual application in testing. And so I just experimented with that, right? What I found is when I get on a project, there's a lot of information. You know, you have tons of
tabs, you have tons of features. ⁓ and this huge test plan usually that you have to review and try to understand and for me personally I shut down when I have a lot of reading to do and yeah I don't don't ⁓
speaker-1: Same, that's why I'm laughing.
speaker-0: There's lots of people who have that problem. so the mind map, and hopefully this brings the high level connection for you. The mind map is one of those things that allows me to like brain dump everything that's going on in my head and what I'm seeing. And then just visualize that there's science behind this tool, right? With mind mapping that when you see things, it helps you to make connections. And so I've just found a way to use the mind map to help me plan. Outline the test coverage, use colors to visualize what's missing, what's covered, and just make sense of all the chaos that's happening. That usually happens on very complex projects, I should say. ⁓ And then the upside is, I work with clients. I've been working with clients over the years and they find it valuable too, because for example, somebody new comes on and they don't understand the application. I've already done. ⁓ something high level that you can glance at and understand, know, not just read about. So hopefully that answers the question of the connection high level.
speaker-1: No, it definitely does. like, so the reason why I was asking that is that I could see like, I see the value in mind mapping is the way I got through university is that I kind of use them heavily. I know, Janet and Lisa have talked about it, but I've never tried to put it into practice. That was like the thing that was I never did. And that's why I was like, that sounds really cool. And I could kind of see it, but I was just the two points weren't linking up. And I knew that was a me problem. So I was trying to work out like how you do that. ⁓ And I think kind of the key thing here is that especially when you've got a lot of people and you're trying to disseminate knowledge down very quickly and allow people to review it, I can definitely see that being really good. And at the end of the day, I find mind maps really simple ⁓ and the simpler they are the easier that I can remember and go, ⁓ yeah, this makes sense. So thank you for that.
speaker-0: Yes, no problem. I'm glad that helped.
speaker-1: Do you have any other tricks that you've been trying to do? So you're the Myra Queen, ⁓ you do mind mapping. What are the other productivity hacks that you've been building on recently that you share out to people?
speaker-0: I really think those are the two main ones, just being able to visualize and communicate what it is I'm doing in testing.
speaker-1: Okay, cool. And I think, so the reason why I was asking that is that kind of one of the key things that I've noticed that you've been doing a lot of is you speak about the power of how in interviews and professional growth. Like, so like, can you explain that method, methodology ⁓ and why it matters and ⁓
how it influences quality engineering?
speaker-0: Yes. I love this one. This one is very personal to me, ⁓ because I created a sub stack newsletter called Hands On Wisdom, is HO, the acronym. And it actually came out of a job rejection that I experienced ⁓ last year. Yeah. Yeah. I was unemployed for a while and I went through this long interview process and I got feedback from them. And they were like, you know, you know, way you're good with that, but we want somebody who's more focused on the whole. And it's not that I didn't know the whole. So it's done when I got that feedback, right? ⁓ want to say no though, in retrospect, it was some of the best feedback I ever got because that was when I realized that the whole is an advantage to a person in the field. being able to explain the why is good, but being able to explain how things actually work in testing is a superpower. And so you'll that reflected on my blog and in LinkedIn where I am trying to communicate the how of things, just hands on wisdom, hands on day to day what's happening. Because you need to be able to explain how you find the bug in our everyday work. You also need to be able to. Explain how are you going to test that thing or test it at scale? How is AI going to integrate in the process? Like you have to get into the details. And so that rejection that I experienced, ⁓ and that feedback that I got about, you know, the how is kind of what has been pushing me all these years from just being a non-technical person, which is like on the design side to where I am now being more technical and really understanding. and learning more about how to do things in testing.
speaker-1: Yeah, and I think, and this is just my opinion, I think kind of the how is becoming increasingly more important, where before, like before kind of the AI age, I'll just call it that, is that like, there was an expectation that you kind of at least had a rough idea of how things worked. ⁓ in the age of AI, think it's become increasingly important because can you defend anything that AI is producing on your behalf? Right? So this could be a test case, this could be code, this could be a PRD, anything. And I think it's important that a lot of people focus in on the how moving forward because So I do a lot of open source work. And one of the key things that's happening in the open source space is that people aren't rejecting ⁓ pull requests or whatever because of AI usage. It's when they go, can you explain this bit of code? Because it looks interesting. I've never seen it. How would it work? And then they go, I don't know. And I think it's important that people still focus in on the how. ⁓ The code can still be messy. ⁓ Messy code existed before AI. I think a lot of people forget that. They just think it must be AI. It's like, AI trained on something. And it was that messy code we wrote before. ⁓ And so what are the steps that you kind of
speaker-0: through this.
speaker-1: help teams, customers, whoever you're working with to actually focus in on the how. Like what are the steps that you go like, go down this path and you'll start figuring out the how.
speaker-0: I mean, I think I can talk about that specifically our own or use of AI now. When I get on Teams, at least over the last year and a half, everybody wants to use AI as you say, and they're using it and we're generating all the code. ⁓ In terms of the how, I found that me as a professional,
speaker-1: When people are like, when you're working with customers, your teams, anyone that you interact with, how do you put them on the path to figuring out the how? Right? So because like everyone knows the why you do something, but how do you encourage juniors, even seniors when you're working with them to go and figure out how something works rather than just going, I'm doing this because that's my job. Right. they know the why but they don't understand the how.
speaker-0: Yeah, I think one of the main things that have to be a lead by example, I am one to show ⁓ if it's a junior in the situation. And I actually have that happening right now where I have to show my teammate, you know, this is how we communicate what it is we're doing clearly and still tying back to that point of visualization. I like to have those visuals on hand to show. ⁓ As I open up conversation with the team with these visuals so that we can have the conversations about these things and get clarity. ⁓ I'm also not afraid to ask the questions, right? So if something isn't clear for me, I ask the questions and I encourage people to do that. I do think leadership has a big part to play because you want to encourage the persons in the team to have like an open mindset and foster collaboration and feedback coming from team members. I always say, know, when somebody starts on a project for the first time and they're very excited and they come in with their feedback and, ⁓ know, this is, here's a suggestion to make this better. I think in those early moments on teams, when people don't, if you don't respond the right way, it sets a tone that might, you know. deter people from giving the feedback and I think it's important to set it right in the beginning. Yeah.
speaker-1: Yeah, I know that sounds awesome. And I think I think you're right. Like a team's culture can be set and it needs to be maintained. It's not just like you say it once and forget about it. It's something that you kind of iteratively ⁓ work through and support each other through it. ⁓ I've seen a lot of cases where it's like, ⁓ you're a junior, you'll figure it out and you're forgotten about. And that doesn't necessarily support them in their long-term career. But also, it seems like a short productivity gain for a senior, but actually long-term, causes more headaches. I don't know if you found that.
speaker-0: Yeah, it's better to rope them in and have them, you know, by your side from the early days. I don't leave my teammates and junior or senior, we collaborate. I
stress collaboration because I think that's very important. You have somebody with you guiding you along, always, not micromanaging, right? But just as a partner.
speaker-1: Yeah, definitely. Anyone who's worked with me will know very quickly I hate any form of micromanagement, either from me to them or vice versa. Because I can give you all this information, but every time I have to stop and give you that information, you're taking me out of flow, you're just causing more problems later. Can we just elaborate? And I love the way you phrased it there. I think that's awesome. Kind of the last part of this is that ⁓ how do you help teams foster a culture where ⁓ non-technical perspectives, so your design, your interior design, are giving us much weight as kind of the functional requirements that are needed in the application. So ⁓ these can be various things, but how do you foster that culture within the team?
speaker-0: I think the three things, there are three things that come to mind. And the first one I kind of touched on earlier, but it is the psychological safety. People need to feel safe in their space enough to say, yes, this feature works. But you know, when I click on it, it doesn't feel quite right. Can we talk about that? And that needs to be welcomed and not necessarily got shrugged off as an afterthought. That's just one area of psychological safety. I do think the other one is actually bringing in designers and QA early in the conversation around requirements. ⁓ And I've been seeing a lot of that. So I think the work that, you know, other pioneers in the industry have been doing is paying off because more teams that I see, this is what's happening. So for me, it all comes back down to user experience. think user experience is the whole point. As we were saying, bad user experience is a bad product. And that just can't work. So when you bring people like QA and designers in, we can ask the questions early. ⁓ And that will prevent issues from going out. You know, the whole mechanics around that where it's more expensive to fix when it's out there in production. If you get the questions asked earlier, it's better. So, um, leaders in the space in our organizations have to be the one to champion taking this kind of feedback from designers and QA and do it publicly. Um, like I said, you know, the new person coming in that first feedback sets the tone for a lot of people. And then that just sets the whole. culture. So definitely those three things are what I think are important for getting the non-technical perspectives in. yeah.
speaker-1: So kind of, think this is a really good point to segue slightly into some of your work around talking around AI and testing and things like that. So you're currently leading the charge on AI where you work. I'm sure you can agree there is a lot of hype in this space at the moment. But you've been focusing on more practical applications of this, ⁓ especially in the testing life cycle. ⁓ One thing that I kind of in doing my research that I saw you mention is that you said AI is a testing partner, not a replacement. ⁓ What is the biggest misconception teams have when they try automate with AI? Like, what is that for you?
speaker-0: For me, honestly, it's... They think AI will replace the entire QA team. It's not that simple. And you know, there are a lot of things to consider. There are different tech stacks. There are different maturity levels. There are different processes. There are different personalities on the teams. in my experience, like maybe for a simple website, simple website, yeah, you could use AI to replace a QA in that sense. But for the complex websites like in banking, that's not a smart move. And that's why I say it won't replace us. If you're in the right areas, it won't replace you. But yeah, I think the misconception is you're going to come in and make this big overhaul, but you have to start small ⁓ because AI will do things. The output we know is not something that we can gauge. And so that makes it hard for us to score or even understand. so, yeah, they need to, as a team, have to start small, ⁓ partner with AI first. And honestly, this is exactly what my browser stack ⁓ breakpoint talk is going to be about. It's something that I'm calling center mode because That's how I see AI actually working. And I want to kind of help to spread the word that, you know, it's not a big replacement. It's something that you work with side by side.
speaker-1: Yeah, I've been describing it as a tool to kind of help me be more productive. The phrase I've used is that AI ⁓ is a force multiplier. But if you don't have that underlying craft of what it's doing and understanding of the how that we were talking about earlier. you'll force multiplying zero and zero times anything is zero, right? Like it'll output something, but if you don't know what it's doing or how it's doing it, you're like, ⁓ In a previous episode, I don't know if you've seen it, the one with Marit, Marit describes AI and it's very similar to you is that she goes, AI allows me the ability to imagine better. ⁓
speaker-0: Yeah, love that.
speaker-1: Marit's so good with these phrases, like, and things like that. I wish I had the eloquence that she has when she comes out with these things.
speaker-0: I've learned a lot from her too, really good.
speaker-1: Yeah. And so kind of going back to your center and things like that, like you've experimented with ⁓ managed AI test squads. Could you explain what a test squad is before I ask my real question in that space? Like, what does it mean?
speaker-0: So a test squad is a set of AI agents that our QA uses to test an application.
speaker-1: Okay. And how does prompting in the space look different to kind of the traditional AI prompt and test automation, so that people can see the two side by side really?
speaker-0: Our automation traditionally is scripted and so it's very deterministic. We know that when we put this input in, we'll get
the same output and the responses are a clear pass or fail, right? AI, you give the same output three different times and you get three different paths depending on the context configurations that you have. the skills that you have set up. And ⁓ I did a podcast recently with Stacey Kirk, that's our CEO at Quality Works. And she said it the best way. So I'm going to quote her here where she said, the difference that's happening now is it's a scoring pattern that we need to use. It's not a pass or fail anymore. And I think that's a mindset shift that has to happen with QA ⁓ to not just be, you know, the red or green, pass or fail type of output. And in the early days, when I just started with a test squad, I thought that this was a weakness ⁓ with AI, but the more I've been using it, I see that it could be an asset depending on how you look at it, right? So I think the scripted tests will only find the bugs that we, like you told it to follow this path, it will follow that path and it will only find these bugs. I see the value in AI being non-deterministic in that it can also explore for us too. So one of the things, yeah, one of the things that I experimented with with the test squad was, you know, instead of the automated test being, you you, log in and let's say a login flow, you'd log in and you need to reset your password. You follow those detailed steps. With the AI agents, I was able to say, you know, here is the user intent. I, I like the word intent because you're thinking about the end user, right? Yeah. Yeah. So it's like, you forgot the password, but what happens? And the AI agents went off like a real user. Resetting, they tried different things like, you know, social logging, things that I probably wouldn't have thought of just off the bat. And even decided to leave, cancel the... and test that flow. And I was like, wow, this is really cool to see. And so that's why it kind of changed my mindset around it. It's not negative that is in the non-deterministic. I think we just have to figure out where to use it. And the human oversight becomes very important here. Because again, going back to what you said about the how, we at the end have to figure out, is this really doing what we want it to do? how we want it to do, is it working how we expected? And I think AI can actually shine when it comes on to helping us do the first pass of our like an exploratory testing type of ⁓ area. I think it's very powerful.
speaker-1: Yeah, no, I think it can be. ⁓ I think it suffers from the same limitations of in the past people were like, we're going to automate everything. You're like, no, you're not. So you can't AI everything. You can't automate everything. ⁓ And it comes back to that phrase around what Marit was saying, which is why I love it so much is that it extends our imagination. Because now we can, rather than doing kind of rote. basic things constantly. like, I don't have to do this. I can go focus on really hard problems. And for me, one
of the things that you described there with this password reset is that like it does all those things, but it doesn't tell you if the page is being slow, being kind of things are not rendered properly. You never see those. Like it can help with some of those, but that just kind of costs more AI tokens, takes longer, things like that. Right. Like you can, you can do it, but ⁓ there's a balance to be had, I think.
speaker-0: think so too. think even like to your example there, like a human has to be there to say, let's steer you in this direction. You're going the wrong way. And that's why I don't think it's something that will replace us.
speaker-1: Yeah. So that's to me, that's the human and the loop, which is the next thing I wanted to ask you about, because that's one of the key things that you've been talking about. Where exactly when you're doing those things, right? Because you're pioneering ⁓ AI and quality works. Like, how are you teaching people, showing people? ⁓ where the human in the loop needs to sit and validating everything versus just like, OK, I trust you. You can go off now, AI.
speaker-0: Yeah. ⁓ So what I'm doing with that is the human to me belongs alongside the AI, ⁓ whatever it is. I don't think it's like you belong before it or after it. I think it's side by side. And that's why I like the whole concept of Centaur mode. That's how I'm sharing it with my teams and with others that I talk to now because Centaur Mode actually comes from chess. Yeah. It's a chess term where the human and AI, when they put them together, they tend to do better together than alone. And that's the kind of visualization I'm bringing to the QA field. Because I think humans bring judgment, which AI doesn't have yet, even though it feels like it does when we talk to the, to the LLMs. We have to remember to have that human level judgment. so humans bring that we also bring the context that matters depending on the project that we're on. AI could have everything, but it might be too much. and so I think we bring that plus business understanding, understanding the end users, business stakeholders, what is, what are the goals that we're trying to achieve? Even if we give it to the AI, I as, as the human have to be the one to instruct it. that this is the path that we want to follow. And I think humans also bring empathy. AI tends to, it could go on, but at some point it takes a human's empath, sorry, at some point it takes a human to say, let's slow back and think about, you know, how this is actually, or affecting the end user. I go into it more in the talk and I'm trying to gauge what I- here versus what they're, it's okay. I think what I want to be clear about is humans stay in charge of judgment. AI brings a level of speed that we've never seen before, right? Because AI ⁓ can execute things like endlessly. It doesn't get tired like we do with our brains. sometimes I get frustrated. Honestly, I get frustrated with myself when I'm trying to do things and I'm like, I'm too tired. So it's not clicking, but the AI has the power to continue going, you know? ⁓ So I don't think humans set the direction. We are in charge of verifying the outputs and we should hold ourselves accountable to the outputs that it's given. And then we make sure that it has the right context to call on. ⁓ asking questions like, is this a bug in the application or is it actually intended behavior? Which I've seen a lot of that it might assume it's a bug, but it's real. It's supposed to be that way. And so if you're stepping into it, would say, you know, if you're stepping into it, like this AI is going to be the rubber stamp and it's the go-to and we can trust the end output. I think you're doing it wrong. think we would need to, it's a continuous loop. with human and AI alongside each other from the start to finish.
speaker-1: Yeah, yeah, definitely. I like that. That's awesome. You've also been doing kind of a bit of like community work and kind of explaining to people that the real experience in QA is important, right? Like, and valuable. And I think kind of what we've discussed so far has been really leading to that. ⁓ I've got a kind of hard question here for you. like, because I think like in the age of AI teams changing and kind of moving around as quickly as possible nowadays, like what's your secret weapon to finding a rhythm to kind of help onboard people in a new project help kind of care about like. their emotional safety that you were talking about earlier, like get them into like being the best human they can be at that moment that you need them.
speaker-0: specifically people coming on board maybe like a new person or just anybody in general.
speaker-1: Because I know you've done community advocacy, right? It's about any project where you do that, right? Because the things that I saw in my research was like, do a lot for a lot of people, right? So how do you kind of give them that, like, you've got a project, you're halfway through it, ⁓ everything is going horribly wrong, nightmares everywhere you look. How do you go, hey, we've got this. Let's get you into a rhythm ⁓ and go.
speaker-0: Yeah. Mind mapping is the, still my answer for this so many years later, it's still what I pull on because it's, it's, there is power in the lean test plan. ⁓ Having a light, like a lightweight way to visualize the scope and priorities and communicate the risk and how we're going to approach things rather than the formal 200, you know, page document. That's been my secret weapon. ⁓ I think most teams from what I see, they don't have this high level of view of documentation. And so it can be very hard for somebody coming on midstream. So my onboarding artifacts usually ⁓ start with this, the lean test plan. And then I do the product coverage outline to just overview what is this actually doing, which areas are covered. And then. I think it's important to know who to talk to. So in my mind maps, I do include people. So, you
know, if there's a problem, who do you talk to the product team? If you want to understand how you talk to the dev team, if there are any existing QA's, you lean on them to get an idea of where the flaky tests were or where the bugs tend to accumulate and which things have been priority. And this for me, it saves weeks. ⁓ for onboarding persons, ⁓ for myself getting in speed and well up to speed I should say. And so there that's my secret weapon, mind mapping. Visualizing, mind mapping but visualizing using a mind map.
speaker-1: Brittany, we've reached the point where I do a quick fire round. ⁓ The main reason for the quick fire round is, as you've probably noticed, I like to waffle. Where this is like my idea of getting succinct answers from people that are impactful answers. So where possible, I just need one sentence to answer this. Are you ready? Awesome.
speaker-0: Ready, let's go.
speaker-1: ⁓ What's your favorite testing tool that you've recently used?
speaker-0: Cursor AI with Claude inside. That's a daily one.
speaker-1: Okay, cool. A book every QA lead should be reading.
speaker-0: The Quality Coaches Handbook, I have it right here. That's by Anne Marie Marrett, ⁓ sorry, Sharad, Anne Marie Sharad. And I have to say Agile Testing book by Lisa Crispin and Janet Gregory.
speaker-1: Yeah, I think that Lisa and Janet's book has come up a few times. So if people aren't reading it, you probably should. ⁓ And hopefully I'll have them on the podcast soon. What is the most underrated skill for testers today?
speaker-0: Curiosity. I think you need to be curious and want to learn in order to stay on top of things in this day and age with so many things changing.
speaker-1: Yeah, definitely. ⁓ If you weren't in tech, what would your next dream job be?
speaker-0: Definitely interior design. like to have and create beautiful spaces, but also functional spaces.
speaker-1: awesome. In one sentence, why does the world still need human testers in the AI era?
speaker-0: because AI is missing context that only humans can add.
speaker-1: This has been incredibly insightful. ⁓ Thank you so much for joining me today, Brittany. I've learned a lot. Hopefully everyone else has learned a lot. Thank you for sharing your blend of creativity and kind of understanding cutting edge technology. ⁓ If people wanted to follow you or learn more about what you're doing, where can they find you?
speaker-0: Yes, thanks David. This was great too. If anybody wants to follow me, reach me on LinkedIn at my profile. ⁓ There's my blog as well where I share these things, brittanystorite.tech. And you can catch me at browser stocks breakpoint too because I'll be sharing more there.
speaker-1: amazing. And to everyone who's reached this point, please don't forget to hit subscribe or follow on whatever platform you're listening to or watching us on so you can be aware of future episodes. Hopefully we'll be getting more people like Brittany and others to join us soon. So thank you everyone.
speaker-0: Thank you. Bye.
speaker-1: you
speaker-0: you