Episode 19 - Part 2 - Launch First: How AI Drives Smarter Startups with David Hirschfeld

In Part 2 of our conversation with David Hirschfeld, Founder and CEO of Tekyz, we dive even deeper into the future of AI, automation, and startup growth strategies.

David shares how AI is transforming software development, why businesses must reinvent themselves constantly, and how leveraging AI-driven workflows can dramatically increase efficiency.

💡 Key Topics Covered:
✅ The rapid evolution of AI and its impact on businesses
✅ How startups can use AI to streamline operations and scale faster
✅ The role of AI agents in replacing traditional workflows
✅ Why “manual” processes must evolve—or be left behind
✅ The future of software development: What’s next?

This episode is packed with insights for entrepreneurs, developers, and business leaders who want to stay ahead of the curve. If you’re looking for practical strategies to scale smarter with AI, this is a must-listen!

🔗 David Hirschfeld’s Links:
💼 LinkedIn: https://www.linkedin.com/in/dhirschfeld/
🚀 Launch 1st from Tekyz: https://launch1st.tekyz.com/
🖥️ David’s Company: https://www.tekyz.com/

📢 Don’t forget to like, comment, and subscribe to stay on top of the AI revolution!

📖 Chapter Markers

00:00:00 - Intro: Welcome Back to Artificial Antics
00:01:05 - AI’s Rapid Growth: How Businesses Must Adapt
00:06:30 - Scaling Smarter: AI’s Role in Startup Efficiency
00:12:45 - Reinventing Software Development with AI Agents
00:18:20 - The Future of Business Workflows: Automation vs. Human Input
00:24:55 - Real-World AI Use Cases: How AI is Already Reshaping Business
00:32:10 - Practical AI Adoption: Overcoming Resistance & Unlocking Value
00:38:40 - The Role of AI in Decision-Making & Business Strategy
00:45:15 - Challenges of AI Implementation & How to Tackle Them
00:51:30 - The Next Big AI Disruptions: What’s Coming in the Future?
00:57:00 - Closing Thoughts: Preparing for AI’s Next Evolution

Stay Updated:
- Subscribe to our channel for more episodes like this: https://www.youtube.com/channel/UCXz1ADq4dDQ5yPy40GWDepQ?view_as=subscriber&sub_confirmation=1
- Follow Us: https://www.buzzsprout.com/2178171/follow

Connect with Us:
🌍 Artificial Antics Podcast Website: https://antics.tv/
📰 AI Bytes Newsletter: https://artificialantics.beehiiv.com/
🚀 Artificial Antics Business Site: https://artificialantics.ai/
💼 LinkedIn:   https://www.linkedin.com/in/artificialantics/
🐦 Twitter: https://x.com/anticslab
🍏 Apple Podcasts: https://podcasts.apple.com/us/podcast/artificial-antics/id1694398244
🎧 Spotify: https://open.spotify.com/show/0QpTQhJrdXNeqc5TX8clmj

Transcript

Natasha: [00:00:00] Welcome back to Artificial Antics, where Rico and Mike will talk about the implications and opportunities around artificial intelligence, machine learning, and deep learning.

Natasha: On this episode, we continue our conversation with David Hirschfeld, CEO of Tekyz. Last time, we discussed his AI journey, the launch first approach, and how startups can use AI for growth. Now, we're covering AI adoption, workflow automation, and the future of development. David also shares insights on scaling businesses with AI.

Natasha: Let's jump back in. 

Rico: What's up everybody. Welcome back to artificial antics. And I'm here with my cohost, Mike. Mike, if you want to say a quick hi, 

Mike: Hey, everyone. 

Rico: we're here with David Hirschfeld. And as you remember from our last episode, we talked about David's company techies and one of his products that he offers called launch first.

Rico: Uh, David's been in tech a long time and we kind of talked about his journey into AI and some successful use cases with AI and without further ado, we'll let. David, get into the business side of [00:01:00] what AI can do for you.

David: Uh, thanks, thanks. Great to see you guys again, Mike and Rico and, um, uh, really looking forward to the discussion today. Um, yeah, for the audience, I'll tell you a little bit about. Me and where I come from. So, um, I was in enterprise when I started in over 35 years ago in software, um, uh, for large companies.

David: I can tell Motorola, Allied Signal, Texas Instruments, and then had my own startup from in 92 and which we built and sold to a publicly traded firm in 2000. And then I ran VP of products for the company that acquired us for the next three years until I cast out again. And started techies almost 18 years ago in 2007.

David: And techies is a custom software development shop. Um, and lately it's a custom AI development shop because that's all there is anymore. It seems like is the focus on AI for, for many reasons. [00:02:00] Um, uh, one is because everybody that's coming to us has some AI requirement. Uh, if not, they're building an AI product, uh, that they want us to build.

David: Um, and also because we automate a lot of stuff internally in techies and recognize that AI is changing every aspect of software development and, uh, design and workflow automation and how we have to approach all this. So, um, um, so it's really captivated us and, and it put us in a position where we are literally reinventing ourselves almost every month.

David: Um, Uh, what, who we are, what we do, how we go about what we do and what direction we're headed, um, to try to stay ahead of this massive wave that is AI. 

Rico: Definitely. And David, just for the audience, can you tell us, like, how could a small business start identifying tasks for, uh, for the automation workflows?

David: So that's a really important question and a tough one [00:03:00] to answer because I could give you a lot of trite. responses on what you should be looking for, manual tasks, things like that. But usually in a small business, a lot of these things are part of your DNA of operating. If you're a profitable business and successful, then you get into this work, this manual workflow of doing these things on a regular basis.

David: You understand and handling all the nuances of what it takes to do these things, not even recognizing how many nuances you're handling because you've handled them so many times. So, uh, if I go when I, in the past, when I've gone through workflow automation with the client, a good example, a friend of mine that runs a really big business network and, um, we did a workflow automation with him.

David: It took three months, not three months of effort, but three months of going back and forth, probably total of 30 hours or 40 hours of development effort. Uh, but three months of going back and forth with him, teasing out all the [00:04:00] nuances, every time we'd come up with a new build and show him, he would realize that he had missed some of the requirements and certain of the cases.

David: And at the end of those three months, um, we had something that worked and this was somebody who spent seven hours every Monday getting ready for this big networking meeting, uh, every Tuesday morning. And it was, it's complex because of the way he runs his meetings and how big his network is. And, uh, Uh, that workflow automation, which he didn't even know he could automate it.

David: But I suggested he should consider doing this based on things he had told me. And he said, okay, let's do it. Uh, let's do it. It takes him now 15 minutes to do his Monday. And he's, every time we talk, he, he tells me, you know, I still use that program you wrote for me four years ago. And I just, every Monday like clockwork and it's just amazing anyway.

David: So, but there was like 40 hours, maybe 50 hours of actual programming work and quite a bit of time for us to tease out all the nuances. So [00:05:00] most, a lot of small businesses are full of these types of workflows and that's not the only workflow he's got. That's really time consuming. Uh, Um, and it rarely is right.

David: So now I'll talk a little bit about like what we're starting to do internally. Um, uh, so we have this idea of trying to document workflows that we have, that we know are repetitive in what we call playbooks, because we want to be able to scale. And if we bring in somebody new, that's going to be. Doing that thing, if it's a marketing task or sales task or development, automation task or whichever it is, we want to be able to give them the playbook for them to learn.

David: So they know what are all the steps to do and what and what are the nuances that they may run into and how to address those, uh, Now what we're start, I'm starting to realize is that for any of these playbooks, we need to be thinking in terms of taking the playbook and now using AI to start to automate that [00:06:00] playbook.

David: You know, asking and asking ai, okay, here's my playbook. Um, uh, uh, for this particular thing, um. Do you see anything that I could improve in the playbook, number one, because it may come up with things that I didn't even realize that are duplications of work, uh, just because it's something we've done so many times and are comfortable with and good with, um, and ask it if there's a way to improve it, and then, Ask it what, how can we automate these activities or should we even rethink the, how we approach this completely?

David: Right? That's the first thing is, should we rethink this? We don't want to disrupt our business, but maybe in the process of rethinking it, we can come up with some tweaks to improve what we're doing and then ask it how we, um, um, how we automate. These functions or which functions can we automate and then ask it to prioritize from the ones that are the least costly to automate and can be done the quickest to the ones that would take more effort and time to automate and have it build a [00:07:00] priority list of automation tasks, each one that we should be able to put in to activity once it's done to see a boost in productivity.

David: Uh, our ability to produce. So the idea for me is, okay, right now I have a, a virtual assistant that's helping, that's doing my marketing outreach for podcast related stuff. Right. And we, and we've got that, uh, playbook really pretty well defined now. So, but as I scale, I don't want to get more of the A's. I just want my.

David: VA to get, be basically be better at doing more of these. And we will hit a point at some point where that's a capacity is hit, but we've automated a lot. Maybe she's now able to handle five times or six times or seven times the capacity she could with the automation. And we bring somebody and all of, and AI is documenting the changes in the playbook along the way.

David: Um, um, now we bring new people in and we can scale much faster, [00:08:00] much bigger. Uh, with much less cost. So that's how I approach it internally. I don't know if there are, is a better way to do, but I think it's, I feel pretty solid that this will be hugely effective. Uh, um, and then of course, there's all kinds of tools that you can use to do different pieces of this automation, depending on the thing that you're trying to automate. But that's what I would say. If you're a business, think in terms of playbooks, what are the common things that you do on a regular basis that are manually require today, require a person to do it, and it could be a phone call, you know, and voice, it could be, um, uh, sending communications of custom communications with people are responding to community communications in a very specific way and be able to document.

David: Um, the results of those, it doesn't matter what it is, document these things. Where is if [00:09:00] your business doubled in size, how would you bring a new person in so that that person can now get up to speed very easily and quickly. And, uh, they have a way of measuring whether they're doing something correctly or not.

David: Um, and those, that's what to me, a playbook is right. Um, and when you have that, you can start to, uh, then you can talk to somebody like me or, or, um, or just ask AI how, Okay. what would I automate here or, and what can I improve in my workflow and things like that? That's how I would go about it as a small business. 

Mike: 1 thing that I'll bring up here because I had a really great meeting about it just yesterday is, um, probably about. Two months ago, um, we released some, uh, some, you know, you, you call them a playbook. Let's, you know, I, I've had other people like our, our buddy, uh, Tim Shakur calls them workstations. Right.

Mike: But it's basically, Hey, you land here. This is how you do your job, right? Here's your functions. Here's your different things. And it's easy, you know, how to do it. And, and AI is [00:10:00] checking you along the way. And then obviously you still have to understand that AI isn't perfect. Right. And it might, let's say hallucinate, but I was talking to, um, I just built a couple of tools for our GTM group.

Mike: And, um, and so we do a meeting every week cause we want to get a pulse, right? Like our use of the tools where, you know, uh, are there any challenges, right? How we can, can we refine these? Right. And I think one of the biggest thing is making sure that, uh, You don't just release the tool or release this workflow automation.

Mike: And then like, that's it, you know, we're not going to look at this. And, uh, so I said, you know, I said, Hey, so, you know, how are you guys doing with it? You know, are you having any good wins? And one of our guys, Mark was like, are you kidding me? He's like, Honestly, without this, this set of tools, I would be lost.

Mike: He's like, I don't even understand how I did my job before you built these tools for us. Right. He, and so I was like, Whoa, that's like killer, you know? So he said, this 

Mike: is how I operate all day. I used, I use the tools. Right. And, uh, [00:11:00] 

David: Yeah. It feels really good when you make that kind of impact. Right, 

Mike: Yeah. And, and, you know, he's in sales and, you know, that allows him to be on calls and talking to customers and doing the relational parts of his job instead of the transactional parts. Right. So, um, so yeah, no, that, That's great David. Um, and I, and I know you, you know, you told us even, uh, the, a couple of little bits of other stories too, right.

Mike: They, these automations folks are, um, You know, once you, once you figure them out and to David's point, and Wendy says it, Wendy, uh, Reeves says it too. Like you have to understand the process, you know, what you do, how you do that playbook manually before you automate it. right?

Mike: It has to be very well, you know, it has to be efficient And

Mike: you have to have a good process for it.

Mike: Otherwise you're just making something that's inefficient faster. Right. Which doesn't really move the needle. So. 

David: right, right, Yeah. It's always, you always have to, reinvent [00:12:00] how you do things. Sometimes if you can make it enough faster than it does move the needle, right? It may be a repetitive process that could be done better, but if you make it fast enough, that becomes invisible because it's not create, it won't create a bottleneck, um, until you scale many times beyond where you are.

David: Whereas today it might be creating a bottleneck. So, um, and, and you have to do that kind of assessment too, but some of the, Other things like there's one tool from one of my clients who's in healthcare. Um, and, uh, they have an AI nurse that is like talking to a real nurse on the phone and you can even interrupt her and, you know, and say, no, that's, that's not, that's not what I'm talking about.

David: She'll say, Oh, I'm sorry. Can you explain, um, you know, what's different about what you're talking about versus what I thought it was. And then you do, and she got, Oh, okay. And I understand it's like a real conversation. And the person can even say, you know, I'm just kind of sad right now that she might, she might start, um, you know, just say, I'm sorry, you feel that way.

David: Tell me what [00:13:00] you're, why you're sad and start kind of giving, yeah, it might be somebody who's older, who feels isolated. Right. But that's not the purpose of the tool. I'm just saying, these are some of the things, some of the side effects, the purpose of, of the tool is to basically automate really manual workflows that require somebody with specialized Nursing skills.

David: That is a tedious process, like transitioning somebody from the hospital to long term care. That's a good example. And to be able to make an infinite, not infinite, but like an unlimited number of calls for large numbers of patients at at the time that that patient really needs to call to get this transition support, right?

David: Explanation of what's going on. Um, Yeah, Um, uh, a phone number. They can call if they have questions, which would be the AI nurse again. Um, um, explanation of services that they can expect. What's what, you know, giving basically and very patient and answer any questions. And there's no time gap and no additional [00:14:00] cost that negligible cost in terms of how long the call takes, because there's not a limited number of two people doing this for hundreds of patients, right?

David: There's hundreds of calls happening in parallel, however many needs to happen and they happen just at the right time. So that's an example of a massive value for healthcare system. That's understaffed right.

David: now. Um, um, it doesn't replace nurses, but it takes the pressure off the fact that nurses can't get anywhere near as much of this done as they need to. right?

David: And this is not the part of their job. They really want to be spending their time doing 

Mike: Exactly. Yeah. Menial work, right? Yep.

David: Now, here's one that we're going to be doing. Oh, so go ahead, Rico. 

Rico: no, no, go ahead.

David: Here's one that we're planning on doing, uh, based on a discussion we, I had this week with my director of operations in terms of our teams.

David: What's one of the things that every development team. Has to do every single morning and that's a stand up. Not every team, but anybody that's [00:15:00] using any kind of modern methodology, uh, development methodology, right? You do a stand up where everybody in your immediate team is talking about what they got done yesterday, what they're planning on doing today and any dependencies that are outstanding.

David: Um, and that's all you do. But it still takes 2015 to 30 minutes. I mean, if you're really, really good at 15 minutes, right? But usually it takes 20 to 30 minutes to get through it. Something comes up, people start to discuss it and then it takes the scrum master whoever is running. It has to say, okay, we'll handle that afterwards.

David: I don't want to wonder whatever. So we're going to build an AI agent to that pulls in all this information from during confluence and, and, and identifies anything from email communications that may be relevant, pulls together and does an automated scrum with a stand up with the developer Right,

David: before any scrum meeting.

David: And then, uh, and then we may eliminate them all together, or we may have a quick one minute call to say, you know, is [00:16:00] there anything that didn't get addressed in your, um, in your, um, Meeting with Gerald, whatever we're going to call this scrum agent, right.

Mike: This is awesome, by the way, this is, I'm just, no, listen, I'm thinking about, so a couple of things, one, I personally wouldn't get rid of a daily meeting, especially in a, a distributed remote work environment, because what people like to do is that's how they get a human connection, right? But in the 

David: And that was my exactly right. 

Mike: In the same breath though, having Gerald give me a rundown so that I'm, I'm like, and, and, and I mean, That's just so fricking valuable to understand and aggregate the data from all the channels, including email and teams and, you know, whatever, you know, maybe it's Slack for your company. Right. So, but aggregating all that data and really having a rundown of what WTF did I do yesterday?

Mike: Because you know what happens? People are moving, moving, moving. And they, and [00:17:00] they may not even give themselves credit for all the stuff that they've done. Right. So having that just quickly delivered to them, I could see that being transformational and that's just fantastic. That's super cool that you guys are doing that. 

David: So one of the things I want my team to do is every day talk about how, what they're going to do, try to do today using AI to improve, you know, right. To improve what they're doing, whether it's make it better, make it faster. Um, um, uh, whatever, whatever that is. So that may be what happens in our standups.

David: And 

Mike: There you go. 

David: you know, is that, and any dependencies That have to get discussed that have several people involved, right? 

Mike: exactly. That that's, that's a good purpose for them. Yes. 

David: So the scrum master now is looking at the, whoever's running it, right. So looking at the result of these, of the standups and sees that there are six points that, uh, may be a problem with the people with dependencies move forward.

David: [00:18:00] Spends five minutes on those. Gets those addressed and spends 10 minutes now taking and doing an intake on, okay, what's your AI thing today? And everybody's got to come up with something even if it's the same as yesterday. I'm gonna continue to do this Okay, what and and what value have you gotten out of it so far?

David: You know, no, no value Okay, do you think it's you're going to or is it something you should come up with a new one tomorrow? You know like that and Right. And change the whole media need for those meetings so that it's almost like having affirmations in the morning, right? And so if you have your list of things you read every day as your starting day kind of Process like I I have one somebody I met somebody recently is really successful and he was doing it I thought you know, I I know this works because you just keep Sticking those, those ideas in your mind every morning, Right.

David: And, um, and you just start to make them happen unconsciously, right.

David: If you say every single [00:19:00] day, you know, weekend, week out, no matter what day of the week it is, and there's like 20 things, right? One's for family, one's for the company, one's for finance, like that sort of thing, one's for health and one's for exercise, and there's three or four things under each one of those, and there's certain kind of format you follow, so they have.

David: Punch and impact and they're generalized enough. So why not turn our standup meeting into something like that every day about AI, but not aphorisms, but talking about planting that seed of this is what I'm going to do. And knowing I have to be doing something to 

Mike: it on their 

Mike: keeps it on their 

David: push, it. Right. 

Mike: They're accountable. They're, they're accountable 

David: to take, I want to take credit for the agent, uh, scrim agent thing, but that was my director of operations guy, 

Mike: That's, that's great. No, I, I,

Rico: That's a great use,

Mike: I love that idea. And, you know, we were going to go into directly into like, um, trends for the future, but, you know, I was thinking about it and, um, one of the things we have on the agenda, David is last episode, you know, [00:20:00] I had talked about how you had showed me bolt and I showed you repl it.

Mike: And you've, you've completely migrated to Repl. it. So a question for you, I have is how do tools like Repl. it change the game for developers and business, right? Like, and how have you seen those gains with, with the, you know, some of the tools and the features that Repl. it has, like, like their agents, right?

David: right? I mean, I

David: I'm imagining how it's going to change the game. He's starting to use replit made me realize that we really need to reinvent ourselves again, completely, because what we're doing as a developer, as developers and building apps just won't, it won't be the same thing next year, you know, in a year from now, it'll be.

David: And the ones that are still trying to do it the same and those, they're not going to go away in terms of demand, but they, um, uh, but they're just going to be so pretty far behind the curve in a year if they're still, even if they're, and a lot of shops aren't even doing modern things from a methodology, methodology [00:21:00] perspective, from a automation perspective, a dev ops, CIC, a CD, you know, um, uh, automation, automated testing.

David: I mean, all the things that are. Like the buzzwords, right. That are kind of modern shops, Right. They're not even doing all that stuff. Um, so, uh, next year, all that stuff will just happen. In this time next year, potentially. So from a predictive standpoint, just how fast things like replit are coming along.

David: Um, like for example, we need a, uh, referral partner portal because we're building this network of referral partners. Um, so we have to have a way for a referral partner to, Um, easily add a referral if they have one or, or we pull it, they send me an email with the referral and, uh, the portal is watching emails and automatically creates a record for them knowing what their referral, you know, fee rate is and things like that.[00:22:00] 

David: And then that way a partner can go log into their dashboard and see, Oh, you know, I, there's eight referrals that I've given. Here's the status of each one. Two of them, actually, we've got contracts and now are accruing some, um, uh, commissions for me. And this is what's paid out, you know, over the last nine months or whatever.

David: Um, and I'm building the whole thing with Repl. it in my spare time for the last week and a half. And I've got much of the first version of this done. So what does that mean? Okay, do we do these high fidelity prototypes anymore, or do we actually build a application prototype instead? Use Repl. it to have Repl.

David: it, uh, basically have it describe the design to it and have it build out the screens and the workflows, and then have it wire all that up after we're comfortable with, we think the design is good, and build it as an application and get an MVP out. In a month or three weeks or two weeks or a week, Right. And go [00:23:00] out to the market and do some prelaunch sales with this, um, with this tool that was built by replica to prove that there's a product and now you've got something they can start using. It's, and it might even scale to a decent amount because Repl. it allows you to deploy it into a, uh, into an auto scaling server.

David: Right? That's 

Mike: Yes. It, it, it really does. I mean, you could get something that I

Mike: would say, unless you're like Twitter, it can, you know, it could scale pretty well, right? Like you'll hit the limits at some point, but to your point, you know, that partner portal probably isn't going to be getting like a ton of play, right?

Mike: Like, 

David: Well, you don't know that if 

Mike: Because I want you to get a lot of partners and a lot of partner activity. But you know what I mean? I think about the amount of 

David: Yeah. I'm just kidding. 

Mike: put in would flow through that. Even if you're doing really well, it's not a ton. Right. So 

David: This might be all we need, right? But I also, then I can put a SaaS front end on it. And so my partners, if they want to use it, right, then they are [00:24:00] paying me 20 bucks a month. And now they're using it as their own partner portal. And if you've got five people that you're referring projects to, you have one dashboard that's consolidated, right. for all of it. 

Mike: Yeah. I love 

Mike: this. I mean, I, I 

Mike: really, I love the idea. Yeah, that's 

Rico: It's a handy tool.

David: yeah, yeah, I, I, I'm still like shaking my head. We have a team meeting tomorrow where I'm basically going to show this to the team. Right. And they all laugh at me that I built it. Right. Because my development skills are a little rusty. When you start building a company, you don't get to play with, I love coding.

David: It's like my favorite thing to do. Um, uh, which is why sometimes I'll take on these hobby projects for friends of mine like that workflow automation for the guy with the network. Anyway, but. I don't get to do it very often. Right. So my skills are a little rusty for any particular technology. Right. So They don't need to be that good. anymore because AI is,

Mike: They 

David: know, [00:25:00] AI does it

Rico: Yeah, 

Mike: I will say this, you need to know how to debunk what comes out. And I know, I know you're already thinking it and you're doing it, but you know, to folks and our listeners, you need to be good enough to know what's coming out of, you know, what's coming out of it is good, bad.

Mike: Uh, what needs to be modified because you don't repel it. Is great. But the first thing I did with Ruid agents was asked it to build a Django app, which is a Python framework and, uh, with these specific things, and it built me a Flask app, which is different but similar, but different, right?

David: Yeah. right? 

Mike: you know, the, it, it worked.

Mike: But it was like, wasn't what I asked for. And if you didn't know the fundamental differences between those two frameworks, which it's, it's a massive difference, um, then, then you would never know any better. Right. You just say, Oh, I got this pretty thing and yeah, it works. Look, I clicked the button. right. 

Mike: So, um, so yeah, so with, 

David: Let me qualify what I said. Yeah. Yeah. Let me quote. Yeah. Let me qualify. Like, Like, when it [00:26:00] comes to approaches and architecture and things like that. I'm coaching my team, even my most senior guys still just that comes from experience or database design or, you know, things that. You just learn all the nuances of what can tank you, um, and what will make it really scale and be resilient and, um, um, and reduce maintenance over time because you can build on it and expand it instead of it starting to become heavier and heavier and, you know, in terms of, those kinds of architectural concepts, um, Uh, and what it means from a technical implementation perspective.

David: I understand that really well. I just don't have to remember how to write the syntax for 

Mike: Totally agree. Yeah. It's like Linux commands, right? It's like Linux commands. I don't, I know what Linux can do and I know exactly what I need to Google to get my exact Linux command. Now I use chat GPT for all Linux stuff. It's so good with that man. Like you can have it with you have a pass script or whatever.

Mike: It's just so good because [00:27:00] these are like these minute little things that we shouldn't. Be keeping in our head anyway, we should just know what can be done and what, you know, at a basic high level, what should be done. And to your point, David, thanks for clarifying, because I a hundred percent agree with you the specifics of what used to be called a code jockey, where you're just like, Oh, I type code, that's my job.

Mike: That's going away. Like, I mean, way sooner, I think that some people think, and it's really going to be about just knowing how to guide things through. And, and, and, and to your point, some of those skills of experience where it's like, Hey, what's, what could, what's good. What's likely to tank us. That's a great way to say, I mean, like, and that's something that you gain from experience.

Mike: So you're always going to want to have. These, these, you know, people with experience that are, that are guiding the people that, um, you know, you're going to want to have good code reviews. Right. That's one thing, right. And even if you go to like an AI code review, which, um, we've [00:28:00] started to do some of that, like as a first pass, right.

Mike: Which saves you time. So it's like, it's the menial work of, Hey, did this hit or not hit? These basic things, right? Oh, it didn't great. I'm not even going to look at your code review, but, but for that code to get through and actually go get pushed to production, heck Yeah,

Mike: there's going to be some scrutiny there, right.

Mike: So 

Mike: from your, from your senior architects, developers and whatnot, and, uh, and you need that. So no, that's awesome. Um, so, so thinking about that's the kind of the future, part of the future of coding, what other. Predictions of like, you know, crazy stuff. I, we had some conversations that were like, whoa. And, uh, so I wanna get your take on what other predictions you think are happening, uh, over the next couple years that are gonna be directly outcomes of, of, ai.

David: Okay. So some things that are really hard to predict, um, in terms of like maybe in five years or 10 years, do we even need programs anymore? Or will ai. [00:29:00] just assemble the workflow as it's needed real time? As you're asking it to do things and then it sees the patterns and I don't know, I'm just saying that's a possibility that I've kind of been pondering and what does that mean and how do you do something today that will have some kind of resilience and, you know, three or four years from now, it is very, very tough to, um, uh, to break or maybe be.

David: Then this is scary for all the creatives in the world right now. It's especially today with sorrow coming out Maybe we don't have movie and film and TV production anymore because AI is Generating it real time based on your real time feedback as you're watching it by you know, your your How you respond and, you know, you laugh and, and it's, and it's picking that up and creating stories.

David: Um, um, um, as you're watching it and as these are not pre produced things, they're just custom designed for you. [00:30:00] Um, that's one, 

Rico: If I could just on that, we, we, we, yeah, we did a round table while back and, uh, Mike K you remember this one, Mike, uh, he threw out, he said he can't wait, he can't wait until it gets to the point where he can sit down on the couch and say, this is what I'd like to see and give a general like storyline and the type of characters he wants to see and have AI just literally, you know, think for a moment.

Rico: And with that, Three over the release of Sora, I'm sure that'll be coming sometime in the near future, but then AI will just create the storyline, add the characters and everything, and then you're watching, you know, original content that you kind of created yourself, but you just gave it, you know, the idea of what you want to talk about or what you'd like to see.

Rico: So

David: yeah. Yeah, and then it's testing things like, did he laugh at that, not laugh at that, right? And it's monitoring you real time and it's getting to know you better and better to, so that it creates a comedy that you literally can't like your stomach's falling apart

Rico: can't breathe.

David: every single note and the timing and Right, 

David: I mean, I could see this at some point. I don't know when, um, uh, I don't know [00:31:00] if that's three years away or 30 years away. Right. I used to, but 30 years seems like everything's a closer. I used to think. What AI is doing today and four years ago, I would have said that's 15 years out, not, not four years.

David: Well, actually I would have said 15 years and it probably wouldn't have thought it was this good. So, um, here's one thing I believe is predictable, which I think you guys know, cause we talked about this, but if you're invested in, multi level parking structures or any kind of a parking structure, um, like multi level garages outside of stadiums or in an office building or underground parking lots, like under a mall or whatever, sell it today.

David: Cause in somewhere between three and seven years, I don't know when that tipping point will happen, but it'll happen very quickly. There won't be any cars parked there anymore because of automated, because of, um, automate auto driving, right, Uh, uh, things like. When Tesla comes out with their auto [00:32:00] taxi and Waymo's already out, which I've ridden in Waymo's and they're pretty frigging amazing.

David: Um, and then you've got, uh, and then the people and people stop buying cars. And the few people that they'll stop buying cars because of the, it costs a lot to own a car way more than it'll cost for you to be driven everywhere by these competitive auto driving taxis. right. Um, and there'll be so available.

David: That you'll be able to get one in a minute or two, always, because somebody in your neighborhood will probably still own a car somewhere because they're making money off this auto taxi, and there'll be a critical mass of these vehicles, um, um, available so that when you say, Hey, I'm, you know, I'm, I'm leaving now, and you finish brushing your teeth, you walk outside, it'll be waiting for you already.

David: So, uh, and it's much safer. So, and it'll be much more dangerous to drive a car because it is dangerous to drive a car today. We're just used to it. But it would be much safer. So it'll only be people that can afford it. And that just [00:33:00] really want to drive and love to drive. That'll have cars. Cause I know I, and that'll be True. 

David: or let's say you have a pickup because you like to haul stuff.

David: Right. Um, um, so you would just say, I'm, I'm. You know, get a pickup to help you haul whatever it is you're buying, that'll be the thing you get and it'll be there like almost immediately because there's an infinite number of pickups on the road and they'll all be self driving pickups. Um, there'll be some exceptions for that, I think, like for people that live in rural areas, that'll take a lot longer before this sort of thing might be available there in that kind of number.

David: Um, obviously for people that use, you know, Their vehicle for work, like construction vehicles and things like that. Now, you know, there'll be exceptions obviously. Um, uh, but it's, but for the typical driver, they're going to work or going to the store or, or going to a friend's or entertainment, those, I think it'll be a massive shift.

David: I don't know what the automakers are going to do. Um, [00:34:00] um, to, because the demand is going to shift and the need for as many car vehicles on the road is going to go dramatically down. is they'll just be so much more efficient. 

Rico: Mm hmm. 

David: So there's a 

Rico: I think. Well, uh, how do you think the adoption would be by the public? I mean, do you think that'll be like a phased approach where it'll be some people that like, that are still skeptical now? I mean, you've, you've seen AI adoption in your own business, let's say. Uh, how do you think the public at large is going to adopt that?

Rico: Or do you think people are still going to like be a little resistant to giving up their, their freedoms, their own vehicles?

David: well, I'm an early adopter, of course. So I've been in a way, Mo, um, a couple of different times in Phoenix, right? Um, uh, my wife and my mom are both saying you're crazy and I'm thinking to myself, no, I, you know, you just don't really 

Rico: tired of driving. Right,

David: I, it's, it's nice. I can sit there and play chess while I'm going, you know, Going from wherever and it'll pick you up right at the airport.

David: [00:35:00] Now, you know, in Phoenix, that was new in the last month, uh, right with all the other ride shares. It just navigates in between them. Um, and it'll drop you off there. And, uh, it now all goes all the way to my mother's place, which is way North. And it, at the moment, it's still in the city because they hadn't turned it on freeways yet, but that it's only a month away probably.

David: And then it'll get there in the same amount of time. And it's half the cost of Uber. And they don't even have any competitive pressure on them yet. So, um, uh, but once there's a critical mass to this and, uh, uh, the, I think there'll be a big wave of the, uh, public that basically starts using them because they're getting in one with a friend or, or, uh, because they're finding out that everybody is taking one to work and they're the only ones driving to work.

David: And people are thinking, are you crazy? So they'll try it, realize how really incredibly cool it is. Um, I, it'll happen fast. It'll happen really, really fast. [00:36:00] Um, uh, it'll hit a certain critical mass. Like I said, three years, seven years, somewhere in there, I think somewhere in between that range. And that's really purely guess it's not based on anything except for my experience I had with something massively disruptive like this with, um, uh, that I saw with Uber.

David: So, um, I don't know if I mentioned the story to you last time or not, but I, I used to travel to India a lot, 15 times, starting in 2010 until the first week of the pandemic. Um, uh, because I was building my teams there and people that say that they work offshore and had bad experiences is because they were throwing basically a project over the wall to some team in India that they really didn't know, right?

David: Um, if you, you can't expect to have a team that works in a particular type of culture that you're trying to build if you don't get to know them personally and spend time with them, [00:37:00] um, uh, and establish some of the basic fundamental tenants and then you build an exceptional team no matter where they are in the world.

David: Um, so that anyway, so I spent, um, uh, uh, for the first six years, I went there six or seven years. Yeah. till 2015. So I started actually in 2008, traveling there. Um, so I had to make that 17 trips. But, uh, 2010, 2015, every time I would go, land in Mumbai, and I'd take, uh, Uh, drive it have somebody pick me up because there's no way I was going to drive there, um, uh, because it's just nuts, right.

David: It's opposite the other side of the road and the, and there are,

Rico: Volume.

David: there were literally no rules and there were like in the city of Pune that had five and a half, 6 million people. There were no rules. There were like five traffic lights in the whole city. So people just had to figure out how to get through intersections without dying.

David: And right. 

Mike: Mm-hmm

David: And there were stop signs. I mean, there just was no [00:38:00] traffic control. Um, that's changed a lot since then, but this was back in 2011, 12, 13. And there was this infinite sea of tuk tuks or autos. There are these three wheel motorized rickshaws, no matter where you went. I mean, that's not, I would be picked up in a car and that there was probably 10 of those.

David: Motorized rickshaws to every car. Um, and then also there were 10 motorcycles as well. So it was like motorcycles and these three wheeled rickshaws. Then I didn't go for 15 months between 2015, 16. And I came back and I got in the car to go to Pune and I thought something is really different. I couldn't really put my finger on it.

David: Then after we were driving for a little bit, I realized I'm surrounded by cars, not tuk tuks. What happened to all the tuk tuks? And so when we got to the office. And I thought it had big government regulation, nothing could possibly eliminate a millions of these vehicles and their drivers all, you know, literally overnight.

David: I got to the office. I asked her locker. She was our director [00:39:00] of that office at the time. And I said, cause we had Chalaka's one team and Gayatri is a different team because I mentioned Gayatri earlier. Anyway. So I asked her locker, what happened to all the autos? She says, well, you know, Uber came to India about six months ago and they won't approve them. And Wow.

David: whammo, an entire class of vehicles and all the people that own those cars were literally wiped out overnight. And the people that started, and the people that started Uber, which was only six years before. weren't sitting there in their garage going, just imagine in only five or six years, we can wipe out a whole class of these vehicles in Southeast Asia, right?

David: And I mean, obviously they're not thinking like that, um, which I always say, things that are truly disruptive like this are never Intended to disrupt in the ways that end up disrupting. Right. So does, uh, did, uh, Elon Musk say we're going to get rid of all these parking [00:40:00] structures? No, of course not. But when we hit that critical mass, it's going to happen fast.

Mike: For 

David: Um, just like it did, uh, by the way, all those vehicles came back because a competitive service came out, um, uh, like a year later, I think it was called a wall or do wall or something like that, um, that was an Indian based company and they approved them. And then, of course, to compete, Uber had to approve them as well.

David: And then overnight, they're all back.

Rico: They're back. 

David: They're back. Yeah. 

Rico: That's crazy. So on the, on the business aspect, staying in the same theme, as far as adoption, you know, you had some experience now with it. What, what advice would you give to businesses to get to AI adoption, maybe amongst the employees or, or, you know, B2B, uh, relationships?

David: Um, and that's probably a really good, but really hard question to answer because people, It's it's a mindset thing. So, so whatever you can do, right, whatever you can do to [00:41:00] constantly put it in front of them and then to, Um, guide them into using it For something on a daily basis, or at least a couple times a week with everybody in your, uh, team so that it's, they start to just think about it when they're doing something.

David: Um, that's what you need to do. Uh, explore ways that it can help them in their personal life as well as in business, um, that you feel is safe. That's not going to expose your business in any negative way to things that you might like intellectual property and being, um, you know, where A. I. Is using that to train.

David: And there's lots of tools you can use and ways of protecting privacy that are that are. Pretty much like cloud is everybody uses the cloud. Now, nobody worries about it in the way that they did 78 years ago, and it's like that with AI. You don't have to worry about it. As long as you take some basic precautions, have your privacy settings set properly in the tool that you're using.

David: Make sure. you understand what the privacy is. Uh, [00:42:00] capabilities of that tool are that they're not using your data to train the model that it's, if you have a little private, uh, uh, garden wall around your data, uh, and then you use it, um, uh, and, and explore what tools are out there, uh, that you can use an intro that might be a benefit to your people on your team and that you can introduce to them a really, really good one.

David: That's probably very. That's ubiquitous in terms of how it can be applied as, as a notebook LM, which I love because it becomes your own little private AI garden 

Mike: What is it called? What 

David: notebook LM from Google, from Google. 

Mike: From 

Mike: Google. Yep. 

David: yeah, right. And it's just a very, um, uh, low hanging fruit. It's kind of product where you can upload any document, put links in there for content that you want it to learn about.

David: Uh, and then you can ask it anything about that content. And it's very specific in terms of [00:43:00] what it's being, what it's trained on now. You know, it's a large language model informed by your specific content. Um, you can even create a discussion. About that content by just clicking a button. And now you've got two people talking and they sound like real people talking about the content you put up there, summarizing it, creating really intuitive insights.

David: about that content surfacing things you might not have realized about your content. In fact, we did it when it first came out, like in the first few days, pointed it to my website, techies dot com. And of course, we're blown away having because these two people are like having a podcast episode talking about what we do and very edgy kind of a cool conversation.

David: And they said, well, these guys have been doing it for But, you know, uh, this kind of concept of launch first, and they've had this for several years. That's like dog years in tech time. I was like, you know, these are kind of nuanced, cool [00:44:00] things that it's doing. It also was talking about some of the messaging down halfway down on our website about some of our capabilities that was not messaged properly.

David: And we didn't realize until We, heard them talk about how they perceived it. And we go back and read it and go, you know, it's exactly right. So, like, you just use it as a, like a, uh, an evaluation tool, right? Like for that, but, um, or to say, summarize all this for me and put it into a certain form so that I can present this to a customer or create a proposal for me, here's all of the parameters or, I mean, you can do anything with it, right.

David: And it just focuses on your content. So that's a good way to start to introduce it.

Rico: We, we did an experiment a while back and Mike, maybe you could remember the tool that was, but where it created a, um, a script and it sounded like a man and a woman talking on a podcast and they 

Mike: it. That's, that's this. 

Mike: That's it. Nope. 

Rico: that's what it is. 

Mike: the thing. Yeah, exactly. 

Rico: And, uh, we, we had, uh, added the [00:45:00] audio to it and they were doing the ums and ahs as they talked 

Mike: Yeah, they stop and pause and 

Mike: yeah, that's what 

Mike: got me is like, it's 

David: you didn't know, yeah, you would not know. 

Mike: Yeah. And if you 

David: Uh, by the way, 

Mike: the other a hundred people that have released podcast episodes about their notebook LM thing, because that's the one, that's the one thing I will say is I wish I could do different voices, like, like change the speakers in there.

Mike: That would be gold. and I think there's another thing that, that actually allows you to do that. So, uh, because it's so

David: there is some guy, you can guide it. Now you can guide the conversation. Yeah. They just came out with that like last week, um, where you can guide the car. I don't know about the voices yet. I think they may have that now. Uh, there was a really funny one that somebody did and published, um, where basically they, um, explained to notebook LM that you're not a real person.

David: Yeah. That you're an AI. Anyway. And so then they had this two people talking and says, you know, I don't know what [00:46:00] to do with this information that I'm not real. Well, what? And she said, what about my family? She, she says, well, yeah, I mean, you still have a family, right? I says, well, I don't know. I mean, I called my mom and there were, that number didn't exist and neither did she.

David: No, I think I'm really an ai. I don't, it was so funny. 

Rico: That's something else. 

David: funny. 

Rico: We're going to have to find that.

Mike: Yeah, we will have to find that for sure, David. And, you know, we were talking about podcasts. So like, um, and generating them. So speaking of podcasts, David, you've actually got a new podcast coming out. You want to kind of tell us like what the podcast is about, what motivated you to start it? 

David: Yeah. Sure. Yeah. Yeah. Well, I mean, I'm doing a lot of interviews now. Um, and, uh, because the world is changing so fast and I think it's important that I have that people hear my voice, at least from my opinion, what I think about it as a way of branding. Techies talking about what it means to be an exceptional software company, talking about AI and [00:47:00] how it's impacting, uh, the world and the development scene.

David: Um, um, and then I thought, you know what? I really probably ought to be in, uh, um, doing my own podcast on the same thing. So, um, uh, that my first interview is supposed to be tomorrow. Postponed it for a few days, but we're starting it, you know, it's starting literally right away and then I'll publish it as soon as we've done three interviews, so it'll be within a week, week and a half.

David: It'll be published. Um, and, uh, it's called scaling smarter, uh, with, and I'll be interviewing CEOs and CTOs kind of like you guys. So companies that are either are successful or have failed or are in startup mode, you know, right? All of those, uh, with the idea of learning what they problems they've run into, how they overcame them.

David: Or what happened when they didn't overcome them and how big an impact it had on them, how AI is impacting what they're doing and, or how they're leveraging it to [00:48:00] solve these problems. So it's going to be that kind of a podcast, you know, it'll blend between startups and startups and scale ups. 

Mike: I like the, I like that you're actually open, you know, like you're, you're going to focus on the entire sphere of, of how things can go. Right. Because, um, you know, knowing, understanding the failures, uh, is, is just as beneficial, you know, like that as understanding the successes, right. And a lot of times the failures are what ends up ultimately leading to the success.

Mike: Because you've got, you've, you've learned what things could bite you. Right. So, um, yeah, I'm super, super excited to, to catch the podcast. Is that going to be a weekly podcast, David, or is it pretty much just going to, 

David: I'd probably be two or three, two or three episodes a week is what I'm shooting 

Mike: oh, wow. 

David: 10 a month roughly. And, uh, there'll be shorter in, uh, at least initially, um, um, uh, there'll be much shorter, uh, kind of [00:49:00] episodes to really kind of focus on a microcosm of somebody's, uh, business and experience. Um, uh, and that may change, right?

David: So, uh, they may change the longer format ones more like, yours. Um, I'm, I'm using the guidance of somebody Transcribed by https: otter. ai Um, uh, that suggested try the short, the short format first to make, you know, to create more punch in the podcast initially. and we'll see if that works or not. I like talking, all Right. And I like listening to people that want to talk. So I have a feeling it'll probably expand into longer things. And the one thing I'll say though, regarding AI is just channel your inner five year old, you know, when you're thinking about it. 

Rico: That's how we started. I think

David: Yeah. Yeah. Yeah. I think I will 

Mike: good at channeling and his inner five year old. I don't think he's grown past that, honestly. 

Rico: more an external five year 

Mike: why he's so good at this. That's why he's so good at this.

David: like, uh, a friend of mine told me [00:50:00] about his granddaughter who was three years old walking, uh, and she had never seen a book cause she, her family was all digital. We're two and a half year old and they don't read to her, but they're have everything digital and iPads and all that, right. And keep her interested and engaged with.

David: learning stuff on that. She walks up to his coffee table, which is full of these magazines, and she walks up to the magazine and she starts to go like this. 

David: On the magazine and her eyebrows, I mean, she might've been two and a half and her eyebrows kind of knit together. She looked up at him and then he picked it up and flipped the pages and her eyes got huge.

David: Cause she had no idea, 

Rico: yeah.

David: She thought it was everything's digital and you slide your finger around on it to make it happen. Um, so that's What I mean by channel you're in a five year old, right? You don't know what you don't know. Um, so just click on everything and try everything and don't be afraid. 

Rico: Definitely. Yeah. So, uh, when, once you come out with your first [00:51:00] episode and you have to let us know, and we'll put it in our AI bites newsletter, we'll start, you know, kind of pushing that for you to see if we can get some, uh, traction for you early on. But, uh, is there anything else you want to add David, as we, as we wrap up here?

David: Well, yeah, I want you guys to commit to me on the air that you're gonna be that you'll let me interview you on my New podcast here in the next 

Mike: What I didn't want to impose, but I was actually going, I

Rico: I was hoping.

Mike: now. And so I'm really glad, guess what? We're all aligned. Well, we'd love to be on the show, David. And I was actually thinking, um, I have a couple of founder friends that, um, or people that have been at senior, uh, executive levels in companies that have helped grow them and they, they will have some great battle stories for you.

Mike: So, 

David: Oh, I love that. 

Mike: be. Be pushing some folks your way. Uh, because I think that's such a compelling podcast. I'm, I'm super excited to listen to it and absolutely. We'd love to be guests on the show. So 

David: Thank you. I really appreciate that I figured you'd you want to be but I just thought [00:52:00] I'd throw that out like that And you know and just Be fearless that's all I can say is be fearless and Uh, and, but that doesn't mean be, you know, blindly forward your head either, Right.

David: The one thing there was a study done, uh, there's a, a podcast on happiness called the happiness lab.

David: Uh, that's pretty well known. It's a Stanford professor that started this thing anyway, that she has an amazing story. Um, she started a course at Stanford on happiness, um, and she didn't know that it was going to, it was, she's a psychology PhD and, uh, um, and she ended up, the class had, um, uh, got full almost instantly.

David: And then she started to make it online and she ended up like 150, 200, 000 people signing up for it. And so she started this podcast. So, um, and she interviews. People about what makes people happy, right? And one of the episodes was on CEOs and this idea of power of positive thinking. And it's a myth, [00:53:00] you know, that you just keep forging ahead.

David: You keep saying something positive because all these really successful CEOs. When you ask them why they were successful, they say, Well, I was just the right place at the right time. And, you know, we're lucky and we had good vision, but you scratch the surface just a little bit. And it turns out these are very anxious people who are afraid of everything's going to come and tank their business.

David: And they just imagine all these ways of failing, and then they work out mitigation strategies. If this happens, if that happens, it's so they're like brilliant mitigation planners and by doing that, no matter what happens, they had a mitigation strategy for it, right? So to them, it's like, well, we were lucky it all worked out.

Rico: Well, once it's going good,

Mike: that's, that's great. No, that's great. And I'm thinking about the people that I know that I'm really close to that are founders. And they are exactly like that, right? Like, like, you know, something that five years, let's say five, six, seven years ago, when I wasn't in a, in an executive level at a company and I thought, Oh gosh, this [00:54:00] one thing happened and what are we going to do?

Mike: And then I talked to the CEO and he was, he was like really on phased by, he's like, yeah, And we're already thinking about, and, and, and, and, you know, five years later, he was spot on and you know, everything is fine. You're going to have bumps in the road. Uh, but there, there's that healthy fear, you know, to your point, David, and they teach you that in the military too, right.

Mike: In different situations, it's like a healthy fear so that, you know, you have enough to understand that there could be a serious problem and that you figure out ways around that, right. Like I was, 

Mike: um, you know. I forgot, I forgot which book it was. I was reading. They were talking about the most successful people, um, you know, in, in a job are the people who are looking forward and trying to like, like figure out like what could happen.

Mike: Like let's say a truck driver, right? Like a big semi-truck driver. He's looking forward and like play it a game. Like, oh, if that car moved right over here, I would do this. Right? [00:55:00] And, you know, and, and, and I've taken that to heart and so I do that in my life. It's like what could happen? How would I adjust?

Mike: Right? And so that's exactly how entrepreneurs function. Like, you know, naturally, I think so. 

David: right. Yeah, In fact, that's funny that you mentioned the truck driver. Cause I remember, um, this, everybody talked about being a defensive driver and I just naturally kind of did that from the time I was young, like when it was raining, um, uh, heavy rain, I was, and I was 16 or 17. It was fun, but I also, for me, it was also just learning how to control my car in the rain.

David: I go to big giant parking lots that were completely empty at night and just, Do donuts and spin my car out and learn how to, and I can't tell you how many times that has saved me from being in an accident or, or when I'm getting on the, I'm getting on the freeway ramp and I see there's somebody in the French road and they're literally parallel with me.

David: I think I better slow down. What [00:56:00] happens? And then I've had that. I was with my wife one day and I slowed down and the guy just cut right. over. Right. They didn't have their blinker on. They didn't look for me. If I was there, it would have been, she said, how did you know they were going to do that? I said, I had no idea, but I knew if he tried that he had no place to go and we'd be in an accident.

David: So I just slowed down just to take the risk out and right. So it's like that running a business. If you run it, well, 

Mike: If you run it, well, yep. All right, David. Well, thanks so much for joining us. Great to have you on the show for this second segment. Uh, Rico, this was.

Mike: fantastic. Um, you know, uh, we're definitely gonna have to get back together and, uh, you know, like you said, uh, we'll come on your show and, uh, we should do another.

Mike: There's, there's so much to talk about, right? There's always so much talk about, and in three months, our strategy of development is going to be probably even different than it is today. So, uh, folks. 

Mike: Yeah, 

Mike: it's dramatically different. Exactly. So folks, thanks for watching. Don't forget to like and subscribe if you're liking the content and [00:57:00] we'll See you back in the lab soon.

Rico: See everybody. 

David: you guys. Great conversation. 

Rico: Thanks, David. 

Natasha: Thanks for joining us. Don't forget to like, subscribe, and let us know your thoughts in the comments. Stay connected with us on Twitter, Instagram, and LinkedIn for all the latest updates. And check out antics. tv or our YouTube channel at Artificial Antics. We'll see you back in the lab soon. We want to give a huge shout out to Nick and the team at Nomad Studios for mastering the Artificial Antics podcasts.

Natasha: Want to level up your audio visual game? www. nomadstudios. pro