961: Keeping Up With The Fast and Furious Web

Scott and CJ go live from JS Nation NYC to talk about how developers can actually stay current without drowning in the constant churn of new tools and trends. They break down how to see through the fluff, focus on why tech exists before adopting it, and build a healthier, curiosity-driven approach to learning in 2025 and beyond. Show Notes 00:00 Welcome to Syntax! 00:39 Scott delivering a non-technical talk at JS Nation. 03:24 Lamenting the frequency of change as developers. 03:46 Understanding why things exist before deciding to learn them. 05:11 Learning styles are a myth? 07:41 First dates and psychology exams. 10:39 Discovering is step one, playing is step two. 13:32 Learn with a project that you actually want. 18:16 Brought to you by Sentry.io. 18:34 Cutting through the noise of new tech. 21:40 Using AI as a learning tool 25:12 Sick Picks & Shameless Plugs. Sick Picks Scott: dbrand Ghost Case 2.0 CJ: analog watches Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Speaker 00

  Welcome to Syntax. In this episode, I'm going to be talking with Scott all about keeping up with the fast and furious web because things are constantly changing. It's hard. It's hard out there.

• 0:12Scott Tolinski?

  It's hard out there. Yeah, no kidding.

• 0:13Speaker 00

  So we're going to talk about tips for keeping up, like what should you be paying attention to, what should you not be paying attention to, those kinds of things. And before we get into it, shout out to JS Nation because as you can see, we're in wonderful New York City. So, big thanks to them for giving us the space to talk about this.

• 0:29Scott Tolinski?

  New Jersey City.

• 0:33Speaker 00

  Any keen viewer would know that if you can see the skyline, we're not in New York.

• 0:36Scott Tolinski?

  Yeah, yeah. Cool, let's get into it. It's so funny giving a non-technical talk at a conference. I'm typically giving more technical talks. And so, I think it was good. I was going to be doing the last talk of the day, and I feel like everybody, after seeing talks all day, might appreciate maybe a less throwing 1,000 APIs or library announcements at you or something. So, yeah, when I was developing this, this was actually like a talk I had given maybe like 10 years ago, maybe not that long ago, maybe like eight years ago for the first time. And so much has changed on the web, but so much has changed in my

• 1:19Scott Tolinski?

  career and my approach. And I was thinking like, would it be cool to rethink, whoa, my phone just almost bit it, to rethink and reapproach some of those like ideas. So, I took like a look at this, this idea of like, man, throughout my entire career, it's been having to learn things as fast as humanly possible and as deep as I can.

• 1:45Speaker 00

  Right.

• 1:45Scott Tolinski?

  So that way I can really be able to express that in a way that like people will understand.

• 1:53Scott Tolinski?

  And so that that was really the the approach to it was like taking a look at my systems for learning, but not just my systems, because when I the the previous version of the talk was very much like, oh, here are the systems that I employ to learn things fast. And that was well received. But when I started diving into it, I realized that it's it's not just since I started making content that I've had to learn things fast. It's since I've started working on the web.

• 2:23Speaker 00

  Yeah.

• 2:24Scott Tolinski?

  Since I started with table layouts and angel firebase sites. So there's like a point in the talk when I'm just like listing all of the things that have changed. And honestly, it was exhausting to type out and even like think about every little thing that's changed over the course of even like five years, six years, seven years, and so on and so forth. And it was really like, okay, well, what hasn't changed too. So that's really the genesis of this this talk. And yeah, I don't know, I think I've developed a lot of systems and.

• 2:55Speaker 00

  Yeah, I mean, it makes sense. So like, when I was an instructor of full stack, we always started off with learning how to learn.

• 3:02Scott Tolinski?

  Yeah.

• 3:03Speaker 00

  In this career, you just have you're constantly learning like things are like you can't just learn how does JavaScript work and then just use that until you retire.

• 3:12Scott Tolinski?

  Totally.

• 3:12Speaker 00

  You're constantly evolving. You're constantly having to learn the latest APIs or learn the latest frameworks or the latest styles and ways of doing things. So maybe like, what's your first tip?

• 3:24Scott Tolinski?

  Yeah.

• 3:25Speaker 00

  Let's get into it.

• 3:25Scott Tolinski?

  Yeah. Well, I think even before I say a tip, I think people often lament the frequency at which things change. They lament the next library. Now I got to learn this the new frame. There's another new framework. Like, I've seen all the comments. I've been on YouTube since 2012. So like, I know what people think and say about all this stuff. And I think that one of the key points is, one, you don't have to learn everything that's new, but you should understand why things exist and know that.

• 4:00Scott Tolinski?

  If it will benefit your users or not, because at the end of the day, the people using your applications are really what matters. So when you're approaching what to learn, take a surface level view of is this thing going to improve my users' lives in a meaningful way before taking that moment to really go deep on something. Because again, at the end of the day, the user's experience is really what matters there. So like, when I see comments about like, oh, another new JS framework, it's like, well, you don't have to use it. But also, like, what if this new idea unlocks a massive amount of new things

• 4:42Scott Tolinski?

  for us? And I never want to like dump on anybody's experience of like, having that attempt to build something that will change things massively for users. So that's tip number one. Understand why things exist before you want to dive into if I need to learn this. Yeah. When you do want to dive in and learn something, I think one thing that I think often gets overlooked is this idea of learning, learning styles, learning styles, I don't know if you know this, is a controversial topic.

• 5:22Speaker 00

  It's a myth. It doesn't exist.

• 5:23Scott Tolinski?

  It doesn't exist. I was actually, this is, this is a story that I haven't told necessarily before, because I don't know if I'm bound by any sort of legal obligation. There was a company that was attempting to acquire LevelUp Tutorials. And I was in essentially like an interview with this company about whether or not they wanted to acquire us. And the guy, I was like, oh, I'm about to go give this talk. And I'm, it's a, it's a talking about how like, I learn things differently than other people. And he's like, or I, I says about like, learning things fast or something. And this was back when I first gave this talk. And he was like, oh, that's really interesting. I also doing like a talk about like, learning things. I was like, oh, that's, that's cool. Because

• 6:07Scott Tolinski?

  this guy wasn't a tech person. He was like a, a business guy. And I was like, okay, so like, Uh, he was, he's like, so what's your talk about? He's like, well, it's about how learning styles don't exist. And I was like, oh, shoot.

• 6:19Speaker 00

  Yeah.

• 6:20Scott Tolinski?

  I'm like, well, I think there's a hang up around that word or something.

• 6:23Speaker 00

  Right. Yeah. And if I can talk a bit about it, cause so like, I have a bit of an education background, like working as a full stacked instructor. Like we had, yeah, instructional organizers, people helping us come up with curriculum and how to teach it. And I think the idea of learning styles itself, that every person has a specific way that they like to learn. That's a myth because we all learn in different ways. I think the, the right way to talk about it would be like, sure, I identify more with visual learning versus like actual like hands on. And these are the different types of learning styles. Like are you a hands on learner? Are you a visual learner? Do you need to hear it first? But in, in my mind, everyone can learn from every one of those things and should be learning from every one of those things.

• 7:07Speaker 00

  I think that's one of the main issues with learning styles is you don't want to just focus in on one of those areas. Because you actually, even if you do gravitate towards visual learning, hands on is still great for everyone, regardless of if you like it or if you think it's, it's effective. I think basically changing modalities really helps solidify concepts because just taking it in one way isn't going to be the way that you learn that thing. You have, you have to get it hands on. You have to hear about it. You have to talk about it. So I think that's the main myth is like, we're not just one, everyone is kind of all, you might have some preferences, but everyone can learn from all learning styles.

• 7:41Scott Tolinski?

  Yeah. And, and there are, I'll have some pushback on some of that, but I, I do think that you are right on many of those aspects. I didn't realize before getting into this that that was such a loaded word in terms of like the way people perceive that. But let me tell you like, uh, so you've met my wife, uh, Dr. Tolinski. She, uh, when we first started dating, uh, she was in grad school to become a psychologist. And she had to perform X amount of like tests. And so she Did literally every psychological test like known to man to me in our first like year of dating. So she knew what she was getting into. Wow. According to if you're if you're watching this. Did you know it was happening or was it like a slide?

• 8:26Scott Tolinski?

  Oh, no. Yes, these are very involved tests. Okay, okay. They're very involved tests. She gave them to my friends. She gave she was diagnosing people not like literally, but like. Sure, practicing, I guess, yes. Yeah, yeah. And one of the things that we discovered through my psychological exams with my wife is that I have no IQ. My IQ is invalidated by my results of the test because I did really well in some areas and very poorly in others. Yeah. And some of that is defined by like my learning disability, whether that's dyslexia or whatever. But my brain does not process written word the same way it processes audio. Right.

• 9:10Scott Tolinski?

  And I always got on YouTube a lot of comments when I first started that video is really bad for learning. I can't learn on video. People should read blogs. They should read documentation. They should read the code. They shouldn't watch on like I would publish videos and people would show up in my videos just to be like, why are you teaching programming on YouTube? And like in 2025, we can know how stupid of a comment that is. But like, for me, I never understood that because it's like, I need to hear somebody talk it through with me. Yeah. And honestly, if it was somebody reading the documentation in a nice way, like I I can zoom that better. Okay, yeah. And I do actually, when I read blog posts, I select and do text to speech because

• 9:53Scott Tolinski?

  otherwise I am not like physically able to really comprehend it as well. I see. So I do think our brains do function differently. Now, I do agree that like having hands on, having the different types of ways that you can learn things are all helpful to have that wide breadth for everyone. Right. But in the same regard, like if you plop down a book in front of me and tell me to read this book, or if you give me an audiobook, I'm gonna walk away. Away with two very different understandings of that material.

• 10:27Speaker 00

  Sure.

• 10:27Scott Tolinski?

  Yeah. Uh, and, and so like, yeah, learning styles as a, as a word is like loaded in that like it consumes a lot of different intentions other than like, oh, uh, people have learning disabilities or yeah.

• 10:40Speaker 00

  Yeah.

• 10:40Scott Tolinski?

  Yeah.

• 10:40Speaker 00

  And I think, uh, my main takeaway is like, everyone should try and learn from multiple things, even if you have preferences, because you will take other things away from it. And like the idea of like watching YouTube videos, like that's just step one. After you watch the YouTube video, you have to actually go out and try the thing that you just learned. Like you, you didn't, you didn't actually learn it just by watching the video, which is hard to say because we make a lot of videos.

• 11:03Scott Tolinski?

  We make a lot of videos, but getting your hands dirty, number two.

• 11:05Speaker 00

  Yeah.

• 11:06Scott Tolinski?

  Uh, very much an important part of the process. I try to get my hands dirty as fast as possible, even before I fully like understand what the heck it is. So we just interviewed Evo Plaza about type GPU.

• 11:18Speaker 00

  Right.

• 11:18Scott Tolinski?

  And the number one thing I loved about type GPU is that they have a massive amount of interactive docs. I can get in there, I can change some values, I can see how it affects visually this thing that's being outputted. And, and that to me is so much richer of a learning experience than just like, all right, now I got an NPM, let's get started.

• 11:37Speaker 00

  Exactly.

• 11:38Scott Tolinski?

  And then maybe the thing doesn't work and you're like, all right, I'm done.

• 11:41Speaker 00

  Yeah. The interactive example is like in the world of education, it's like this idea of play. Like it helps a lot with, with kids.

• 11:47Scott Tolinski?

  Yes.

• 11:47Speaker 00

  Because like when they're playing, they're actually learning. But when we can go in and change a value and see it immediately reflected in the demos, that's huge for us. Cause like that, that connects the dots like, okay, now when I'm writing my own code with this library, that, that's what that value is for versus just telling somebody what that value was for.

• 12:03Scott Tolinski?

  Yeah, we, we just, Wes and I recorded an episode about like, uh, like strudel and some of these other things. Uh, it's for like making music in the browser with chain methods and it's awesome. And Wes knows nothing about audio and he was in there and just like messing with values and being like, oh, I made a hi hat. Like, like he has no idea what he's doing there and he was able to get something like real out there very quickly by, by playing around with it. That is like my number one hack for if you have the focus time to, to get your hands dirty and, and play that, like makes such a huge impact on things. That, that's always been a big thing for me is especially. Uh, when I'm learning something to teach someone else, I will start working on this

• 12:47Scott Tolinski?

  and start getting into the code without reading docs, without uh like just glancing at things. And then when I hit little hiccups, those are the hiccups that people who don't read the documentation deeply beforehand are gonna hit.

• 13:03Speaker 00

  Right.

• 13:03Scott Tolinski?

  Uh, and people miss stuff all the time, especially if they're, they're, they're looking at the docs. They're gonna miss little things. They're gonna hit a bug. And if you can get out in front of that and learn where all of the edges are ahead of time, you'll know, um, obviously you hit edges, you find the answer. You hit edges, you find the answer. Um, and that can like get you, that's obviously not the most optimized way or anything like that, but it's a good way to understand, um, how to get yourself out of, out of trouble kind of constantly. Uh, another tip I have for people who are looking to learn things and you're sitting down, you're like, I'm gonna build another to do app. Uh, we hear all the time on here about like people being stuck in tutorial

• 13:44Scott Tolinski?

  hell. Pick a project that is something you actually want in your life and push through that. Uh, one of my, my favorite things to say is like, if you're building in, let's say I wanna learn zero, uh, zero sync, um, like local data syncing software. And you're like, I'm gonna build a to do list because that makes sense. And then you hit an edge and maybe you can't figure it out. A lot of percentage of people at that point, depending on how hard of an edge that is of like, oh shoot, I'm stuck, aren't gonna have the

• 14:24Scott Tolinski?

  desire to push through that. And like that pushing through an edge there is like where so much good learning happens every single time. And so because of that, like, one of the things I always suggest is really pushing that, that project to be something that you're You want, I say like, let passion drive the learning. Where like, if I'm building an app for my mom and it's not working, and I've already like dedicated that energy to be like, my mom needs this app. Like, I am going to push through that and I'm gonna get so much further done, especially if you like really commit yourself to that idea.

• 15:03Speaker 00

  Definitely. I completely agree. I mean, that's where a lot of my learning has happened as well as like, I want something to exist or I want to solve a problem. So I have to learn a new library or like learn a new thing to try and make it work. But all the edges that I hit along the way, like you're talking about the edges, like that's where the learning happens.

• 15:22Scott Tolinski?

  It's always where the learning happens.

• 15:23Speaker 00

  It's like when you run into an error or a mistake, like you are gonna internalize more why something went wrong and like how you fixed it versus things just working great all the time. Yeah, I completely agree. Like in doing things that you're interested in, like you're saying, you can move move past certain blockers a lot just because you're so, you're addicted to that problem.

• 15:44Scott Tolinski?

  Yeah, you're right. That's just a problem you're trying to solve. Learning technology is not a problem that you want to solve ever. It's like, oh, I I kinda wanna learn how to do this thing. But it's also like like woodworking or something like that. I wanna build a workbench for my basement. If that's something I really wanna have, like I'm gonna learn the tools and techniques I need. But if I'm just like, oh, I think I might learn woodworking. Let me just carve up some wood and hammer it together. Like, what's the point there?

• 16:12Speaker 00

  Right.

• 16:13Scott Tolinski?

  So that definitely pushes through. Uh, that's something I can always suggest to people too is like, we live in such a time where like all these libraries are hyper focused on library specific information. But the the core fundamentals of stuff is cannot be overstated. How important it is to learn browser APIs, to learn CSS deeply, to learn JavaScript as it is JavaScript and not some library implementation of it, to learn these things deeply. But not only that, like big concepts. When you're learning, right now, a lot of people are learning, there's a thousand AI buzzwords and stuff like that. And some people are gonna spend their time learning

• 16:55Scott Tolinski?

  this specific platform, specific way of doing things. Your time would be way better served learning what all of the big concepts are. I always say it's like learning the stuff that you can take with you because. Whether or not you agree with this or not, React is not always gonna be the thing. And, and, and some people disagree with that, but it might not always be the thing. Just like Angular at one point was the thing, just like Backbone was the one. And React is obviously different than Backbone and Angular, but in, in terms of where it exists in the industry, in terms of the size and magnitude there.

• 17:33Speaker 00

  Right.

• 17:33Scott Tolinski?

  But like, learning the things that you can take with you from, from thing to thing, and debugging those core issues, those core concepts, uh, will always serve you well no matter what. Um, and on top of that, like I said, just debugging in general.

• 17:50Speaker 00

  Yeah.

• 17:50Scott Tolinski?

  Um, and you mentioned it before, like pushing through those edges where, is where you, you pick up so much stuff, but it's also where you learn the skills to debug. Um, half the time when we're trying to solve a bug, it's just trying to figure out what the heck the bug even is. Um, just trying to, and so if you can reduce your time to finding what the bug is, your, your chances are of finding, uh, how to fix it is endlessly faster.

• 18:15Speaker 00

  Definitely.

• 18:16Scott Tolinski?

  Use Sentry, by the way.

• 18:17Speaker 00

  [laughing]

• 18:18Scott Tolinski?

  Sentry.io forward slash syntax, sign up for, uh, use the coupon code TastyTreat and you'll get two months for free.

• 18:25Speaker 00

  Yeah, Randy, if you could, a plane flying by with a Sentry.

• 18:27Scott Tolinski?

  Yeah, yeah, yeah. Just, uh, tell Randy to do some, uh, motion graphics here of a animated in a plane, yeah.

• 18:34Speaker 00

  Uh, I wanna, I wanna touch on, um, like, basically like seeing through the noise or like trying to identify which of these things you're trying to learn do have staying power or like, like what you're, you're saying, or like cut, cut through the noise. I think that, that's one of the hardest parts is

• 18:50Scott Tolinski?

  Yeah.

• 18:51Speaker 00

  determining what should I actually learn and hold on to and not buy into the hype, but at least have something that I can carry with me past the hype.

• 18:59Scott Tolinski?

  Yeah. Speaking about buying into the hype, uh, I have a slide that says, resist dogma.

• 19:04Speaker 00

  Yeah.

• 19:05Scott Tolinski?

  Influencers are lying to you for clicks.

• 19:07Speaker 00

  Yes.

• 19:07Scott Tolinski?

  Let me tell you, there are so many times that I get an email that from some company wanting to push their thing and, and offer some money for me to push it.

• 19:18Speaker 00

  Yeah.

• 19:19Scott Tolinski?

  And we don't accept sponsorship on Sentry.

• 19:23Scott Tolinski?

  Perfect timing on syntax, but we are owned by Century, right? And so because of that, I get to say no to all those things, which is great.

• 19:31Speaker 00

  Right.

• 19:31Scott Tolinski?

  But it's also very interesting to see other folks talk about the same thing you were just pitched.

• 19:40Speaker 00

  Right.

• 19:41Scott Tolinski?

  Uh, without disclosing it's an advertisement.

• 19:43Speaker 00

  Yes.

• 19:43Scott Tolinski?

  And I can see it, like you are not, you are not being honest with this. And it is, it is kind of shocking sometimes. And then also see those people's opinions then being echoed by people on Reddit or people on Twitter, like verbatim.

• 20:02Speaker 00

  Right.

• 20:03Scott Tolinski?

  Uh, and then it's like, oh, man, that marketing campaign really worked. Like they really hit on that.

• 20:08Speaker 00

  Yeah. Marketing in the world of Dev these days like is absolutely crazy. Like, and it's kind of like evolved over like the past five years or so. But that's another thing that we kind of have to learn and realize what's happening is like, when are you being advertised to and when is something being hyped up? Versus when is this like an actual staying technology that's like foundational and is going to be used for years to come?

• 20:29Scott Tolinski?

  Yeah.

• 20:29Speaker 00

  Um, that's, that's another thing that we have to work on and be aware of.

• 20:33Scott Tolinski?

  I think something, a, a good test for that is if somebody is saying like, this is the only way to do things and it's like a paid product.

• 20:43Speaker 00

  Yeah.

• 20:43Scott Tolinski?

  You know, if it's a paid product, then they're like, this is it. This is changes everything, like that kind of approach. Now, I'm going to show Svelte all day long, but there's no financial, uh, anything involved in that, right? There's no, I don't even, there, there's nowhere to, yeah, like what we possibly do.

• 20:59Speaker 00

  The framework.

• 20:59Scott Tolinski?

  Yeah, we like the framework. Um, and same thing with like view, right? I'm going to say nice things about it all day long, but I, yeah, it is something to be aware of. Uh, that people who are saying, use this, never use this, you only use this, or this is the only way to do things. If somebody says, this is the only way to do things, they're, they're, they're, they might not be saying it for financial gain, but they're saying for your clicks because it's not true. So resist that like dogma of this is the, the, the cult of this particular library or framework. They're all tools for your users, the users at the end of the day, they matter. Yeah.

• 21:39Speaker 00

  Definitely.

• 21:39Scott Tolinski?

  Yeah.

• 21:40Speaker 00

  Cool. Uh, any other tips for us?

• 21:43Scott Tolinski?

  Yeah, AI. We haven't said the words AI.

• 21:45Speaker 00

  AI.

• 21:46Scott Tolinski?

  Uh, I know CJ, we gotta say AI for the clicks. No, CJ has had a lot of great videos about AI and development. The thing I will say is that AI can be useful for learning, but used intentionally for learning.

• 22:03Speaker 00

  Yeah.

• 22:04Scott Tolinski?

  Um, summarize this. I read this paragraph eight times and I don't understand what it's saying. Summarize it. Explain it to me like I'm five. Here's a bunch of code. I have no idea what it's doing. But the things that are important is like, don't trust it. It lies to you.

• 22:18Speaker 00

  Yes.

• 22:18Scott Tolinski?

  Um, it, do not trust it. It will, it will tell you all kinds of stuff, but also like you can use it to aid in your learning. Whether that is more advanced text to speech, whether that is a back and forth, whether that is using it to compare things that if you're, you're giving it this bit of information and this bit of information, compare these two things. So get that information, then validate. But don't have, if you're trying to learn a topic, I'm trying to learn React JS. Don't go to, to your AI tool and say, write this React function for me. You're not gonna learn shit that way. You're not gonna learn anything. So

• 22:58Scott Tolinski?

  you still like, not to say that you shouldn't use AI tools or whatever CJ might say that, but like, not to say that you shouldn't use those tools, but if you're trying to learn something. It, it's the equivalent of like letting your mom do it for you.

• 23:12Speaker 00

  Right.

• 23:12Scott Tolinski?

  Like, you know?

• 23:14Speaker 00

  Or hiring somebody to go do your learning.

• 23:16Scott Tolinski?

  Right, yeah. What are you, what are you gaining out of that? So, yeah, yeah.

• 23:20Speaker 00

  I think the, the, the little bit of pushback I have is, yes, AI is good for learning, especially because it takes a lot of work to figure out how to search the web and how to find the answer that you want. And so AI gives us that instant gratification of like, oh, it just tells me what the thing is. But the pushback I have is that process of searching the web, finding the answer yourself. Is something you'll need even when you don't have AI.

• 23:45Scott Tolinski?

  Sure.

• 23:45Speaker 00

  Before we had AI, that's basically all we could do. We became really good web searchers, right?

• 23:50Scott Tolinski?

  Mm hmm.

• 23:51Speaker 00

  Um, and that's kind of a skill that's going away with AI because you can just ask it a question and instantly see an answer. But like Scott said, you need to verify it and validate it. So my only advice to you is start to work that into your workflow is like, maybe take half the day and use web search instead of AI.

• 24:07Scott Tolinski?

  Sure.

• 24:08Speaker 00

  Um, to work on that skill because uh, you're going to reach a point in your learning and in the things that you're doing where AI can't help you or it doesn't have an answer or the answer is wrong and you're going to have to figure it out yourself. But if you haven't practiced actually searching and figuring it out yourself, you're not going to be able to.

• 24:23Scott Tolinski?

  Yeah. Yeah. And you know, like, I mean, we were talking about type GPU a minute ago.

• 24:27Speaker 00

  Yeah.

• 24:27Scott Tolinski?

  And they're excellent examples and stuff in their docs. Let's say there's some new CSS API and you can copy and paste the entire MDN page for that API, paste it into chat GPT and say, give me a demo with this. Maybe that spits out an example, working example, and then now you have like, yes, we just said, get your hands dirty, write it from scratch. But if you want to just see something in action and then tweak it, modify it, explore it, and then go and write it for yourself. You can have a better idea, or at least again, you're exploring like in real demos in that way, if that doesn't exist. But yeah, I, you know, MDN, right? That's instead of Google, just go to MDN.

• 25:08Speaker 00

  Sure.

• 25:08Scott Tolinski?

  Right? Yeah. Just start searching for APIs and browsing through them.

• 25:11Speaker 00

  Definitely. Uh, so with that, let's get into sick picks. Uh, I'll go first and uh, analog watches are my, my sick pick.

• 25:19Scott Tolinski?

  Oh, nice.

• 25:20Speaker 00

  Um, so I mean, I haven't called attention to it, but I've kind of, I've kind of dressed like the nineties of sorts. Um, but first of all, I got this watch, which has a calculator on it. That's sick.

• 25:29Scott Tolinski?

  You've got two watches on.

• 25:30Speaker 00

  Two watches on. That's a very, that's more of like an eighties thing to do, like two hats, two watches.

• 25:34Scott Tolinski?

  Yeah.

• 25:34Speaker 00

  Um, but uh, surprisingly, being able to tell that, like, I don't even wear a smart watch, but being able to tell what time it is, is pretty great. So having a watch is awesome. Um, yeah, nothing to do crazy. And I have two watches because this has Denver time and this has New York time. So.

• 25:50Scott Tolinski?

  Okay.

• 25:51Speaker 00

  But I'm not going to wear two watches into the future, maybe just one.

• 25:53Scott Tolinski?

  Yeah. Well, the first agency I worked on had a, like a wall full of clocks.

• 25:57Speaker 00

  Oh, yeah.

• 25:57Scott Tolinski?

  And I was like, because of where each of their, uh, because they had just some, a couple of remote work, remote workers, which is ahead of their time for uh, 2011. Yeah. Um, I always thought that was the coolest thing in the world. I was like, I'm going to get a bunch of clocks on my wall.

• 26:12Speaker 00

  Definitely.

• 26:13Scott Tolinski?

  Yeah, I'm gonna sick pick. Man, I don't know if it can be stated or not, because Dbrand is like pretty, uh, popular, but this is my first Dbrand skin.

• 26:23Speaker 00

  Okay.

• 26:23Scott Tolinski?

  Um, not sponsored. Um, and I gotta say, it was really nice. The skin was nice and applied nice. Uh, I hated all the colors for the new iPhone, so I was like, I'm gonna put a skin on this thing. And then also, this is the, the Dbrand Ghost case, which also is very nice. I, I was actually, you know, I don't know if it's something about that brand is always like, kind of turned me off a little bit, even though I think they are funny. Um, but I, I, as somebody who's had a lot of phone cases in general and stuff, I gotta say, I'm impressed with all the stuff. And the, the process was really good to install it all, so.

• 27:00Speaker 00

  So it's kind of like a vinyl stick kind of thing? Like, there's adhesive?

• 27:03Scott Tolinski?

  Yeah, this is a vinyl sticker and it's thick, and you do it with a hair, hairdryer, and you, you get it all on there. And I don't have a, I don't have the steadiest of hands. I'm a clumsy ass dude, and I was able to get this thing on with like, zero issues. So, um, perfectly aligned, install instructions were great. Um, there was a good video. And then I even have like, a, a glass, a glass screen protector on here, which I never have. And that install was great. No bubbles, nice and easy. So they really like perfected the whole onboarding of this stuff. So, uh, yeah, I, I'm sure Dbrand is like, needs no help here, but, uh, I was impressed and I've never bought their stuff.

• 27:45Speaker 00

  Nice, not sponsored.

• 27:46Scott Tolinski?

  Yeah.

• 27:46Speaker 00

  Cool. That's all we got for you. Thank you, everybody, uh, for tuning in and go out there and learn. We'll catch you in the next one. Peace.