Welcome to Inspect, a podcast about web design and development. In this week's show, we're going to be talking about our top 10 VS Code extensions. So we'll be picking our top five and we're going to compare, see what the list is like. So kick us off, Kaj, do you want to go first with your number five spot?
Yeah, so it was a bit difficult to put in a number five, but this is so many out there that I'm using. But I think going through what I've been using recently and what's most helpful for me, I think, going with Auto-Close Tag is my number five. It's self-explanatory there. You're writing, especially for me when I'm writing HTML for templates, especially for Word Press and things like that.
Just the ease which tags and divs are closed when you're starting to write your code. It will, you know, it'll know straight away when to close the tags for you because you get into a lot of situations where you're probably writing a lot of code and you tend to miss a closing tag here and there. And I've been, I've been in that situation myself quite a few times, actually, especially when I've been going through code I've written before. And realizing later that is a missing div or, you know, the closing HTML tags are not there for some reason, but yeah, the Auto-Close Tag is my number five.
Yeah, it's handy, especially when you, when you're handwriting code and you know that you're about to do several layers of nesting. Like if you're creating a div with an unordered list in there with list items with paragraph tags, you tend to write your opening div, your opening URL, your opening LI and the opening p tag and then you've got to remember to close them all in that order. So having the Auto-Close, I mean, it's surprising that VS Code doesn't ship with it. It's out of the box.
Yeah, it should be native, I think. I just yesterday I was working on some code somebody else that wrote and it had nests upon nests upon nests and you had article tags within divs and within that you had unread lists and it was just mental, but using the Auto-Close feature in VS Code just saved me a lot of time. Yeah, yeah, I've got it installed as well. It didn't make my number five spot, but it's up there still.
I instilled mine quite a while ago, so I don't know if VS Code has actually introduced this natively now, but the plugin still exists and it's still getting stars and downloads, so I'm guessing that it's still not native. I think it's still not native because it's still there. The one that I just found, there was another one I found that had just been removed because it's native now, so they are going through them, I think. Okay, brilliant.
Right, and the show notes will include links to all of these links to the VS Code marketplace for all the extensions that we mentioned. All right, so my number five spot is Accentiable Colorize, which is spelled in the American way, C-O-L-O-R-I-Z-E. Basically, what this does is it draws through your code and it finds, it mainly for CSS, obviously, and it finds any hex values and HSL, any RGB values, and it basically gives them a background color which matches the color that they represent. So the good thing about this is it also works with SAS, so it colorizes your SAS variables.
It basically searches up the chain to where that variable is declared and picks out the color. It also works with CSS custom properties as well, so you can have some weird names for your custom properties and they may not necessarily be very obvious. And it kind of shows you a quick background swatch of what that color is. That's pretty cool.
I have a little different one, definitely. Yeah, I'll find it really handy in my SAS variables file because I like to organize my color palette in sort of hue color, and they're not necessarily going to be 10% gray, 20% gray, but generally you have like five or six shade of gray and one will be lighter and then will be darker, but they may not necessarily be called gray light gray dark, for example. So it's nice to just have visual cue of which one is the darker one, or which shade of red is slightly darker than the other. I think that's really handy, especially when a design has been passed on to you and you're just literally just working through a coat, and it's always good to have a visual cue of the colors, the brand colors that you're working with within your coats of is there.
I mean, that's so handy. That's brilliant. I'm going to have to look into that one. Yeah.
Yeah. I can see that one helping me out. And it just means you don't have to keep referring back to your variables files or you can just, because as you're writing your CSS, the plugin is encouraging enough to search up the tree and find where that variable was first declared and it picks out the color. So it's very good.
Okay. So before Git lens, and again, it just made it into the top five recently. I heard it mentioned on Twitter, this developer that was following, and I just kind of picked up and started using it in a project recently. But it's just essentially using, well, it's just like get on steroids really within VS Code.
And the reason why I'm using it within VS Code is just to allow me to navigate and explore repos and the code comparison inside of it is just really, really helpful, just having everything natively there, rather than going, because I usually use that source code, so it's also a tree to when I'm working with repositories and stuff and pushing anything to a repository. But I wasn't using it that much before. I think I mentioned that in previous episodes, but recently I'm working with a couple of other guys on some projects and it's just really, really handy to have it within VS Code, rather than having another application for which you don't find these kind of things. But for me, it's just brilliant.
And I've started to use it a lot more now. So definitely, before I can see it's moving up to number two at some point. But yeah. Yeah, you're right, I get that as well.
I did have it in my list at number three spot, I think it was, I've since removed it because you've added it, so we don't really need too much repetition. But yeah, I'll use Git Lens as well. I don't use it heavily, because like you said, as well, I mainly do all of my Git workflow using source tree. The only time I actually turn on, because you can toggle Git Lens just using the command palette.
So I have it turned off by default most of the time. And then I literally just turn it on every now and then just to get a quick idea of who did a certain line of code in a file, for example, if this, and normally if I find something which doesn't agree with the way I would have done it, and then I at least I can find out because I do work for an agency and we have several people, you know, working on files at the same time. It's quite handy in my case to just turn it on now and then. But I do really like the diffing features where you can see, you know, the before and after a file.
So I find that a lot cleaner to do that in VS code than it is to do that in any external file, diffing tool or doing it in source tree. So yeah, that's why I like it. And also like that, you know, when you have got it toggled on, it sometimes it can overpower your file a little bit, but it's nice to just have that little muted text next to each line showing, you know, the date it was last committed and what the branch name was and so on. But like I said, it does clutter your file a little bit, so I did turn it off most of the time.
Yeah, I'm the same, literally just like it's on and off when I need to look at it. It's on. Yeah. Okay, my number four spot.
I also did have auto-close tag in there, but another one that I use in conjunction with auto-close tag is auto-rename tag, which again, it's very self-explanatory. What it does is if you've got a diff on your page and you've tried it with some text in it and you realize actually I need to make the semantic only to turn into a paragraph, you can just rename the opening tag and it automatically renames a closing tag. So yeah, this I use this a lot with which react especially where you've got because it works with them. It's not just native sort of HTML tags, it's any custom tags as well, so it works with react component tags.
And it's good when you're maybe copying and pasting some example code from somewhere else and then you want to change the markup slightly, but not necessarily the structure. And yeah, an example of that is like if you want to change an unordered list or order list, you can just quickly just rename the first one and it will make the closes, renames a closing tag as well. They are really good. Works well with auto-close tag.
Nice. Might have to get one on board as well. Right, go on there. Number three.
Cool. Number three. So for number three, I've got prettier. I don't like the name, but yeah, again, it is self-explanatory when it comes down to format in your code.
And me being me and a top person, I must spend a lot of time wondering how and if I'm going to format the code in, you know, just say HTML file or a CSS file, do I write my CSS all in one right? Or do I do it the long way and you know, use tabbing and things like that for a new declaration of things like that kind of style. Using this plugin really, really extension really helped me because I don't have to think about that anymore. So it's literally start typing it out, however, want to type it out and you know, I can use presets or whatever the default settings within the extension and you know, it just formats it for me.
And I'm generally happy with the format anyway. So yeah, it just saves me a lot of time and hassle and your code just looks really, really nice in me afterwards. Yeah, do you have any overrides that you've put in? No, I haven't.
Not yet. Not yet. No, but that is definitely something I need to be looking into because it's such a handy feature. Yeah.
Yeah, I pretty much use it default out of the box as well. I think the only thing that I've changed on my prettier settings is the tab width changes to two spaces instead of four. Yeah. And I think there's the trading commas option I've got it turned off, probably this should be off anyway.
Yeah. So that, you know, trading commas on and allowed. I should keep that on actually because it's actually handy to have trading commas on. But yeah, otherwise I keep it pretty much out of the box.
It seems to have good, good opinions on ways to format code. But you know, the beauty of the plugin is that all there is opinionated, everything's like, everything's an option. So you can just turn it off. And then the great thing is you can obviously then create this pretty, a conflict file as well, add that to your repositories so that the whole team can be working off the same formatting options.
So that's right. Yeah. Do you have your set to format every time you save the file or just do you do manual formatting? It's manual at the moment.
Yeah. Yeah. I do my manual as well. I found out I didn't auto formatting it.
Sometimes it makes it hard to read your code while you're typing it. Yeah. I find that I've been doing. Yeah.
Yeah. Because sometimes you do want to have non-conventional formatting while you're actually just laying out your content. Yeah. And I don't mind if like text lines lines are longer than you know, the suggested wrapping point, for example.
Yeah. And I think it keeps your coding natural as well. That's what I find about it. It's the normal way that you've got to code without this extension.
It helps to keep that balance of him. Yeah. Yeah. I've worked on some projects where the code formatting was very strict, where you couldn't even push a commit to your Git repository without fixing all your sort of formatting errors.
Wow. And it just, although it created a really nice repository in the end and very clean code, it just made it, it just made the whole sort of development cycle really slow. So every time you would go to push your commit, you'd just end up with these stupid errors. And you know, errors about white space and stuff like that.
I know some people have probably very particular about that sort of thing. You know, there might be people showing at their, showing at their, not at their screen, but at their podcast player announcing, you know, what you're doing, you need to have this enforced. But I suppose it depends on the size of your project and the number of people working on your project. But for small teams, it doesn't need to be that strict, I don't think.
No, definitely not. Yeah. Yeah. Cool.
Cool. Well, I've got pretty on there as well for the down my list. So that's going to be coming up soon. My number three spot, I've, I've just switched out actually because we had some repetition, but I've just added in a plugin called Better Comments.
So what this does is it's got a few shortcuts for creating quick, like, comment blocks and things like that. So you can have like multiline comments and single line comments and comments in certain formats for different types of files. So, but the beauty of it is, is that you can add like modifiers into your comments. So you start your comment off and then add an asterisk.
And then what Better Comments does is it highlights your comment in green. If you put a next formation mark at the beginning highlights in red, if you've got question mark highlights in blue, for example, and then if you start your comment with the word to do in uppercase, then it gives you a nice orange, right, orange comment. That's really handy. Yeah.
So although they're the state comments in your code, it doesn't affect the way your code runs within your visual studio editor, you can, they just stand out a little bit more. And another thing is when you comment out an existing comment, right? So like, yeah, it's like the other double slash to write comment, a single line comment. If you then put another double slash in front of that, so you end up with four slashes, it actually strikes out your comment as well.
So it's like, you can comment out your comments. It's a bit of a strange concept, but it's quite handy as well to have that. And then because you've got all these different types of comments, then you can search by those as well. Right.
So you can just sort of search your whole project for the word to do and bring up a list of all the outstanding to do items within your code, which are obviously within your comments. So yeah, better comments. Good one. Very handy that one.
I think the formatting side, when I'm looking in other people's code, other files and things like that, the first thing I do check out are the comments. And usually when they grade out, it's really difficult to kind of, you know, go through it. I think with the color coding, I'll just open it up and browse it. It doesn't really, really have it handy.
It depends on your, obviously your theme, your editor's theme and the language that you're writing in, because some languages do color their code quite a lot anyway. Yeah. But for something like, say, I know, CSS where CSS doesn't generally have that many colors in the code, it only has like three or four, when you've got these sort of bright orange comments and bright blue comments, you can really make them stand out. You're just having a look at the languages that it's supporting its Yeah, supports everything.
I mean, there's probably some weird, weird, like offshoot of some sort of language that's not supported, but all the big ones are there. All the standard ones. So yeah, that's good. All right.
Number two. Moving on to number two. So this one's probably, you know, I don't think a lot of people would agree with this one. I think it depends on what frameworks you're working with, but in HTML, a mine number two is Bootstrap for Sniffits.
I work with Bootstrap quite a lot with websites, generally just creating page templates and custom templates that I need. I'm using Bootstrap for a lot of the time. And before I was having to refer to Bootstrap for their codecs and just go through their pages and find the class names or the little features that I'm required to get something working. So I can accord you in a slider and things like that.
So even buttons and stuff. So this extension just chucks the Sniffit feature in there and it will auto detect what you're trying to type and I'll wait for it to look for from the Bootstrap code. And it just saves a hell of a lot of time and hassle. And I swear by if you're a Bootstrap developer out there, if you use Bootstrap on your websites, I highly recommend you use Bootstrap or Sniffits in VS code.
It's just a life saving extension. Are you fully over to Bootstrap for now? Do you not use Bootstrap 3 on any of your website? No, everything's I've migrated everything over.
So anything that was on Bootstrap 3, I've actually gone in. There were small sites anyway. They've just been like, you know, overhauled and got Bootstrap 4 on everything now. And the WordPress theme that I use, it's called Bootstrap now I'm a starter.
And that's a Bootstrap 4 theme anyway. So that's being used in all the websites that I'm running out. Okay. Yeah.
Just on the side now, what's the upgrade process like from Bootstrap 3 to 4? I don't know what the right process is, but I just literally, you know, it was a case of there was about four or five of these websites and very small sites. And luckily for me, they were, you know, they were using a theme in WordPress, which was using Bootstrap 3. And for me, it was just a case of just installing the new Bootstrap 4 theme, creating a child of it locally first and just trying to see if that kind of, you know, worked seamlessly.
There were a few issues, but you know, it was just a case of just, you know, a few minor fixes here and there probably didn't take mind or longer than an hour, to be honest. But I don't know for anyone who's gone on a hard code either, you know, Bootstrap 3 in websites, you know, there's probably some documentation on it on the Bootstrap website. But yeah, for me, it was just a case of just installing anything. All right.
Well, my number two is on the same vein as yours. It's also about snippets. So that's actually called a JS space, a JSX snippets. So JS and JSX snippets.
And yeah, basically I use this pretty much every day. It's got a lot of prebuilt snippets for React. So that's where I use it the most. So let's say you're creating a new class component instead of writing, you know, import react from React and so forth.
I can just basically type in RCC. So react class component RCC and then hit the tab. And that gives you the whole sort of React class component structure. And it automatically puts the cursor into the component name so that you can just give it edit the name straight away.
And then, and then hit tab again, and then it moves the cursor into the actual component body as well. So it's just very clean. It's got a user for the class components for the stateless components to create the constructor in a class component. So basically anything react based, you know, it automatically updates your class when using the class keyword, it updates that class name and then just little things like that.
And then some of the JavaScript is ones as well. So if you're doing like a document dot get ready document, yeah, let's go over and remember what it says because I hardly ever type it now. I think you just type in doc and it comes up as one of the, or you know, you type in ready, I think, just the snippet for that is just having ready in a job function, or you can type in like, I E, E, I E, if I E F, I can give that immediately invoked from I if fee. Yeah, if fee.
So you type up like I if and it gives you the snippet for that. So it opens up a function expression with, you know, and then you hit tab and it puts the cursor in the right place. So yeah, just really good, really well thought out snippets. They've all got, you know, the placeholders will set up and the tabs or work nicely.
There's a couple of places like this, in particular, the sort of stateless function, stateless component, React, stateless component, when you hit tab, it doesn't ever, it doesn't tab into your sort of component arguments that will await where you need to import your props. It doesn't tab into there. So you'd have to go manually move your mouse into there anyway. But I reckon I could probably pack it and add that in if I wanted to.
But yeah, just massively speeds up, React development. That is pretty cool. And the fact that it works, you know, you've got the JavaScript there as well. I think that's very handy.
And this might end up rehauling my whole top five now, because this is probably something I need to look into, especially with the JavaScript. Yeah, so it works with JavaScript, TypeScript and React and TypeScript React as well. But this is for loads of little ones, like for example, you can find some examples, there's loads of React ones. There's loads regarding like prop types for React.
So you can just type in like PTA and that equates to prop types.array, for example, if you've got an array prop type. And then just general sort of basic ones like Cm will give you a comment block within a JavaScript, so like a proper JavaScript, comment block with parameters and all sorts of things. It gives you one of those. Just typing in iMP gives you an import statement, so it lets you import and then you put in your path and then you tab to what you're defiling or importing.
So there's loads. Yeah, there's some really good ones. Okay, here we are. Number one spot.
So my number one is IntelliSense for CSS class names. Bit of a bit of a mouthful there. But you'll find a lot of IntelliSense extensions on the marketplace for the years code. I just find this one just so helpful and so helpful.
And I'm using all the time because I'm writing CSS for every single project I'm working on. So it's just so handy to have also completion with CSS class definitions in your workspace within VS Code. So if I was to just drag and drop a folder into VS Code, it will automatically pull all my definitions from any folders that contain CSS files. And yeah, it will just help me to write my code much cleaner, much faster.
And you've got the override feature as well. So there's certain folders which contain CSS, which you don't want it to actually go into and find any kind of definitions and things. Then you can always tell it to not look into those folders. So it's just brilliant.
And it's going to be hard to top this one. But I think you've mentioned a couple of new ones where I think they could come close. But for me, this is an Obrina. Okay, well, this doesn't necessarily have to be in a favorite to least favorite order.
These are just our top five users ones. So we can put a disclaimer on there in no particular order. So it's basically draws through any classes that you've added to your HTML and Autos suggest those that we're doing. Yeah, that's it.
So what it will do, it will look in your CSS folder and any CSS files that you've got. And so when you're writing your HTML and you're pulling a class, yeah, it'll basically just pull out all the ones you've mentioned. And then you just hit enter on the one that you want. And it just starts to, you know, it's just very easy to write your code.
Okay. Okay. Create and do some things like that. Yeah.
Does it, do you know if it works in reverse? So suppose you've got some HTML with some classes defined on it. Yeah. And then you go and write your CSS afterwards.
Does it in any way of like bringing up what those classes are? That'd be an interesting one. I'll check that one out. That's very interesting.
I think it might. I think it might. I'll have a look at that. Yeah.
I'll check that one out. Because that could work then. If you've inherited some markup and you had to go and write the CSS for it, instead of you trolling through the whole markup to see what classes are used, you could potentially just, you know, start bringing those up with IntelliSense. Yeah.
It's got manual recaching in there as well. So if anything has changed in your definitions, you can, you know, you know, manually recache it and then it will just, you know, auto populate anything that's been updated and amended. Okay. Is there any sort of loading time of your project that's affected by this?
Not really. I haven't noticed anything. I suppose it depends on the size of your CSS files, but yeah, if you've got huge files in, maybe. Yeah.
All right. Well, my number one spot, I actually had pretty, but because we've already spoken about it, I haven't really got anything else added other than go and check it out because it's brilliant and it deserves to be at number one. It just, you know, it takes a bit of configuration and it might feel a bit alienate at first because, you know, you might not necessarily agree with all of its, it's like formatting options. And there's a few that I don't agree with, but it's easy to get around them.
You can look at that. You can customize all of the properties in there as well. But what I've done is I've just gone and added a sort of bonus number one spot as well for another one that I use all the time every day. It's not essentially that important, but it just, it just makes it very, very easy in an agency environment, especially.
So the extension is called project manager. And basically what it does is if you're using VS code for all of your different projects, you can just basically save a, I think it saves as a JSON file in your, in your like dev directory. Yeah. It just saves the JSON file with the paths to all of your different projects that you've got.
And then when you want to, if you're working on a project and you quickly want to switch to the context of another one, you just hold a command chiff P or control chiff P and you just type in actually, no, it's command alt P and just, it brings up a list of all your projects and then you can just quickly just scroll through or start typing the name. So like in my list, I've got so 15 or so different projects for the different clients that I work on. Some of those are personal projects. Some of those are actual work related ones.
Some of them are just like hacking when I'm just testing things out. And yeah, anytime I start a new project in VS code, I'll always go and save that project path to my project manager first. And then yeah, we've always got kick access to it. So that's my sort of bonus number one spot.
And then that's it. That's the top 10. But obviously we did, you know, we picked out a couple of bonus ones as well. So I'm on top of what I managed.
So do you want to go for your bonus one first? Yeah. So my bonus one I've got is a Quaker. It's QU, KK8.
And again, I found this recently when I found out that we were going to be talking about VS code extensions. This, this is sort of like popped up and it's very handy and allows you to test your JavaScript within VS code. I am new to it. But just from the recent usage on it, it's like a significantly very handy.
I can see myself using this a lot more than loading up dev tools and typing in JavaScript and the console and things like that. So what's been reading up on the actual extension? And yeah, there's a lot in there. There's a lot.
So that's the my bonus one, Quaker. All right. Cool. Yeah.
I've looked at Quaker before. I think they've got web interfaces, which have looked at. But it's not something that I've used in any sort of production. Sorry, anyway.
Right. My bonus one is, well, it's not really any, it's not really any already used, to be honest. But if you've ever been on Twitter or something like that, and you've seen these nice screenshots of people sharing the code, chances are it's created with this extension called Polar Code, which is like Polaroid for code. And what it does is you install the extension and then when you run it, it basically opens up another tab in Visual Studio VS code.
And it gives you a little text sensor in that tab and you're pasting your code and then there's a little camera icon at the bottom. And then it basically just generates a nice looking screenshot of your code. Wow. How cool is that?
I'm just watching the demo. Yeah. It gives you all looks like a browser window. It strips away all the extra Chrome that you don't need strips away line numbers.
But what it does do is it does match your editor theme as well. So if you've got a light theme, you're going to get a light themed screenshot and the screenshots it gives you are PNGs on transparent backgrounds and they have like a bit of a drop shadow behind them as well. So if you're then going to drop that into a presentation or something, it does stand out for the page. It looks quite nice.
And yeah, if you've ever seen like, you know, nice screenshots of code on Twitter, chances are they've come from this plugin. So yeah, I don't use it very often. But it's nice. It's just a nice way to share code if you rather than, you know, so that's pretty cool.
Because I've seen this. I've seen some people on Instagram who follow my page on there with these guys got nothing but code screenshots on there. And I'm like, how on earth have you got it? So crisp?
And you know, I was like, yeah, because the alternative would be, you know, to increase your font size maybe and then take a screenshot, open that info shop, you know, delete out the phone the line numbers and then, you know, crop that window and put into a different sort of frame, you know, sort of minimal frame. So it's a lot of hard work. Exactly. And then yeah, this just makes it really nice and simple.
So yeah, that's your bonus one. So I'm going to install that. I'm impressed. Nice.
All right, cool. So that's the extension. So portion. I figured we could just talk about your actual theme as well.
You've got any customizations on your actual workspace and what font using what theme using or anything else. Yeah, I think when it comes to the font, I think they're both using the same fonts, not either. Fear of code. It's like the cleanest one out there.
I think everyone's using that to be honest. Yeah, I've actually already switched to a recent fear of code. I used to use, I used to use an operator mono, which is nice. It gives you like, it's got some nice italics in operation.
It's got like a cursive italics. Yeah. And just generally it's a quite clean font. But you know, a lot of people that work as well, they were talking about fear of code and the way it's got the literature's and, you know, you get your nice looking fat arrows and you're nice looking, you know, double equals and triple equals and stuff like that.
So it looks cool. So yeah, I never thought I'd see the day developers would be having issues about the font that's been used for later. Well, if you're going to be staring at this font and, you know, for the best part of six, seven hours a day, you want something that looks nice and yeah, it doesn't. True.
I mean, you can imagine typing code in Comic Sense. Oh, yeah, it still works. Yeah, I'll take it. You've got a dark theme as well.
Members, people. Yeah, I've got, so I find myself switching between Dracula and the Atom One dark theme. Right. They're both really cool one.
In the Atom One dark theme, I tend to use a dark sort of like brown background. I do like that. And it's just weird because sometimes I tend to switch and then I just want to go to the Dracula theme, which just has like a, it's not really black background, but it is dark. So I find myself switching between the two and it just helps my eyes as well when I'm helping to focus on the code.
That's me. That's the way I work on it. Yeah, switching between those two. Yeah, sure.
I'm using the material darker. So material theme comes with a few different flavors. It's got like dark darker dark light lighter. So I'm using the darker version, but I've added a couple of customizations to it because I have the terminal open within VS code as well.
By default, the dark, the material theme, the terminal is the same color background color as the rest of the actual coding environment. So I just, yeah, I just go and tweet some of the preferences to make that a little bit darker. So I made that darker. I made some of the borders between the panels of chains of colors of some of those.
But yeah, pretty much just straight out of the box using material darker. It's quite a nice one. Yeah, I think these ones are pretty good out of the box. I don't think they need too much customization.
I mean, for me, the background does require a change, I think. Yeah, that's just me. That's my preference. Yeah, do you use any light themes ever?
No, last time I used the light theme was when I was coding in Dreamweaver. And that was why. What I found is that if you ever presenting at a conference or a meeting or something like that and using a projector, I found sometimes that a dark theme doesn't show up very well, unless you've got a a very bright projector. So sometimes if I am presenting anything, then I might switch to a light theme then and then I just literally use a material light theme as well, which is kind of almost an invert of what my current theme is.
It just makes it easier to show up on a projector. But then as soon as I'm done, I switch back. All right, brilliant. Well, that's the whole list.
So yeah, all the links for all of these extensions that we mentioned, the fonts, the themes and all the bonus things will all be in the show notes. Show notes, you can find that at inspect.fm and they should show up in your podcast player as well with links. If you like the show, you can leave us a review or rating on Apple Podcasts or within your own podcast player if possible. And the best thing to do if you want to support us is just share it with your friends, let people know about the show and let people know what you think.
Yeah, so any final words? Not really, just top up on your anti-istening device because I've just been hit really badly this day before. Yeah, that's my word for the week. All right, okay, I'll catch you.
Nice one. Bye.