That Time I Brought Down The Company
Chris and Mike share stories of their worst days at work and the lessons they learned from their mistakes. Both stories highlight the importance of slowing down and showing empathy towards others when they make mistakes.
Leave us a voicemail online and send us your experience or thoughts to info@notquitethereshow.com
Visit nqtshow.com and visit here to see all available platforms this podcast is now available on!
What do you do with your worst day at work? Mike Mobley and Chris Howard trade their best worst stories and land here: slow down, lean on the people God puts around you, and show others the same grace you needed. Chris tells how, early in his programming career, one distracted delete in the wrong environment wiped every loan from a mortgage company’s system. Mike tells about his second (and last) night stocking shelves at a grocery store, when a bag of raw meat from the butcher department split open and poured down his shirt. Along the way: Proverbs 18 on slowing down, why real life has no test environment, the gift of people who jump in to help, and why empathy for other people’s mistakes points back to Jesus. Below: the key takeaways, the Scripture discussed, and the full episode transcript.
The Day Chris Brought Down the Company
Fresh out of college, Chris was a programmer at a mortgage servicing company, experimenting with Java to make a clunky system easier to use. He pulled real data from production into a test environment, and he was in the habit of clearing out his test database between runs. One day he got distracted and ran the delete on production. Every loan in the system, gone. When people started asking where the loans went, he raised his hand. Thankfully, there were backups from about an hour earlier, and the company added safeguards between test and production. He kept his job. Looking back, he couldn’t have asked for a better reaction.
Raw Meat and a Moment of Clarity
Around 19 or 20 and between jobs, Mike took a night shift stocking a grocery store. On night two, he watched the crew, boss included, eat the inventory and hurl cake icing tubs at the wall. Then, taking out the trash, a paper-thin bag split over his head and raw meat from the butcher department slid down his neck. Before it hit the ground, he knew he was done. He wasn’t following Jesus yet, but he gives God the credit for the clarity: if he stayed in that environment, he’d become like them. “You need to be walking with wise people.”
Slow Down: Proverbs 18
Chris’s first lesson is simple: slow down. Think about what you’re doing, and choose quality over quantity. Mike connects it to Proverbs 18, which his group just studied. It contrasts wisdom with the folly of running our mouths: “A fool’s lips walk into a fight.” Scripture shows a Lord who is slow and patient, who even speaks in a whisper. If we don’t slow down, we can’t hear him. Yet by default we race, talk, yell and rush to get the quick comment in.
There’s No Test Environment in Real Life
Chris’s big takeaway: in life there’s no test environment. We get one shot, so we need to be considerate and deliberate about what we do, how we spend our time and who we spend it with. It’s for keeps. Mike adds the flip side: we may always be one keystroke away from a big mistake, but also one keystroke away from doing a really awesome, godly thing God is calling us to do.
Backups, Restoration and People Who Jump In
Lesson two: have backups. Lesson three: restoration. The data came back, and God restores and redeems our mistakes too. Chris remembers the senior programmers who didn’t blame him or demand he fix it. They just said, “Let’s get a plan,” and walked toward the conference room like the Earp brothers heading to the OK Corral. Mike notes how easily we beat ourselves up for a season (or two) after a mistake, and how much we need each other to talk about it.
Empathy for Other People’s Mistakes
The lesson Chris believes God most wanted him to learn: empathy. When people make a mistake they didn’t mean to make, he can relate, and he has more patience for it. Mike calls it a good word to end on. We get aggravated so fast, even at a customer service worker who’s just trying to get by. We’re not perfect, and Jesus is perfect on our behalf, so we can extend grace. Be the person who steps in without asking questions and helps. After all, think of the mistakes Jesus’ closest followers made, and how patient he was with them.
Scriptures From This Episode
Proverbs 18:6–8 (a fool’s lips walk into a fight; the words of a whisperer)
Go deeper: 3 Reasons Why Your Job Matters · Scripture on Work · Scripture on Wisdom · Fruit of the Spirit: Patience · Grace And Consequences Are Both Acts Of Love · Scripture on Grace
Full Transcript, Not Quite There, Episode 11: That Time I Brought Down The Company
Voicemail: Hey Mike, it’s me, Mark. How’s that one championship banner hanging? You know what? We got 18. Yeah, Celtics, baby. Tatum. Brown. Jrue. Even Porzingis. Your liability’s become our asset. Yeah, that’s right. Hitting threes with the bad knees. I’m going to name a Wahlburger after him. It’s going to be called the Porzingis Porker. Guess what it’s going to have on it? Three layers of beef. Three different types of cheeses: Havarti, Muenster, cheddar. And guess what? It’s going to have three different layers of ham: prosciutto, pancetta, capicola. That’s right, baby. Say hi to Luka for me. Maybe next year.
Mike: Whoa. Marky Mark with the hot takes versus the Mavs.
Chris: With the hot temper. I always feel like he’s just coming in a little bit irate.
Mike: I think everyone from Boston’s that way.
Chris: You know what? I’m starting to believe it. Wicked mad.
Mike: Well, thank you. Thanks, Wahlberg, for calling in again after your 3:30 a.m. workout. But we have to take our licks. We did lose. Even though you’re a Colorado fan, I’m saying “we” and bringing us both into this.
Chris: I still want to see the Mavericks do well.
Mike: Yeah, because who doesn’t love the Mavs?
Chris: I mean, Luka and Kyrie. I thought we had something.
Mike: Congratulations, Boston. Have fun hanging your 18th banner.
Chris: We’re so excited for you.
Mike: You know what I’m feeling great about? The latest update on your kidney stone. Can you give us a quick status report?
Chris: I believe we are all past.
Mike: Oh, for real? It’s done?
Chris: Yeah. I want to believe.
Mike: I want to believe. Okay. Are we saying it’s done?
Chris: Yes. Until further notice.
Mike: All right. Congratulations. That’s a big week for you.
Chris: It is. I’m glad to be on the other side.
Mike: What else has been going on for you this week?
Chris: Oh, let’s see. This week I’ve got some new leisure shorts.
Mike: Oh, yes. Are you wearing those right now? For the listener, they are very blue and very leisurely slash swimwear shorts.
Chris: I would say you can go from pool to podcast.
Mike: Chris is wearing the shorts with a black polo. So he is Zoom business up top…
Chris: Very much.
Mike: …and pool party down below.
Chris: But these are the greatest shorts ever. You don’t understand. They are super comfortable.
Mike: They look comfortable. I want to keep looking at your shorts.
Chris: Please do not envy my shorts.
Mike: Well, you did not make a mistake with your shorts. Congratulations. Father’s Day gift?
Chris: Shout out to the family. Three pairs of new leisure shorts.
Mike: Okay. Humble brag on the three.
Chris: I can’t be happier.
Mike: Well, I can be unhappy for both of us, because I have multiple mistakes to confess over the last week. Let’s get into them. From last episode, if you remember, I may have rudely shouted out Walmart for bad customer service. Well, Walmart, we listened to you, and I meant Academy. It was Academy Sports that gave Joelle some terrible customer service, not Walmart. So, Walmart, we apologize.
Chris: Okay, well, so the possible Walmart sponsorship is back on the table.
Mike: Yes, you’re still considering. Please consider. Academy’s out the door now, because we destroyed them. And then when I posted our episode, those of you with a keen eye would notice it wasn’t Chris Howard who was hosting last week’s episode.
Chris: Who was it, Mike?
Mike: It was Christ Howard.
Chris: Do you realize how much pressure that puts on me? Do you realize the level of that?
Mike: I guess I had Christ on the mind. Not a terrible thing while you’re making branding and graphics. But yeah, the pressure’s on you. So now you have the follow-up episode. Good luck to you.
Chris: I’m glad that you were thinking of Christ.
Mike: Has anyone ever called you Christ Howard by mistake?
Chris: No, that hasn’t happened before. Maybe that will happen more now.
Mike: And you know what? We’re going to leave it out there on social media. A little thing called authorship integrity.
Chris: We’re going to let the mistakes stay out there. And you know what? It’s my kind of mistake.
Mike: If you’re going to make a mistake, why not? There are worse mistakes than being Christ Howard. What are we talking about today?
Chris: Today? Mistakes. We can do that a little bit. I don’t want you to feel lonely out there. I know you’ve been taking some heat. I want to make sure you know I’ve had to learn some lessons too. We’re going to take a little bit of a story time here.
Mike: You’re going to minister to me through this storytelling, is what you’re saying. This is like counseling for me. All right, let’s do it. Story time, everyone. Story time with co-host Chris.
Chris: Before podcasting, and before digital marketing and other things that I’ve explored, I started out my career as a programmer: systems engineer, programmer analyst, all sorts of fun titles that went with these types of jobs, where basically you sat in front of a computer and you programmed.
Mike: Like you’re writing code.
Chris: So I started off writing in a language called RPG, which sounds a lot like…
Mike: Role-playing games.
Chris: Nothing like it. But it was on a platform built by IBM called an AS/400, and they tried to rebrand it to the iSeries to sound a little bit more hip. Sounds really cool, but this thing was ugly to look at. Think a terminal: a black screen, green code.
Mike: The blinking cursor all the time. Almost like The Matrix a little bit.
Chris: Very Matrix. But that’s what I was working on out of college.
Mike: So you were Neo in college.
Chris: Yeah, we’ll say that. But that’s what I was looking at each day, and I wanted to play around with some new technology. I had some friends who were off in the Windows world doing some fun things, and I was like, how can we make this a little more user-friendly, a little nicer to look at for our client, which was an internal client? So I started playing around with Java.
Mike: Was that a new thing at the time?
Chris: It was newer.
Mike: This was about 50 years ago, if I’m getting the timeline more or less correct.
Chris: I was zero years old and I was coding. It was a prodigy thing. Like Doogie Howser without the medical stuff. Just insert programming.
Mike: So you start experimenting with Java.
Chris: Java. Yes. And if I haven’t bored you to tears yet, Java was something you could basically hook up to this ugly-looking program and its database.
Mike: I’m listening. Was this part of your job, or was this on the side? You were just trying to make it better.
Chris: This was part of my job, and it was something I was interested in, so they gave me some rope to go ahead and explore it. The whole idea was that this was going to be something good. Well, long story short, I decide I’m going to use some test data, and I’m going to pull that test data from our production environment, because that’s the best data. It’s the real data. Then I’m going to put it in a test environment, run some queries over it and make sure this thing’s working and everything’s going fine. Until that one day. I was used to deleting information out of my test database so I could run it again and check the results again…
Mike: Out of the test environment.
Chris: But guess what? I get distracted, and I run the query over the production environment, and it brings the whole house down.
Mike: Okay, hold on. Let me recap this to see if I understand the technical jargon. This isn’t like you deleted something that goes into a bin that you delete again later. This is from the terminal. If you delete this, am I understanding? It’s gone.
Chris: It’s gone.
Mike: There’s no double delete. There’s no safeguards. This is, again, when bread was a nickel 50 years ago. So you run this script, it’s over.
Chris: Yeah, I run this. It deletes all the loans in the system, because this is a mortgage servicing company. All the loans.
Mike: So, financial information. Are you going to get in trouble for saying this? None of this is financial advice. When people say that on podcasts, no matter what they’re talking about: none of this is legal or financial advice. What in the world happened?
Chris: Well, people start questioning some things. They start asking, “Hey, what happened to the loans?” And people are looking around, and finally, I think I know what happened. So I raised my hand. Managers come over, and we take a look at what just happened. Pretty soon a plan is put in place. We have our best programmers on it, our most seasoned programmers, and they’re putting together a restoration plan.
Mike: And you’re over in the corner, holding your legs, rocking. Make it stop. Restoration plan. Can they restore?
Chris: They could. They took backups.
Mike: Oh, they did take backups.
Chris: They did take backups. But what we found out from this is that we needed a little more of a safeguard, a partition between our test environment and our production environment. So in a way, I was kind of a pioneer. I didn’t discover Florida or anything. But this caused us to put in some safeguards, some policies. And I didn’t really hear anything too much about it, at least to my face.
Mike: I’m sure there were some things behind your back. How frequent were the backups?
Chris: They were frequent enough to get us within about an hour of what happened.
Mike: Oh, man. What if the backups weren’t there?
Chris: It would have been really bad. It would have been really bad, Mike.
Mike: But what I really hear you saying is you pioneered the future of safety for that company. You took the hit for the company.
Chris: I did.
Mike: We thank you.
Chris: They didn’t thank me, and there was no bonus for it.
Mike: Did you keep your job after that?
Chris: I did keep my job, thankfully. I couldn’t have asked for a better reaction for almost taking down the entire company. Or at least taking it down for a while.
Mike: I feel like you took it down, actually. And it was restored back to life.
Chris: Exactly. After I killed it. There was a commercial going around a while back about the pink slip virus. Somebody clicks on a “Wanna get away?” kind of email, and all of a sudden every computer in the office starts lighting up.
Mike: Is there a part of you that hates that for malware and virus purposes, but another side of you that’s like, well, that’s a little clever? I kind of want to see an office go through that.
Chris: What I know now is that whenever you see two-factor authentication, or anything that says, “Hey, do you really want to delete this?”, I think that would have been great to have back then.
Mike: That’s your reminder every time. Okay, I’ve never heard this story. Do you remember what distracted you? Were you playing Tetris on the side?
Chris: No, I was working very hard during that time, and I was working long hours.
Mike: So you were tired? A little sleepy?
Chris: Maybe tired. Maybe somebody had asked me a question or stopped by my desk, back in the day when people would come up to your cubicle and just talk you up. I have no idea. I can’t remember what distracted me. All I remember is that I pressed the button to clear out the data.
Mike: And then you heard that space in your mind go, “Oh no.” How would you encourage coders from here? In code speak, nerd speak, tech speak?
Chris: Go from development to integration to production. Don’t walk around production too often. And make sure the data you’re pulling is from testing.
Mike: What are those fancy words people say? “Make sure the synergistic energy of the integration is optimized for full efficiency factors.”
Chris: I would say yes.
Mike: In any boardroom, you’re like, yes. That’s excellent.
Chris: Let’s do that. Synergy.
Mike: Wow. So do you think that’s one of your worst day at work stories?
Chris: I would say so. That one had me feeling pretty vulnerable, and I really felt like I was going to be asked not to come back. Like, if you’re going to do that to our company, then we’re not going to want you here.
Mike: So have you taken down any other companies, like in your spare time?
Chris: I have not. The lessons I learned from there were: be a little more careful. Concentrate.
Mike: You’re making me think of one of my worst days at work. And I’m also realizing, right before I tell you this story, that you’re just a much more mature and adult man than me, because here you are coding…
Chris: With great leisure shorts.
Mike: With your swimming trunks on. And my story is a job that may not be as important as yours, but I feel like there were some life lessons learned. So in my young twenties, maybe 20, maybe I was 19, I don’t know, at some point I was between jobs and I just needed some cash. I wasn’t necessarily looking for a career move. So I went to a grocery store to be a stalker.
Chris: Not a stalker.
Mike: Not a stalker. A stocker. Meaning that, as most of you probably know, in the middle of the night all the grocery stores are restocked.
Chris: They don’t stock themselves.
Mike: There’s a stocking crew that comes in the middle of the night and stocks shelves, takes inventory, all that good stuff. This was at a grocery store called Winn-Dixie, back in the day. I don’t think they exist anymore.
Chris: There’s got to be a Winn-Dixie out there.
Mike: There’s probably one out there. So I think it was my second night on the job. I kind of didn’t really care about the job. To be honest, I didn’t have a future in stocking, if that makes sense. And I realized the stocking crew and the manager were in the back, opening up the pallets of food, and there was a mixture of the team eating the supply, and taking these cake icing tubs and throwing them against the wall as hard as they could to see who got the biggest splatter. Biggest splatter wins.
Chris: I had no idea this goes on after dark.
Mike: These are after-dark activities. I was very surprised. Not only to see the team doing it, I mean everyone was doing it, but to see the boss doing it with them. It was day two. I was like, well, I’m probably going to be here for about a week. I’m probably going to be looking for another job really quick. But on that same night, and this is the shortest job I ever had, we also had to take out the trash. So I was taking out the trash. They had these trash bags that were paper thin, the plastic, you know what I mean? And as I’m getting the bag up over my head to throw it into the dumpster, the plastic opens up. And it’s not just trash that falls on me. It’s raw meat from the butcher department. And it goes into my neck and slides down my shirt.
Mike: I have raw meat literally pouring down into my shirt, all over my body, an hour after I’m watching the team eat food and throw food against the wall. It’s a wonder Winn-Dixie isn’t still around. You’d think, with great employees, great quality. So as that raw meat was gliding down my neck in slow fashion, you just have one of those moments of clarity. I wasn’t following Jesus yet, but I know I had a lot of clarity in that moment. Before that meat hit the ground through my shirt, I already knew I was done. I immediately went to the boss and was like, “All right, well, y’all have a good time. I quit. We’ll see you later.”
Chris: And are you still covered in meat? Did you take some time to clean up, or did you go straight home?
Mike: I forget, I used something there to rinse off my neck. I think I even took off the shirt and changed into a T-shirt. Got in the car. I just immediately went home. I was done.
Chris: You didn’t tell anybody what happened? You were just, “I’m done.”
Mike: Yeah. I wasn’t even going to explain it. I wasn’t interested. The whole thing wasn’t going to work out. And again, they went out of business not too long after that. I can’t imagine why. But there’s something about when you’re working at a job and raw meat glides over your body. You really think through your priorities.
Chris: That’s kind of a job killer.
Mike: Yeah. Hey, kudos to the people out there who are stocking the shelves tonight. We thank you for your service. And if you’re okay with raw meat hitting you in the face when you’re taking out the trash, more power to you.
Chris: So just take some precautions. You might want to double bag that.
Mike: Wear gloves. Double bag. Or a helmet, you know, some pads.
Chris: So your bad night, because it was during the night, right?
Mike: Early morning. It was like 1 a.m. or something.
Chris: My bad day.
Mike: Yeah. I mean, you took down a company and almost ruined thousands of lives, and I took out the trash. Well, we don’t need to compare the differences. No, it’s fine. They’re really just the same scenario.
Chris: I’d gladly trade positions with you and get meated.
Mike: Get meated. That’s going to be a new phrase. Have you gotten meated at any of your jobs before?
Chris: It’s one of those things you’re not expecting, right?
Mike: To be honest, I wasn’t a believer yet. But if we really want to go there, I was thinking, when I was driving home: okay, I clearly didn’t want that job. And honestly, I didn’t want to be around a team that acted that way. Not because I think I’m better than them. Frankly, I feel like if I was in that environment long term, I would probably join them, just by association. Before you know it, I’d be eating the inventory and throwing icing all over the place and laughing about it. And I just didn’t want to do that. So there was something in me even that day, which I give God the credit for, because I don’t think it came from me, that had the mindset of: “Hey, I don’t think you’re supposed to be here. This is not your future. Whether or not you’re looking for a career move right now, you need to be walking with wise people and not associate yourself with this.”
Chris: I’m glad you say that, because there was a little bit of a wake-up moment there for me too: is this really what I enjoy? It did kind of point to the fact that I was working pretty long hours there and maybe not taking care of myself. So it made me question some things, and I don’t think I stayed in it much longer after that. But it taught me some good lessons.
Mike: What’s an example of a lesson you learned from that?
Chris: I can think of several, but one that comes to mind right away is slow down. Slow down. Make sure you are thinking about what you’re doing. The work will get done, with better quality versus quantity. And I would say that’s helped me in whatever I’ve done beyond that.
Mike: It’s really funny you say that. The other day our group was going through Proverbs 18. I’m not going to read through all of it, but if you go back and read Proverbs 18, my takeaway is that it talks a lot about slowing down by wisdom. It talks a lot about the opposite of wisdom, the folly, like when we run our mouths or we’re too quick to talk. “A fool’s lips walk into a fight, and his mouth invites a beating.” “A fool’s mouth is his ruin.” “The words of a whisperer are like delicious morsels; they go down into the inner parts of the body.” I’m not going to read through all of these, but the takeaway is that there’s so much to be said biblically about the Lord being slow and patient, and even, multiple times, speaking in a whisper. To the point that, like you said, if we don’t slow down, we couldn’t even hear him. But by default we do the exact opposite. We’re racing and going, or talking or yelling, or we want the next word in, our opinion, or the quick comment on social media. So that’s a good word for me to hear you say. Okay, I was clearly going really fast between the test environment and the production environment, so fast that I made a colossal mistake.
Chris: Yeah, you’re right. Part of me was just thinking about that meat slowly rolling down into the most inward parts of your shirt. But really, the takeaway for me there is that there is no test environment here in real life. We have one shot here, and we need to be very considerate and deliberate about what we do and how we spend our time. And also who we spend that time with. It’s for keeps, right? Are you familiar with that phrase, “for keeps”?
Mike: Why don’t you explain it for our listeners, for people who may not be able to relate?
Chris: Sure. Growing up, whenever we said “for keeps,” we meant it was for real. Something was actually on the line.
Mike: For realsies? How would the youth of America say it? For reals?
Chris: Slap. Dab.
Mike: What do the kids say these days? You have an older child than me. You tell me.
Chris: For keeps.
Mike: I don’t know why I’m yelling. But like you said, we’re in a production environment all the time, and we’re almost one keystroke away from making a big mistake. But also maybe one keystroke away from doing a really awesome, godly thing that he’s calling us to do. You said there were a few lessons out of that. Did you get another lesson from that experience?
Chris: Have backup. Make sure you have things backed up in a good way. Not a constipation kind of way. Make sure you are keeping things backed up.
Mike: I wasn’t thinking that.
Chris: In a technological sense.
Mike: I was not thinking constipation at all. Now I am. Look at your face. Did you have another one?
Chris: There’s the restoration process. In this case it was restoring files and data. Do you say data or data? (Two pronunciations.)
Mike: Data. Like, there’s a bunch of data we’re going to look over.
Chris: I’ll say data. I have heard people say it the other way, though.
Mike: I know, but that’s weird.
Chris: So, restore the data. And of course you can apply that to life, the restoration that comes. And also the fact that I had help that day. People were helping. They weren’t saying, “Hey, you must fix this. You messed this up.” It was, “Let’s just get a plan.” They were jumping in to help me out. They were senior-level programmers, and they just knew what to do. I remember having an image in my head of them walking toward the room where they were going to have a conference to figure out how to fix my mess, and it looked like the Earp brothers in Tombstone walking toward the OK Corral. And I’m like, I’m thankful they’re here.
Mike: You’re like, help me.
Chris: Help me, please.
Mike: So: slowing down, having community. It’s funny there are themes in this, because we weren’t necessarily preparing to talk about that. But taking your time, and knowing that even the Lord will restore. He’ll redeem, if you’ve made a mistake. By the way, we would love to hear your worst day at work.
Chris: Please make us feel better.
Mike: Contact us. You can leave us a voicemail on our website at nqtshow.com, or send us a message on social media. For real, we’d love to hear your worst day at work story, because if we’re all honest, everyone listening to this has a worst day at work story. And it’s not to make fun of each other, but I think we can mutually encourage each other, because we’ve all been there. We’ve all made those mistakes, and maybe we dwell on them too long. You probably beat yourself up for a season over that mistake. Maybe a couple of seasons. I kind of did, feeling guilty that I took that job in the first place, or that I should have read between the lines sooner. I dwelled on that a little too long. We need each other to be able to talk about that. But it’s awesome, on this side of things, knowing that the Lord helped and redeemed both of us through those scenarios, right? Your info was restored, and maybe it gave you clarity for what to do in the future. Not because you made the mistake, but it gave you clarity. And I didn’t run around with a crazy middle-of-the-night stocking crew around the city, wreaking havoc with meat and cake icing.
Chris: Yeah, that’s an unusual gang of stockers.
Mike: We’d call ourselves the Winn-Dixies.
Chris: But one of the things, Mike, that’s a takeaway…
Mike: Thanks for saying Mike. Thank you, Chris.
Chris: Michael.
Mike: Thanks for knowing my name.
Chris: There’s empathy for others when they make mistakes. I think that was one of the lessons God wanted me to learn. When people make a mistake and you know they didn’t mean to, I can relate. A bit more patience in that. So, a lot of takeaways from that.
Mike: That’s a good word. That’s probably a really good word to end on. Can we increase in our empathy? Not so much when we make a mistake, but when others around us make a mistake. Because it’s funny how quickly we get bothered or aggravated. We talked about customer service, and the bar has gone down on some of that lately. But some of these people are just making mistakes. They’re trying to get by. It sounded like I got choked up there for a second, but I promise I didn’t. I’m not crying. They’re making mistakes. So show grace and empathy to someone, because we’re not perfect. Jesus is perfect on our behalf, so we can extend grace when people make mistakes. And like you said, maybe be one of those people who can step in, not even ask questions, just jump right in and help someone.
Chris: I’m thinking of those who were closest to Jesus during his walk and ministry here on earth, and the mistakes they made, and the lessons learned in that too.
Mike: And how patient he was along the way. Very patient. Well, one person we don’t have to be patient with or show empathy to, I think we get a free pass here, is Mark Wahlberg.
Chris: Yeah, I would say that. Mark, if you’re out there, don’t make me write a query.
Mike: Oh, man. Those sound like some really manly fighting words coming from your side of the room. Also, you’re going to come get meated, my friend. We’re coming your way to pour that raw meat.
Chris: Get chicken-necked.
Outro: Thanks so much for joining us. Please consider rating and reviewing our podcast and hitting subscribe on whichever platform you prefer. Remember to keep moving forward, because we’re not quite there.
