--- title: Keeping up with Tech Trends date: 2024-11-19T05:30:00-05:00 author: Sean Smith canonical_url: "https://website101podcast.com/episodes/season-08/episode-1/keeping-up-with-tech-trends/" section: Podcast --- <!\[CDATA\[YII-BLOCK-BODY-BEGIN\]\]>[Skip to main content](#main-content)Season 08 Episode 1 – Nov 19, 2024 33:38 [Show Notes](#show-notes) ## Keeping up with Tech Trends  0:00 0:00 1.0x 0.75x1.0x1.25x1.5x2x [](//dts.podtrac.com/redirect.mp3/website101podcast.com/uploads/mp3/Season-08/S08-E01-keeping-up-with-tech-trends.mp3) In this episode we discuss strategies for keeping up with technology trends and how to choose what to learn. ### Show Notes - Welcome to season 8 - CMS - how do you choose a new CMS? - Maintenance contracts and security updates - Front end frameworks - CSS, Javascript, etc.. - Laravel Mix and Vite - Friends and colleagues influencing - Code Editors (VsCode, Cursor and more) - AI and Copilot - upcoming topics in season 8 ### Show Links - [Lunch Bytes (November 20, 2024)](https://www.youtube.com/watch?v=o2SRAC7Bolg) - [Imposter Syndrome (S07 E04)](https://website101podcast.com/episodes/season-07/episode-4/motivation-burnout-and-imposter-syndrome-with-kevin-nicholson/) - [SyntaxFM](https://syntax.fm/) - [Visual Studio Code](https://code.visualstudio.com/) - [Cursor](https://www.cursor.com/) - [Claude AI](https://claude.ai/) Powered Transcript Accuracy of transcript is dependant on AI technology. **\[00:00\]** **Sean:** Hello, my name is Sean Smith. I'm your co-host and this is the website 101 Podcast, the podcast for people who want to learn more about building and managing websites. I'm here with Mike Miller and Amanda Lutz, my co-host. Hi guys, how's everybody doing? Good things, how are you? We're back. We're back. It's great to be back. We've got a number of episodes planned for the upcoming season and we're really looking forward to recording and showing with everybody. Congratulations friends on making it to season eight. Season eight. It's hard to believe it's been that long and that many episodes. So a lot of people have podcasts that last. Everyone has a **\[00:48\]** **Mike:** podcast these days but not many that last this long. I remember when I set this **\[00:53\]** **Sean:** up that I saw something about the average number of episodes for a new podcast before it fades away **\[01:00\]** **Mike:** somewhere like 10 to 13. So episodes? Oh yeah. Yeah. Yeah, because I mean it's a lot of work. And **\[01:08\]** **Sean:** honestly, I started it alone, but I could not, I would not be here if I was still alone. I really need to share the workload with you guys. You guys help keep it going because there's just so much to do. **\[01:20\]** **Amanda:** there is and also I mean I've tried to so for new listeners we also have a lunch bites which is a YouTube live that we do on the first and third Wednesday of every month and over the summer especially you know people are on vacation people get busy with work I've tried to do one of two of those lunch bites like solo and it's just clicking a button like there's zero production effort behind that but sitting there and trying to like think of a topic and ramble to yourself and trying to make it relevant and entertaining and not getting any feedback and any communication and back and forth and it's hard just talking into a void. So Sean, kudos to you for keeping it up on your own as long as you did. **\[02:03\]** **Sean:** Yeah, you knew monologues are tough, and speaking of lunch bites, there is a lunch bites scheduled for the day after this episode is scheduled to be released. So we're releasing on, we release on Tuesdays, that then this one's scheduled from November 19th. There should be a lunch bites on November 20th. So if you're listening, here's a real reminder, tomorrow, there's a lunch bites coming listen to us. **\[02:31\]** **Amanda:** And it's already, it's already set up and scheduled on YouTube. You can go find us right now, website 101 podcast on the YouTube channel, go, go subscribe then get ready for tomorrow's live. **\[02:45\]** **Mike:** And watch the back episodes. **\[02:47\]** **Sean:** So listeners may know that our favorite CMS CMS and I'm going to bring up something that they do they are they relentlessly update the CMS every week there are updates released whether it's a security update or new features or bug fixes they're not a CMS that does it like once a year it's every week every couple of weeks you got to keep up with that and it's not just that I mean there's there's different kinds of frameworks, JavaScript frameworks, CSS frameworks, AI, all of these things. There are so many options for content management systems (CMS), each best suited for different users and end goals. Let's assume craft did not exist, what would you do to pick a new CMS? **\[03:43\]** **Amanda:** Yeah, lots of topics to get into, but before we overwhelm our listener, and it's just like already trying to head in the sand, which is totally what I do when I'm overwhelmed, let's just break it down one topic at a time. First, I want to talk about Sean started to the content management systems. There are so many options and there are so many best for the end user, best for the content editor. Like how do you, I'm going to put out a hypothetical. Let's assume that craft did not exist, even though please, universe, don't let that happen. We all like craft. But Sean, Mike, if craft didn't exist, what would you do to pick a new CMS? **\[04:28\]** **Sean:** Oh, that's a tough one. I want Mike to go first. OK, well, so yeah, that's in, like you said, **\[04:35\]** **Mike:** there are a whole bunch of different things to consider in making that decision. There's like how flexible is it for me to develop the site? How user-friendly is it for admins to manage the site later? There's like longevity of, like, is it, you know, they're going to go bankrupt tomorrow, that whole thing that clients sometimes worry about. Plug-in ecosystem, is there a lot of extensibility, extendability, whatever the word is, to make it more than it already is? All that kind of stuff is something to be considered. And I find, Sean, just before you answer that question, I find one of the things I'm constantly getting trapped into is once I find a CMS I like, I use it all the time. It used to be expression engine, I used it for years, as you all did as well. And that was the only CMS I would ever use. Then I moved to craft and I started realizing, oh, there's all these other CMS's, statumic and stuff like that. And now I just find I use craft pretty much all the time. And I worry that, you know, am I should I be branching out more? Or, you know, anyway, I'd like to know your thoughts on that. But Sean, first, how do you evaluate? Yeah, I am going to respond. **\[05:50\]** **Sean:** I am going to respond to your thing at the end of my bit. How would I respond or what would I look for is number one is community. I want a good developer community. That's more important to me than anything else because I want to be able to talk to somebody who best practices. I want to know that the CMS is going to continue to exist and grow and people care about it, a non-toxic community. So, Craft CMS is probably the best online community that I have ever been in. Craft doesn't exist. Oh, but my point is, I don't know another one that is quite as good as that. Okay, so, community, very, very important. Second, documentation. **\[06:44\]** **Mike:** Documentation yet. **\[06:45\]** **Sean:** Documentation is really important. I think craft docs are good, but they're not great. are better, there's better documentation out there. So that's their only weakness in my opinion. And as Mike said, I want to have extensibility whether it's plugins, modules, or things like that. And finally, author experience. So that my clients can enjoy using it. There's no point in building them a website with a CMS if they don't enjoy or find it easy to update their content. **\[07:16\]** **Mike:** Right. **\[07:17\]** **Sean:** And this is, I just don't have the brain power to keep a working knowledge of two different CMSs in my repertoire. Like I worked on an expression engine site earlier this summer. Yeah, I'm familiar with all of their concepts, But I haven't worked on EE in a few years. So I had to reference the docs and things like that. I was unfamiliar with some of the plugins that we were in use, or the best practices, or what's popped through, or what's not. So there was a lot more work for me to do, because I'm not familiar with it. I think for an agency, if you've got a developer team, whether it's two or three or four developers, you could specialize in two different CMSs for targeting two different types of clients. Maybe a smaller client and one that needs a more bespoke options. So that's my thoughts on it. Amanda, what do you think about that? Security is also an essential factor when choosing a CMS as it ensures the safety of the client's website, whether it's for a small or large business. I prefer to use a well-established CMS with a good community and strong security measures in place. **\[08:52\]** **Amanda:** Every thing that both of you have already said, I absolutely agree with security as well. It needs to be secure. Even if it's like, and every CMS does their best with security, with security. Obviously nobody wants anything to ever be hacked and I always think that it comes back to making sure that the client is reassured, that even if it's only a website for the mom and pop shop around the corner and it's just a little brochure site, for some reason security is always top and foremost in their mind as well. So I think that having a well-established CMS that has, I prefer one that's been around the block, that's been around that has like the good community group and, you know, good people working on it, but I also think that it's easier to see if they've had any security issues. So I'm not saying that I would never check out, like, a brand new development, but I probably would feel more comfortable with something that's been around for a while. Next up, let's discuss front-end frameworks and how to cope with the constant changes in technology. **\[09:59\]** **Sean:** Yeah, I'm on board with that and a little side note about the security things as a developer you should be updating your client sites as often as possible, especially if there's a critical security update. I strongly encourage quarterly maintenance for all websites. **\[10:18\]** **Amanda:** I'm really, I'm really bad at selling my clients on that. I'm usually very much just and and sometimes to sell them on the project I'm like we're gonna make it once and you're gonna have it and then the project is done **\[10:31\]** **Mike:** Yeah, yeah, at least a maintenance thing where you keep it up to date and if not then also look You know keep working with me and we'll keep adding features to the site kind of thing That's the next the next level **\[10:42\]** **Sean:** You know yeah earlier this summer I I rebuilt a site from craft two to craft five and it was like a complete rebuild just because there was no way to no path forward. I pushed the maintenance contract, clients like, yeah, maybe I have to follow up with them. It's been two minds and it's like, yeah. Come on, they were interested, but they didn't want to do it, start it right away. And it's like, yeah, but you're going to end up in the same situation. **\[11:11\]** **Amanda:** Yeah. Okay, let's step away from content management systems because you know what else? What else is constantly always growing, changing and evolving is the front-end framework. And whether it's a CSS framework, like Bootstrap or Tailwind, or if it's like a more advanced framework, like React, Angular, View, Svelte, Swiftie, NextJS. NextJS, there are so many. And I super get overwhelmed. Even sometimes talking about Sean with your starter, don't you use, it's not a front-end framework, but don't you use, like, you used to use Gulp to set it up. And now you're using different things. And and quite frankly, there's a lot of times where I just I just tune out. It's like too many buzzwords being thrown at me. How do you guys cope with that? Um, to know. You nailed it. You nailed it. Like seriously, **\[12:06\]** **Sean:** I I have a high level awareness of things. But until I have a problem with my existence thing set up, I'm not looking into it deep. So you mentioned things like gulp. And this is my build process. I don't use gulp anymore. I was really happy with gulp for a while. But it was slow. And then people were talking about laryl del miix. And you know, it'll make your site build faster or like the compiling faster. I finally switched. It was a hassle to switch all my projects over and get everything where I wanted it. I've been using it for a few years now. I'm aware of VIT and that it's even faster. But guess what? Their real mix is not slow. And it's not slow enough that it's creating a problem and I want to switch. So if I end up having a problem or maybe VIT or another one of these things has a feature that is must have for me, then I'll look into it. I don't have, my focus is on getting business, not on learning new technology. **\[13:19\]** **Amanda:** Yeah, well, even just how you said that, it's like until something comes out that solves your problem better or that has a better feature, I don't even know that I have time to be paying attention to all of the new features that all of these different development frameworks have available for us so that I know when it's time to start to look into, so, quite frankly, Sean, I just copy your stuff. I think I started using the, what is the Laravel mix? Go-oh mix? Yeah. **\[13:47\]** **Mike:** I use that too. **\[13:48\]** **Amanda:** And I only use it to have the browser refresh when I save. **\[13:54\]** **Sean:** I can help you out with that because yesterday. Do I care? No, no, because it's even lighter weight. Yesterday I was working on an old site with Bootstrap 3 and SAS with no build process. All it has is Compass. And so I was like, all right, I can't handle this anymore, we're building new sections, got approval, and I've added a tailwind to site. Part of that was like, I need it to compile, and I want the browser to refresh. A little bit of AI work 10 minutes later, I have an NPM script, I just run NPM run start, and boom, it does everything. It's a much later, it's a much later wait, set up then the full layer of our next thing. **\[14:39\]** **Mike:** Yeah, but if it's not broke, well, I fix it. **\[14:41\]** **Amanda:** Well, I fix it. Yeah, I need the whole thing already, because I **\[14:47\]** **Sean:** it's an existing site. So that's why it was going. **\[14:50\]** **Amanda:** I know, I was just going to say, so yeah, before we like dive too deep, I wanted to kind of keep this episode a little more high level before we dive too deep into any specifics. I want to to reference our user, hey, we have a whole episode in a previous season about Imposter Syndrome and getting overwhelmed and how it affects everybody and how to try to overcome it. So we'll add a note in the, in the, add a link in the show notes to that previous episode. **\[15:18\]** **Mike:** It's episode four of last season, season seven. It's called Motivation Burnout and Imposter Syndrome and it's with our friend Kevin Nicholson. He's the guest on the show of that episode. **\[15:27\]** **Amanda:** Mike already has all that information. I remember that episode, that was a good one. Yeah, so then, where do the two of you find your tech news? Do you have any resources that you find you keep going back to? **\[15:41\]** **Sean:** A couple of discord that I go to, mostly craft discord, but I do go to our front end discord once in a while, and then the syntax FM podcast. **\[15:51\]** **Mike:** Yeah, I usually get my news from podcasts. I don't use social networks anymore, and so I don't get news that way. Yeah, it's almost always just podcasts that I listen to, stuff like that, where they start talking about this or that technology. That's how, like I use Tailwind for CSS, and that's one of the few ones where I started hearing about it so much from people that I respect, that I thought I'd better try this thing out, even though I use, it was foundation, I used at the time was my CSS framework, not to get too technical again, but I started using it because I heard about it and that's why I switched. But yeah, it's usually just people in the industry I respect and what are they doing these days? **\[16:34\]** **Amanda:** That kind of thing. I have to say that instead of people I respect, I'm on Reddit a lot. Reddit is almost the only social platform I'm on anymore. And I do subscribe to the, what is it, slash web dev. And so it's like, I like to just kind of keep an eye on the questions that come up. And so what was the technology that might be confusing? And so very often people will get on there and be like, I'm starting a new project. What framework should I use? What front-end should I use? What server should I host on? So it's nice to see more of a majority opinion. I think that it likes to kind of keep things balanced between what everyone's using and if it matches what the trusted professionals are suggesting. **\[17:21\]** **Sean:** Yeah, I also think it's kind of important to pay attention to what your friends and colleagues in the industry are using. So, yeah. **\[17:32\]** **Amanda:** But working for ourselves, it's hard to know what colleagues are using, right? **\[17:37\]** **Sean:** Yeah, but that's kind of why we have this Slack chat that we're all a part of here in Toronto. And we talk about these things. Like there's another guy in Ottawa, I won't name him, but he uses expression engine, and then he really loves to try out new technology, and he's really good at it. Powers him. I learned about new stuff from him, but I don't always use it. **\[18:06\]** **Mike:** It's good to have friends like that. They'll do all the testing for you. Okay, so speaking of, we're getting into code a little bit here. I want to talk about a big thing that's happening these days, which is the actual code editor that you use to write code. So for the longest time, way back, it was sublime text I used to use, I think. And then after that, I moved to VS Code, Visual Studio Code, which is a product. **\[18:32\]** **Amanda:** Oh, but there were ones in between. There was, I used Adam for a while. I used notepad plus plus for a while. I used notepad plus plus also. Yeah, and then from that, I moved to Visual Studio Code. And I am currently, I don't like to pay for things. Amanda is super cheap, but I am currently paying for GitHub co-pilot with Visual Studio **\[18:53\]** **Sean:** code. I've been paying for GitHub co-pilot as well for about two months or three months now. I bet the bulletin paid for the year because it's cheaper. Yeah, well, you know what, I might switch to the year one because I can see that I'm going to continue to use it, but I'm not going to switch to the year until I make that decision about cursor. I'm interested, but the cost of switching and it's not financial cost, it's the time cost that I'm concerned about. Mike has switched. Let's hear about your. **\[19:28\]** **Amanda:** Yeah, cursor is big news right now. Mike, do you share? **\[19:31\]** **Mike:** Right. Okay. So, VS Code is usually the industry standard pretty much these days. It's a very great editor that people use. And they've implemented GitHub code pilots because Microsoft owns the the whole thing and it lets you do AI stuff in there and it can help you write code and this and that. It was great. I was using that too. Then the big news, whatever the new thing everyone's talking about was an app called Cursor which was a forked version of VS code. Someone forked it, made a copy sort of thing which you're allowed to do and then they implemented AI directly into it so you don't have to subscribe to GitHub co-pilot specifically. It gave you all these advantages, like co-pilot, let's you use. **\[20:16\]** **Sean:** There's four different ones I saw. I was looking at it yesterday. Four different. **\[20:20\]** **Mike:** That's because they changed, though. Initially, there was one AI model that you were allowed to use, and then cursor came out, and it let you switch between clawed and all these different AIs that you might prefer. **\[20:32\]** **Sean:** I was using clawed yesterday. **\[20:34\]** **Mike:** Yeah. And then anyway, this is why I switched to cursor, and I just thought it was a better experience. And that's what I'm using now. And then I see, you guys are funny. You guys are talking about your subscriptions. When I signed up for it, I was like told, I was told, if you sign up for a year, I think it saved like $50. It was quite a lot of savings. And I was like, I don't know, because I'm not sure I'm committing to this yet. And I'm kind of glad I didn't, because the next day, GitHub put out their, I don't know, they did their conference or something. And basically announced that they're going to incorporate everything that Cursor was already doing into co-pilot. So like they're trying to one up each other, you know? Yeah. Obviously that's why they do these year things and like sign up with us because you don't leave, you know, that kind of thing. **\[21:24\]** **Amanda:** Well, I signed up for the year with co-pilot because I had not heard of Cursor. Like this was like a few months ago now. And I was like, and again, everyone uses Visual Studio Code, everyone's talking about co-pilot. it's going to save me some money fine I'll pay for the year and then like literally two months later everything everything is about cursor cursor cursor cursor so now I am kind of kicking myself in the ass but now Mike that you said that tell them tell them what you heard on the syntax FM podcast **\[21:55\]** **Mike:** yeah so that's again that's where I get a lot of my news from podcasts and yet they have both switched and they went to that conference and they talked about all kinds of features that are being built in And it's kind of like we're in a situation where it's a good position to be in as a consumer like us. We can kind of just wait and see who wins, you know what I mean, or bounce back and forth between them. And it works out pretty well. And I just want to say Amanda, you were talking about, you know, you signed up earlier for the yearly thing or whatever. Listener, if you're concerned about all this stuff we're talking about, should I be using cursor should I be using, you know, co-pilot with whatever? My position, I don't care what you use, doesn't matter, use whatever you're comfortable with. I do recommend you start using AI in your code editor in some form. Like get an editor that has it, whether it's co-pilot or cursor or something because AI will really help your coding experience. But beyond that, who cares what you use? **\[22:56\]** **Sean:** That's my joke. I'm with Mike on this and it's not, and it's not just about code editors, it's about all the hardware. Windows versus Mac, who cares? As long as it works for you and gets the job done and you can deliver to your clients, that's all that matters. If you want to use notepad plus plus or hell, just wordpad and it works for you. That's kudos to you. Yeah. Yeah. **\[23:21\]** **Amanda:** Well, and so even just now, when earlier, when you were talking about all of the different AI platforms that GitHub co-pilot now uses. It's like I don't know the difference between them. I'm not going to research which one is better and I'm just going to use whatever one comes default until one of my colleagues tells me you know just change a setting that a different one's better and I feel like this is happening not just with code and not just with text editors but also with like there are so many AI platforms for and for a prompt and it'll create a 30 second video enter a prompt and it'll create an image and it's just there's so much happening right now by so many different companies that some of them in the long run some of them are going to be successful and some of them are going to fail and go away and so in the meantime exactly like what Mike said listener get in start playing with it learn how to become comfortable with it because it's a tool like anything else use it as a resource you still need to know how to work it and what to do with with that information once you've got it, but get comfortable with it now. It's not going anywhere. And eventually, like right now in the Wild Wild West, eventually there is going to be a smaller handful that are the standards. **\[24:37\]** **Sean:** Yeah, I want to go back to the AI a bit. Earlier this month, I think it was this month in Slack. Mike mentioned that he uploaded a screenshot or designed to AI in cursor and cursor spit out the code in a working website. I was like, that's amazing. So I was in co-pilot yesterday and I had a brand new design that I need to do for a new section of a website. And I couldn't upload anything and I switched the browser and the engine. I said, hey, can I upload it? How do I upload an image to have you do this? And I said, I can't currently do that. And I was like, okay, all right, you can't do that in the browser, but I could have gone to the Cloud.ai website and done that because you can't upload an image there. I have a different story about that. But instead, all I did was like, hey, listen, I want, I described the layout, and then I said, I also want this section to use a swiper slider. And I want the buttons, the controls on the bottom right corner and image on the left with a testimonial on the right, how do I do that? And it's spit out mostly working code. And I think in the future, for me, I would instead just say, hey, give me the swiper starter code. And it'll grab it from the docs, spit it out there. I don't have to switch to Google search for swiper, search their docs, copy and paste. Instead, I just spit out the code sample from the docs. So that's a good way to do it. You don't need the whole image to website thing besides that I'm still not fully trusting of the quality of the code that it may spit out as well. **\[26:35\]** **Amanda:** No, like I said, it's a resource. Use it like any other resource. You still need to review the content it gives you. You still need to look at the image that it generates for you to make sure that people have all of their fingers. you still need to, it is early days and we still need to monitor the output that it gives us and we still need to know what to do with it. **\[26:59\]** **Sean:** Absolutely. **\[27:00\]** **Mike:** Well, I think Sean, you made a good point earlier when you said, you know, your job is to bring in business, not to necessarily experiment with a million different tools and so just use whatever is working and that kind of thing. I fully agree with that and I think the key to using AI in this wild west, you know, it's moving so fast, is try to be mindful of how it can save you time in your job. So like if you've got business to do, you know, bring in business or build sites or whatever, have a think about what can AI do for me that's going to make this simpler, whether it's build a slider element or anything else, like even just brainstorming, there's a million things it can do for you, so don't avoid that stuff, I would say. **\[27:47\]** **Sean:** Yeah, slightly off topic, but still on Claude and I, listeners may know that I am an avid amateur photographer. So I uploaded four of my images to Claude, and then I asked it, please tell me something about the photographer and the style of images that I uploaded. I saw somebody else said, hey, I did something similar. And it spit out about six or 700 words discussing the stuff. Now it was all very generic and whatever, but it was an interesting experiment. So you can try different things like that over the coming months and years, AI is definitely going to improve, but the key is it's not a human, so you're not going to get any emotional response, which is what you would want from something like photography or art related. **\[28:49\]** **Amanda:** Well, but even some generic description like that, you could go through and edit it and pare it down to come up with a half-decent bio. Everybody hates writing bios about themselves, but this is, again, another example of AI coming up with content. **\[29:04\]** **Sean:** Oh, I recently spoke at the .1 craft conference here in Toronto, and I needed to have a description of my top, and I workshopped it with AI to get the one paragraph description so that I was really **\[29:21\]** **Mike:** happy with it. Yeah, cool. Speaking of the craft conference that we all attended there, .1 here in Toronto, there was a talk there by someone who works with MostlySeries, which is a web dev company, And he gave a talk about AI and how they use it. And one of the cool things that they said they do is I forget all the tools they were recommending we use, but one of them they dumped in all of their documentation about their company basically. And then whenever they get word of an RFP that they might respond to, they put it in there and they ask AI to spit out a percentage value for how likely is it they might win it. And it might say, oh, you're 61% and they might go, We're not going to go after that one, but if it's like 80% or more in terms of the amount of Services they offer relative to what they're being asked they're asking for then they'd go after it and that's a great That's a great use of AI. Yes **\[30:15\]** **Sean:** Absolutely. That is going to save you tons of time because now you don't have to and you're not going to have to spend as much time Reading the RFP and thinking about your company and analyzing like is it worth it? Yeah, and as we all know writing those kind of things is just like soul-suckingly Oh, man, it's hard work. It's the hardest thing about being a self-employed person **\[30:41\]** **Mike:** We have an episode about RFPs as well. Yeah, yeah, we did one, didn't we? **\[30:46\]** **Amanda:** Yes, anyway, my friends. I think it's time to wrap this up Absolutely Listener again, welcome to season eight somebody somebody tease our listener with with stuff that's coming up this season. **\[31:01\]** **Mike:** Yeah, we had a bunch of topics that we were gonna address in future episodes. One was this whole WordPress nonsense that's going on right now. We didn't mention WordPress explicitly on this show today, but that's obviously one of the CMSs that a lot of people would end up choosing. We know that there's a controversy happening with Matt Mullin-Lague doing a bunch of crazy stuff. **\[31:22\]** **Amanda:** We'll dig into that. **\[31:24\]** **Mike:** Yeah, on a fridge your episode. **\[31:26\]** **Amanda:** I think that, so we've got ideas. I think we were gonna try to bring back our lawyer friend, David Canton. We were gonna maybe bring on an accountant to talk about some money matters, which would be useful for independent developers and also for small business owners out there who are listening. And then we had a couple other cool topics. **\[31:47\]** **Sean:** Yeah, like we did web hosting way back in season two, I think, or season one, but we're gonna revisit it with another owner of a different webhosting company, things have changed since then. It's always good to get some updated view on something that is so integral to your job. **\[32:07\]** **Mike:** Yeah, and we think we might bring, we might talk about some requests that we've had from listeners regarding the onboarding process, project hacks, things like that. So keep on the lookout, subscribe, tell your friends. Lots of stuff to look forward to. **\[32:22\]** **Amanda:** Yes, and in the meantime, of course, there is Lunch Bites. First and third Wednesday of every month, we will see you on the YouTube. **\[32:30\]** **Sean:** Awesome, on a recap. If you're listening to this on the first day, it gets released tomorrow. Tomorrow is a Lunch Bites. **\[32:38\]** **Mike:** OK, good to talk to you guys. **\[32:40\]** **Sean:** Looking forward to the next episode. Bye. Bye. Bye. **\[32:48\]** **Amanda:** The website 101 Podcast is hosted by me, Amanda Loots. You can also find me online at AmandaLutes.com. **\[32:55\]** **Sean:** Recording from a secret there while plotting world domination, I am Sean Smith, your co-host. **\[33:01\]** **Mike:** One of your hosts today was me, Mike Mellon. Find me online at belikewater.ca or on socials at Mike Mellon. What's that rattling? **\[33:17\]** **Sean:** Oh, that's me playing with my snack that I'm gonna eat as soon as this is over. Yeah, I would save that for later all right, you don't want you don't want this **\[33:28\]** **Mike:** Okay, it's almost enough to share with everybody Mike can cut that out and post. He's good **\[33:34\]** **Amanda:** Yeah, I'll just take more work for Mike Close Transcript Have a question for Sean, Mike, and Amanda? [Send us an email](/contact). [![Listen on Google Play Music](/assets/images/google_podcasts_badge@2x.png)](https://www.google.com/podcasts?feed=aHR0cHM6Ly93ZWJzaXRlMTAxcG9kY2FzdC5jb20vZmVlZC5yc3M%3D)[![itunes badge](/assets/images/itunes-badge.png)](https://itunes.apple.com/ca/podcast/website-101-podcast/id1449510012)[![itunes badge](/assets/images/spotify-logo.png)](https://open.spotify.com/show/3rmSM1R9t6q1U8DmYWJRSO?si=NrYPMgDaRV6Dd56PjEaPow)### Season 08 - 1 [ Keeping up with Tech Trends](https://website101podcast.com/episodes/season-08/episode-1/keeping-up-with-tech-trends/) - 2 [ What's going on with WordPress?!](https://website101podcast.com/episodes/season-08/episode-2/whats-going-on-with-wordpress/) - 3 [ Shortcuts That Save the Day: Boost Productivity in Web Dev and Beyond](https://website101podcast.com/episodes/season-08/episode-3/shortcuts-that-save-the-day-boost-productivity-in-web-dev-and-beyond/) - 4 [ Stand Out on Social Media with Jessica Perreault](https://website101podcast.com/episodes/season-08/episode-4/social-media-with-jessica-perreault-2/) - 5 [ Code of Ethics: Navigating Moral Dilemmas in Web Development](https://website101podcast.com/episodes/season-08/episode-5/code-of-ethics-navigating-moral-dilemmas-in-web-development/) - 6 [ Season 8 Wrap](https://website101podcast.com/episodes/season-08/episode-6/season-eight-wrap/) ### All Seasons - [Season 01](https://website101podcast.com/season/01/) - [Season 02](https://website101podcast.com/season/02/) - [Season 03](https://website101podcast.com/season/03/) - [Season 04](https://website101podcast.com/season/04/) - [Season 05](https://website101podcast.com/season/05/) - [Season 06](https://website101podcast.com/season/06/) - [Season 07](https://website101podcast.com/season/07/) - [Season 08](https://website101podcast.com/season/08/) - [Season 09](https://website101podcast.com/season/09/) <!\[CDATA\[YII-BLOCK-BODY-END\]\]>