Latest / You've Been Heard / 403- Why Home Labs Beat College Degrees w/Thomas J. Sweet

Transcript

403- Why Home Labs Beat College Degrees w/Thomas J. Sweet · You've Been Heard

• 0:10
  Speaker A: Everyone, Tom Sweet, welcome to you've been heard. Let's just start off with the brief breakdown and what your day job is right now. Let's start there.
• 0:20
  Speaker B: Sure. So my day job, I'm CIO of a private equity backed portfolio company. We've acquired eight companies. And so in my role I'm doing everything from software development, large language model work, AI strategy, educating the executive team on AI, running security end to end, Azure security, Microsoft 365 security, obviously of the policies, the budget, the purchasing, the vendor management, mergers and acquisitions, due diligence, working with the board, helping the board with other companies in their portfolio that either don't have a CIO or have a managed service provider and providing a second set of eyes on those decisions. And then my team handles support, cameras, physical security, phones, telecom, everything, some app development, website work. So pretty much everything that goes on in IT in a small company, we do one way or the other. Here.
• 1:19
  Speaker A: Let's start with what's your recipe or how do you deal with all that? How do you break all of that down? What are the steps?
• 1:27
  Speaker B: I enjoy this type of work. Not everyone does. There's a lot of people in the CIO community who almost pride themselves on either not being technical, never having been technical, or no longer needing to be technical. And the nature of my current role is I have to be deep into this. In my previous role at GM Financial, I was, you're leading 130 people. And so there was a lot that I didn't understand of the ins and outs of the different financial systems, for the different financial systems my team worked on. Right. I had different teams that worked on the lease system or the remarketing, which is when a car came off of lease. Right. I was trying to manage three levels of management and drive business transformation, but here I'm trying to help as a leader building the ultimate IT team and the ultimate IT service for a private equity company and to help deliver business value through technology. It's a different role and I love this, I love staying engaged with it. And so that makes it so much easier.
• 2:34
  Speaker A: What part of the business do you need to know and understand at your level right now in order to be effective as an IT leader? So maybe just explain the private equity or maybe explain the mergers and acquisitions piece to IT and the pieces that an IT leader would need to be very, very aware of. In other words, are you at a stage where you need to lower customer acquisition cost and the cost of acquiring customers is high and there's a certain churn Rate, like what are kind of the dynamics of the business piece? And then also, so you've got that aspect, right? And then you have like the cost of a, a lead or a customer, right? You've got that aspect. But then you also have, when you have companies being acquired or looking to be sold or being purchased, you have this aspect of when you look at a company, what are the red flags or dangerous areas that would make someone say, no, we don't want to buy them because of this. And so it's kind of like at what stage, how do you break it down? Like where do you start in it with all of that? And how does it add value to the business that's evaluating businesses and purchasing them and selling that?
• 3:46
  Speaker B: So when we look at acquiring companies, there are people who are early on in the space for that. They're looking at the companies that they're going to acquire, they're looking at their sales, their ebitda. There's a number of. They have forensic accountants that will go and investigate the history of the company, make sure that everything is up and up. I'm not involved at that point. I am involved much later in the end. And probably they're gonna, if they make the decision to buy the company, regardless of what I say, it's probably gonna happen. But I need to be able to articulate the investment. Hey, you know what, they have old systems, they have this old erp. They don't have multi factor authentication, maybe
• 4:28
  Speaker A: data props, data leakage or something other.
• 4:32
  Speaker B: They may have been hacked. The Port 3389 is open to the whole world, you know, things like that. And so you're looking at, okay, there's a risk here. There's a period of time that we have risk as a company because we have cyber insurance, right? But we have to make sure that how quickly can we get them migrated, get them educated on hey, is M365 here is multi factor authentication. We're going to move you to a passkey. After that we're going to lock some websites that shouldn't be accessed, right? There's a whole bunch of cultural change and change management. So I'm involved prior to that, not doing an audit, doing the assessment, doing a report and presenting it. Here's what I found. And then a lot of what I'm doing is right at the beginning because day one, the CFO's team was looking to get at their financial data and I have to find ways to get that securely opened up, but also work on the cultural change of Changing it. However, everything else is changing for these, these companies. Right. They're. The day they get paid is probably going to change. Right. They're how they do business, how they do service, how they do construction. The. Maybe there's different policies for company vehicles that weren't necessarily in place prior. So there's a lot of organizational change management. So it's working to do that without doing that. Right. It's changing it without being too aggressive. Right. Because it's overwhelming. Right. Because it's overwhelming for someone who's never had any cyber. Right. They're running admin, they're running global admin as admin on their computer and that's the way it's always been. And MFA is annoying, so they don't do it to. Coming into.
• 6:09
  Speaker A: That's amazing. That really is still a thing. Yeah, it's still, it seems like it's one of the most general best practices. But you're, you're talking about a, a company with 10 people.
• 6:19
  Speaker B: 50 people.
• 6:20
  Speaker A: 10 people. I can see 50 people without multi factor authentication. Yeah. I mean even 10. It's like, it's like you shouldn't even do it as one person.
• 6:28
  Speaker B: Yeah. So that's kind of where I'm at there. Right. So that's part of that piece.
• 6:34
  Speaker A: Okay. It's like when a company comes in, it's kind of what are kind of the problems and how do we go through a checklist? And it's kind of like you've got revenue, ebitda, customer acquisition cost, and like, oh, wait a second, is our customer acquisition cost going up? There's all these different factors and there's kind of like a tier that you've got to like kind of
• 6:54
  Speaker B: go through. Right? Yeah. And so when you look at industrial refrigeration, right. This is warehouses, huge companies like a Cargill or a Butterball Turkey or a Tyson Foods. Those size companies, Cheesecake Factory Warehouse, not your local supermarket, not the Walgreens Cooler. I mean these are huge facilities. So there's a limited number of them. It's not like you're selling a scooter. Right. And there's a whole country full of people that potentially could be a scooter buyer. Right. There's only a small number of people who have this. So one thing that it did is we built a SaaS app. So we decided, hey, let's help reduce the cost of customer acquisitions. We'll make a SaaS app that'll take refrigeration plans. I mean, it's a specific type of plan that they use for refrigeration plants and piping. Right. And not just refrigeration, but industrial type work with pipes. And we use some machine learning and some LLM to create a maintenance plan for the user. Right. So the user will upload the plan. We'll create a maintenance plan based on a lot of effort on the back end and then give that to the user for free. Now the, the trade off is the contact info for the user. User uploads a plan, we'll give them a teaser or a small report. You want the full report you will email with you, but there's no half hour meeting required. We just need like a legit email.
• 8:21
  Speaker A: Right.
• 8:21
  Speaker B: And then we'll send it out. And that's to help to acquire more customers. Right. It's a lead generation tool. And so the costs of customer acquisition there will be much less than someone going and knocking on doors and trade shows and other areas, other approaches that are more costly.
• 8:46
  Speaker A: Most IoT leaders don't need more technology, they need less noise. Over the years, infrastructure quietly gets complicated. Multiple locations, multiple Internet providers, different contracts, separate bills and reactive support. Nobody plans it that way, it just happens. What we do is vendor neutral advisory. That means we, we don't sell platforms or force change. We start with low friction areas. Internet telecom, Microsoft licensing. Places where complexity builds quietly and can usually be cleaned up without disruption or capex. Sometimes we find savings, sometimes we find nothing. Either way the outcome is the same. More clarity, less distraction and it that's boring in the best way possible. If you want a second set of eyes from people who sit on the buying side of enterprise infrastructure every day, just go to you've been heard.com and answer the questions to simplify, streamline and save. Okay, so you're the right person to ask for this then. Obviously with the size of your team, you have to have very, very good partners when it comes to security. If we were to just break down the security aspect of whatever companies being merged together, you've got things like, well if you were talking about multi factor authentication, I'm going to be talking about endpoint detection and response and event management and email security and proactive security training, incident response, compliance reporting. Do you have good partners? Do you love using msp? MSSP for that one? MSP number zero. So what do you do?
• 10:23
  Speaker B: You do everything in house. We have a lot of great tooling.
• 10:26
  Speaker A: Okay, so let's just keep going. So some of the bullet points that we have on here to talk about today, AI native organizations, role consolidation and the End of heavy teams. What does that mean? Handoff heavy teams.
• 10:39
  Speaker B: Yeah. So when I work for the larger company that I just mentioned, they had all different silos. So let's say you bought application that need a single sign on, right? That would have to go to an IAM team, they would have to contact a different team for DNFs, they would go to a third team. You have to go through change management boards. Right? We're a small company. If I buy an app today and I want to make it single sign on, and I paid the single sign on tax when I purchased it, the extra $10 per user per month, whatever they charge, go, and I can go to my DNS and add the entry, I can go into Azure and create the enterprise app, and then I can connect my purchased app altogether and be done in 15 minutes. And so another company that might take them four weeks to go through that process, when really it's only because of change management, because of handoffs, because of silos, only one team is allowed to touch DNS, only one team is allowed to touch iam, only one team is allowed to do this. And larger organizations slow down because of that and things get confused. There's backlogs, there's internal politics. Whereas a smaller company, I mean, we can go much faster. If we fail, we fail forward. We have to do a rollback. We're like, oh, we made a mistake, let's fix it and go forward. And I've made mistakes, trust me, a lot.
• 12:03
  Speaker A: We make a lot of mistakes. We made two years of mistakes on trying to do a website the wrong way. And then finally we hired the best branding guy in the industry and he did it in about 30 minutes and handed it off to us. We're like, okay, great, AI native organizations, what does that mean? What does that mean to you?
• 12:20
  Speaker B: Well, there's all sorts of podcasts that have different definitions about how well you're doing. But what we're trying to do here is get at least all the executive team and the people who are one layer below and get them educated on how to use AI strategically, not just tactically, not like, hey, paste this email in and rewrite it. It's using AI as a partner. But there was a book that we read, I made, kind of made everyone read it, which was the AI driven leader. Now, it is from 2024, so it might be a little dated for some people, but it was really probably good at helping people understand how to use it strategically, making it a partner for what you're doing. Every Day, not just, hey, solve this problem, but here's the backstory. Here's what I've done to solve a problem. I'm concerned about this, this, and this. Ask me questions until you're comfortable with a solution.
• 13:14
  Speaker A: I believe everything that you just said is completely on point. And people that don't know, you don't know. You don't know until you don't know. And I have been having a very long debate back and forth with one of my friends who is on an entire offshore coding team. And he builds, like, basically healthcare ERP software for another large country that may speak French. And so I, I basically, I'm like, look, my prediction is that the majority of the coders that were, as of three years ago, are going to be gone. And he's like, absolutely not. And then there's like, I have another coder friend that's like, yeah, if they're not on board, they don't get on board now. Forget about it. Because to your point about your employees and teaching them, if you don't learn this now and you don't start to learn the tools and have your own sources of data built up and you haven't learned, and like, Claude is a good example, because you can have artifacts or you can have skills, you can have all these things that are kind of built up. And that takes a while. And Greg, our producer, I mean, he's been doing this for years. And when he starts talking about cloud, I mean, he's got like, all these skills built up. He's got multiple agents running up in cloudflare. He's got all apps. He built our podcast reporting app and scheduling and questions that we ask people and crunching down data and turning into infographics and passing it off to production team. And it's all our own custom software now. And it just, like the light bulb just goes off in your head and you think to yourself, there's the most in danger. I don't know if you agree with
• 14:53
  Speaker B: that or not, but, well, okay, so let's just back up to what you said. So you have talked about Claude. They get hooked. They got commands, they get skills. There's a lot of people on Twitter posting great links to grab all of those. So there's people who put investment in and now they share them, right? So you can grab all those. And There was a LinkedIn post about someone who was upset that the SaaS app went from 70,000 to 140,000 for renewal and they built their own app. I don't know what the app did, right? But they basically didn't renew a SaaS app because they're like, we can build this in three weeks. And they built it three weeks. And if you watch any of these UFO shows that talk about the aliens, that kind of purpose built for the commission and that's the way software is going now. It's like it's purpose built, right? You don't necessarily. You can build your own software.
• 15:47
  Speaker A: Building our own CRM. I was like, never thought that would be possible. I'd be like, nah, it's going to be all screwed up. There's going to be all kinds of bugs, drop downs and plugins and like, at least we're building like more point systems now. Kind of like to that MIT article, right? More talking about point systems and kind of starting out on that. Because I don't want to go like all in just yet. We're building an app to just do the vendor discovery because we sat down and we're like, okay, how do we consolidate all our apps? But okay, how do we teach our employees to use it? Oh, I know what it was. What about Cowork? That's like something that's really kind of a rogue thing. It's going to cause so many problems for security. I mean, if I let it take over what I want to let it take over, it will. But the thing is like an end user basically. It will take over your browser and you can be like, hey, could you make sure to like just answer my emails for me and constantly search my emails and can you send an email on my behalf? And it'll just, it'll literally pull up your browser. It'll be clicking on Gmail or whatever. It'll click the send, hey, I need you to kind of just go through all my Google Drive folders and like, will you search for this keyword and kind of organize everything and I'll pull up all this stuff and then I want you to build PowerPoint presentation and can you do that project on the side and then do all. And you can do it coding thing on it. It's all this stuff. You're not even there. I just see that being a massive security issue for some for sure.
• 17:11
  Speaker B: Because here's where it can go bad. You ask it to go to a website and click on Salesforce for example. But someone has an ad on Google Ad Works. That's a malware that says it's Salesforce and it's not right. And so the AI is like, oh, Salesforce link. I'll click on it and it's not the real salesforce. I mean, so those are the issues. I mean, I'm not worried about data loss prevention and people deleting everything.
• 17:36
  Speaker A: So what do you think about my prediction? What's your prediction 18 months from now? It doesn't have to be AI. It could be anything. What is everyone.
• 17:42
  Speaker B: So the prediction is that you're going to see more disruption in the programming market because like you talked about, there are people who still insist like, hey, AI is too buggy, but they're not figuring out that, hey, you know what, it can fix the bugs, right? First of all, bugs existed before AI code. The security issues existed before AI code. But the AI is only going to get better. And, and so there's going to be a tremendous disruption in that market. And, and was, and every time they
• 18:12
  Speaker A: accused it of not being able to do something, like two months later, I was like, oh wait, I can do it now. Yeah, but this, now I can't do this. Yeah, it's happened.
• 18:18
  Speaker B: At least we're going to see the people who are embracing it in their job. Right? You're going to be hired to deliver an outcome. Any of your computer science grad, or you're a marketing grad, or you're someone who go for a formal education, but you can deliver business value. We're talking role consolidation is how do you solve a problem for a business owner, how do you solve a problem for a company and you're using AI to solve the problem. You know, your pedigree may not matter, most likely won't matter how you solve the problem may not matter whether you did it intellectually or used a tool to do it. It doesn't matter. You, you got the right outcome. And I see startups are that way. The one piece of team used to be a two piece of team, now they're talking about one pizza team. Because you don't have as many team members because AI is filling in gaps in knowledge. So.
• 19:06
  Speaker A: Yeah, well, I mean, if people don't start now, if you don't start training your employees now and everything people need to get, there's like a certain. Although even though we've been switching LLMs and stuff like that back and forth, people are going to start to realize I need to organize the data in my life better. And it's kind of like if I wanted to do a certain project on a certain thing and it's like, well, first give me the brand guide. So you got to lay out a brand guide. You got to be like, these are the Colors we use. These are the logos. They've got. I mean this aspect ratio. You've got to kind of lay all this stuff out. Otherwise you're just kind of like throwing stuff at it in a random.
• 19:44
  Speaker B: Why don't you say go, here's my website. Go create the brand guide.
• 19:47
  Speaker A: Yeah, but the brand guide is also the voice. It's also the taglines. It's also, it's like. Because like we have a tagline that's having a seat at the. Having a seat at the table is nice.
• 19:58
  Speaker B: Yeah.
• 19:59
  Speaker A: Heard nicer. But it'll change it to. If we don't say like it's exactly that this the tagline and can ever change. They'll say something like it'll just be like having a seat at the. The roundtable is nice, but it's so much more superior to be say something like it'll just like kind of screw up the tagline. Stuff like that.
• 20:17
  Speaker B: I would have it created for me and I'd edit it and then tell it I didn't like it and then they would fix it for sure.
• 20:24
  Speaker A: Okay, what's the best use of our time? How do you decide that?
• 20:31
  Speaker B: Again, we're trying to focus on what makes us valuable for exit, what helps us make money. How do I get the sales team in front of more people? How do I get them the information they need?
• 20:41
  Speaker A: Granular. I mean literally more granular. Like do you use a planner? Do you write down things at. Do you like do two week sprints and do you like what didn't go well?
• 20:53
  Speaker B: There was only three of us.
• 20:54
  Speaker A: Right.
• 20:54
  Speaker B: We are. It is interactive on teams all day long. Like we have a shared chat and it's back and forth all day. Right.
• 21:01
  Speaker A: And then is it literally just a stream of consciousness or are you guys.
• 21:05
  Speaker B: Yeah, I think so. I mean it's a stream of consciousness that I have. Right. I get the CI, the CEO that calls me. I mean he's the only one that gives me orders or orders, but a direction or requests. Right. But ultimately it's me making a decision as to how we operate. And there is no performance improvement plan for a cio. Right. It's. If you don't solve the problems, you're tossed. Right. It'll put you on a pip. Right.
• 21:31
  Speaker A: But you have to kind of break things up because you might have different projects going on at one time. Yeah. How do you break down your projects?
• 21:38
  Speaker B: I mean, breaking it down in markdown language, because that's what AI is using. So AI uses MD files on markdown. Right. So it used to be you'd use like Jira boards, but Jira and Java and all that, right? Or there was Azure DevOps boards, right? But if everything is going to AI now, so everything is in markdown, like I will do cloud plans, I will work through markdown files and keep all my information there because that way the AI can read it and then act on it.
• 22:09
  Speaker A: Keep going. What else? Teach me something there, because that's not what I do.
• 22:14
  Speaker B: Okay. So, I mean, that's what I do, right? I. I do have GitHub boards for some bugs and stuff that we'll, we'll keep track on. But a lot of it is. But we're small enough, like we don't have to have all this stuff. Like, we don't, right? It's. You're working with the COO when we need this, this and this done. So, okay, we just go do it, right? We have a ticketing system that comes in so that the people that work may well handle a ticketing system if someone's printer doesn't work or they got a software application that aids installation. So we'll track all of that. But a lot of the strategic stuff is interactive in meetings, and it goes relatively fast.
• 22:51
  Speaker A: What's the most important message or topic that you would want to talk about in it that you would want to get out to the world? That's important.
• 22:57
  Speaker B: It's hiring people who have a love for the craft. Hiring people who love this type of thing. They do so much better. Like, I've never hired anyone. They had a home lab that didn't work out as an employee.
• 23:11
  Speaker A: That's priceless. Actually, that's a priceless piece of advice.
• 23:15
  Speaker B: But they can tinker, right? They can figure out how something works. I mean, think about what that is, right? So no one's helping you build this home lab profit, right? People buying a Raspberry PI or they're getting an old computer and they're putting a Linux on it or something and they go find out how to get some app and make it work and connect the network, right? So, yeah, I love people who love to tinker can figure it out. They have the ability to learn because they demonstrated learning, right? Everyone I've interviewed, every single person I've interviewed. Oh yeah, yeah, I'll learn anything you want. Oh yeah, that's fine. Right? And I don't believe that. Right? But people who've half a home lab, they've learned something. They've demonstrated to me that they can learn how to tinker, how to Solve a problem so well.
• 24:06
  Speaker A: Okay, that's the it thing. Like you have a home lab. Are you able to step out of your IT body and step into the CEO body? What do you think he would say?
• 24:15
  Speaker B: Unless I think he'd agree, but I'd have to explain the why. The why is people can troubleshoot, people can solve problems, people can learn, people can overcome challenges without documentation, without all the information, and persevere. Right. And that's really what you hear about hiring people based on characteristics and personality and ability and not hiring on skills. Right. But you're hiring on people who can do this. Now, obviously, integrity is another characteristic you'd want in an employee. And then the home lab doesn't necessarily test integrity specifically unless they were stealing the software that it ran on.
• 24:54
  Speaker A: Yeah, no, I guess what I'm saying is for an IT guy, hiring the right person, it's. I want to hire someone that has a home lab, someone that's curious, someone that's always been curious.
• 25:02
  Speaker B: That's not the only thing. Right? Yeah, but I'm just saying is one
• 25:05
  Speaker A: time we basically searched all of the transcripts and everything of all of the guests have ever been on the show, and curiosity was like, on the list, like at the top. Right. Curiosity was probably like one of the top ones. My question to you is, venture capitalists are looking at inserting a CEO into a company. What do you think they look for? I don't think they look for curiosity. I'm just curious. What do you think they look for as this hardcore business leader that we need to run this?
• 25:36
  Speaker B: I think for the. Looking for, if you're talking private equity or venture capital, I mean, private equity. Looking for people who've done it before who have a successful track record of delivering a company. Right. Running a company and making a profit. Profit is a really big deal for a lot of people. Obviously it's a business. That's how they started it.
• 25:55
  Speaker A: So that's the definition of a business. Right. The purpose of the business, like, have we lost? Are we so off track that we don't understand that some people don't off track?
• 26:03
  Speaker B: The purpose of a business is to make it ultimately secure. It's like, no, you have to make money. So if you over go overboard on security and you have no money to hire business development people because all you have are security tools, well, you got to go out of business. Right. If you take everyone's computer away because it's insecure. Right.
• 26:20
  Speaker A: No one's doing any work. So that's a good balance. How how do you sell the. The security budget?
• 26:27
  Speaker B: I sell it because I'm explaining the why. Like, I always, every week or two, I'll. I'll send out an unfortunate list of huge companies that have much better security people than us, that have much smarter people and more people, and they're still compromised, they're still hit by ransomware. I mean, every week there's a big company, a healthcare company, whoever, that got hit by ransomware. And I'm saying, this is the real threat. And then I also can track phishing attacks based on job role and function. And I show, I said, look at these, the executive team, and look at, they're getting 10 times the number of attacks, right? This is the reality of the world we live in. And I think they trust me to make the right decisions there.
• 27:09
  Speaker A: So there was a really amazing point made in the selling of the security budget yesterday. It was, I believe it was Mr. Brian Rowe. And from the outside, like the, the numbers and the money to spend on the security, it seems as if it's like insurance or something, right? Like we're paying for something. There's no real link to the bottom line. But he made like a really outstanding point, which was when we do have the right seam, right. Or whatever, and process, and we do have a lot of the visibility tools in place, we learn so much more about the efficiency of the company and what people are doing. So just the act of, like, implementing security and just this whole act of having a really, really good security policy, there is some kind of return on investment from the standpoint of understanding how everyone works, what they're doing. And there's a layer of visibility into the company that you may not have had before if you did not do that. Make any sense?
• 28:13
  Speaker B: Yeah, it does, right? I mean, we have DNS filtering, right? We have a lot of things in place. So if you really wanted to dig in to see who's going where, I mean, you could do that. But I think the other piece of this is cybersecurity is not going to help us sell, but it could prevent us from selling. So if we had a horrible plan, right, that's going to affect our sell price, like right now, like, everything is really good.
• 28:39
  Speaker A: So if there's any one thing that you wanted executive management to hear about it, or the world to hear from it, leadership that they don't normally hear. You don't have to stop it here. What would that be?
• 28:51
  Speaker B: It would be stop saying it. And the business, it is the business. Like, you don't say finance and the business or marketing in the business. Stop looking at it as outside the business because it can help you deliver business value if you edit.
• 29:08
  Speaker A: Yeah, but not the department of it. Is there any other idea on top of that? Is there any idea inside of that that every executive would understand about modern it?
• 29:19
  Speaker B: I think that the executives need to do a little bit of learning themselves on technology. I mean, they expect it to understand all about the balance sheets and all about how the business makes money and all these pieces. However, they need to understand how their phone works. They need to understand the basics of a changing technological world because they need to be able to use AI. They need to be able to use technology to improve their department's functions.
• 29:49
  Speaker A: Do they need to build a lab at home? Should we have them build a lab at home?
• 29:53
  Speaker B: They probably wouldn't do that. I don't think they would do that.
• 29:56
  Speaker A: Is there a checklist? Like, what is a tcip? What do they need to know? Like, do they need to know?
• 30:02
  Speaker B: I would look. Separation anxiety. Like how to spend one day using Outlook for web as opposed to Outlook client. Right. There's a lot of Outlook separation anxiety in the world right now. Outlook is their file transfer tool, their CRM, their data warehouse.
• 30:21
  Speaker A: So don't use email as a database.
• 30:24
  Speaker B: No, don't use it as a data warehouse. Don't use it as a file transfer tool.
• 30:29
  Speaker A: It's amazing. So next point, let's just go through to the top five things that C levels need to know that they have to know about it. Don't use Outlook as a file transfer, file tool or database.
• 30:41
  Speaker B: Okay, Next thing, we really don't monitor what you do because we're really not that interested in you to try to look and like, it's just not that interesting. I got enough other crap to do. Right. Honestly. So that's two. Okay, now read is if we want to wipe your computer to fix it, it's probably gonna be a lot faster than if we try to spend three days fixing whatever is wrong. So that's another thing.
• 31:08
  Speaker A: Can we add some vocabulary into this for them? What would he call that desktop design? I don't know. There's certainly some like, we have this urban dictionary of IT terms that we love to add to every now and then we gotta really bring that up. We could easily publish this book, Herding Cats Turning the Titanic. We've got all kinds.
• 31:25
  Speaker B: So we call it a fresh start. So Microsoft Autopilot is called Fresh Start. So if we want to do a fresh start, just like send a signal, wipe it all the stuff comes back from OneDrive.
• 31:36
  Speaker A: Can I get a fresh start? Yeah. This is what they need. So terms that sea levels need to know. Fresh start. Can I get a fresh start today? I'm done.
• 31:43
  Speaker B: Yeah. And then the next thing is, Chrome and Edge are not that different and they both come from Chromium, but there's a lot of people who are really stuck on Chrome and Chrome and Edge both come from the Chromium open source project. Right. And not that different.
• 32:00
  Speaker A: Okay, number five.
• 32:02
  Speaker B: Number five is, I'm sorry, you have to sign in again today to Acrobat, but we're using single sign on and that's just the way it is.
• 32:11
  Speaker A: So you get a lot of complaints about that.
• 32:13
  Speaker B: Yeah. Because we sign in with our M365 account to the computer. Right. The computer's tied to Entra ID, so you sign in with the M365 account and you open a browser and it automatically knows who you are and all that stuff. But Acrobat, it's a Windows client app, so it has to do a single sign on and the token expires and you gotta kind of put your finger on the fingerprint button or the rogue.
• 32:43
  Speaker A: It's a rogue secondary.
• 32:45
  Speaker B: Yeah, it's using M65, but it's three seconds. And so most. So number five really should be. Most cyber attacks probably are from people who don't want to be inconvenienced for three seconds. Whether it be scrolling on the phone because it says this is an external email. I mean, that's been a complaint. It's like, oh, I. When an email comes in, I have to scroll because we got this message. That's an external email. Like you get a scroll. Okay, two seconds.
• 33:12
  Speaker A: Are they acting on that message that says this is an external email though? Are they. Is it making them?
• 33:17
  Speaker B: I would hope so. But does it make you think? No. Our email system has nine or ten different ones. You know, this is an invoice, this is a first time sender, this is asking for banking information. So it goes, it's dynamic, so it changes and it has different colors depending upon the perceived threat level and what's being asked.
• 33:37
  Speaker A: Super cool. Do you guys use a cyber awareness training program?
• 33:41
  Speaker B: We have that. We do the phishing sims.
• 33:44
  Speaker A: That's good. Super cool. We have to end with one more thing. Okay, so again, the moral of this episode, I think the one that I'm most excited about is if someone has a home lab, that's a good sign. I don't know how you want to say there's got to be a quote around that. I never hired someone with a home lab that hasn't worked out without.
• 34:07
  Speaker B: I think that's true. No, I mean, that's what I've said and it's proven true. Now, obviously there's probably a hundred or five hundred of your listeners who could demonstrate that. That's always the case, but it's hard.
• 34:23
  Speaker A: Plenty of us keep home labs, but they ended up arrested next week. You didn't say that.
• 34:26
  Speaker B: Oh yeah, but it's a love for the craft, right? And so what happens is people who love this have that curiosity, they're willing to, to learn something new, they're willing to try something. Because I work with people who like, I do firewalls, but I won't do load balancing and I won't do network. That's not my job. My job is firewall.
• 34:45
  Speaker A: What I don't understand. What do you mean? I do firewalls, but I don't do load balancing. And yeah, what do you have to say to them? Like, that's kind of dangerous to have that mentality, especially in a world where technology is changing so fast.
• 34:59
  Speaker B: It can be dangerous. You have to adapt to a changing world. And right now the changing world is AI and the changing world is role consolidation. So if you want to be the CEO of you, if you want to be heard, if you want to be able to deliver for your family or for however you, wherever you work for money, you have to adapt to this changing world. And that's either building your own LLM on your home lab or using AI at work, or showing people at work how AI can help reduce the costs by increasing how much work you do,
• 35:35
  Speaker A: It's a great point. And if there was one massive challenge that you see coming up in the future, if there was one big challenge that you could fix in it tomorrow, what would that be?
• 35:44
  Speaker B: People have to adapt. And I managed a QA team for a long time and part of why I thought I was brought in was to transform them into, move into a more of a multi dimensional role where people were developing software, they're testing it, they're deploying it, and a lot of people just didn't want, they thought that the job they signed up for at this point 15 years ago would be the job they would have for the rest of their life. And that's not what happened there and that's not what's going to continue to happen. The people who were developers today, they're going to have to change to adapt. The people who do firewalls today are going to have to adapt.
• 36:18
  Speaker A: That's good. Mr. Tom sweep. You've been heard. It's been a pleasure having you on the show.
• 36:26
  Speaker B: Thank you, sir.
• 36:27
  Speaker A: Have a good day.