When you don’t know where to start

Key Takeaways

hello my friend and friends and welcome to my podcast General musings my name is Kevin and this podcast is the audio version of my weekly Sunday newsletter where I generally talk about whatever is front of mine for me in any given week as well as share some sites or fun resources that I've come across in the past week and anything that I might have been up to as well this week we're going to be talking about how understanding something isn't the same as knowing how to do that thing and while that might seem obvious when I say it like that this is a problem that a lot of people run into when they're learning and especially when it's code related for example let's say you're starting to learn and you've gotten past the very Basics and now you want to learn how to make a to-do app so you're not really sure how to make one or how to get started so you go and find a tutorial on how to do it and you will follow along with that tutorial and everything goes really smoothly or maybe you do run into you know a hiccup here or there but you refer ref back to the tutorial you find a little typo that you might have made where you know it was causing something not to work and you realized how to fix it and everything works as intended after that now you repeat this process a few different times building different things by following different tutorials or courses that you're finding and then eventually you have an idea for something that just pops into your head and it's a cool little project a fun idea that you'd like to build so you fire up VSS code and then you just have no idea idea what to do the empty editor is just staring at you that carrot is blinking away sort of taunting you with the empty editor and you're just staring right back at it and you start wondering how is this possible I've made a bunch of projects now I should know what to do now for some of you listening to this you've already gone through this and luckily you've moved past it but you understand the struggle that I'm talking about other people listening to this are going through these struggles right now and you're I understand if you're there right now you're probably very infuriated but I have some tips to help you out and of course some of you might not have gone through this yet because it will happen and I know it will because this happens to everybody at some point it can be infuriating but it happens for a good reason which is when we understand how something works we often think that that means we know how to do it ourselves but that's not actually true and it's also a very easy trap to fall into especially when it comes to writing code and that's because often when we're doing coding based stuff we can follow the tutorial we understand all the different things going on we can open up some code and read it and understand what that code is actually doing but being able to follow along line by line and understand each one of those lines or to open up somebody else's code and look at it and understand what it's doing that is very different from being able to code it on your own it's a little bit easier to understand this concept if we switch to something completely different from code though like doing backflip and that might seem like a weird jump to take pun intended uh but we can watch someone do a standing back flip and while we might be wildly impressed by seeing them do that standing backflip we probably have an idea of how they did that right they jump really high into the air they're throwing their weight backwards probably using their arms like for momentum and everything and as long as they've managed to rotate enough they land on their feet now you're super impressed by that and now you want to learn how to do one yourself you can find tutal for that Linked In the description to this to a short it's 60 seconds long and it covers all the steps to learn how to do a standing backflip and they do a really nice job of explaining how to do a standing back flip so if you did have that opportunity to go and watch it or even if you didn't that's okay but let's pretend you did and there was five steps total in their video and if you watched the whole thing over that 60 seconds and came right back I'd like you to try and think about what those five steps were again now I've only watched the video Once and if I had to remember what those five steps were I know the first one involved sort of planting your hand in the ground and sort of maybe doing some weird movement I think there was another step that involved a more of a cartwheel instead of the hand plant I guess cartwheels involve hand plants but it was kind of different I know one of the steps I think it was the fourth one was just jumping as high as you can possibly jump to get better at jumping So eventually you could get into the backflip so I sort of know what they talked about but I'd also have to watch it again probably a lot of times if I was actually going to attempt to learn how to do a standing backflip and actually if I was going to try and do one or learn how to do one I'd probably watch just one step at a time I would see what their step one was I'd pause it and then I would practice those motions over and over again because that's sort of the idea of that tutorial is here's the first thing you should get good at you should practice that a lot and then you can go on to step two now i' do that I would pause at each single step along the way and I'd practice it and do it over and over again even though I understood what all of the steps were I understand what they're teaching me on that first viewing I understand the Motions they're doing I understand any terms they might be showing you know all the different things that they're showing me how to do I understand but that doesn't mean I can do any of them without practicing them over and over and over again until I can get them right and one thing I definitely wouldn't do is do each one of those steps one time and then just move on to the next one if I did that I just went step one one time step two one time step three one time and just went through all the Motions for each one one time only then when I got to the last step which is actually doing the backflip I'd probably land on my face and really hurt myself which even granted if I were to practice all of the other steps before that I might hurt myself as well but at least I'd be giving myself a fighting chance to be able to land one and obviously in in coding we don't so much land flat on our face but that's sort of the same thing as instead of hurting ourselves were stuck there staring at the blank editor with the carrot taunting us as it blinks away on an empty page when we follow a tutorial or a lesson or anything like that and we're just going through each one of the steps which is you know writing each one of those lines of code one by one along with somebody showing us exactly what letter to write for everything we're not learning how to do that thing we're just learning all of the little steps that we need to be able to do to accomplish the final result and we're going through each one of them one time to get there now that we know what all of those steps are because we followed the tutorial well now we need to actually practice them and the big difference between learning how to do a standing backflip versus coding something is by following each one of the steps one by one to do the standing backflip you're sort of setting yourself up for failure and you probably don't want to do that and you're going to be hesitant to try when it comes to the last step because you know that you probably don't know what you're doing uh whereas with coding we feel like we accomplished something because if we follow each one of the steps that the tutorial is showing us we get the finished product that works in the end and not only that the part that I think throws most people off is you could look at the code that you wrote and you can understand everything about it you could even look at that code a week later and you'd understand it or you could find a to-do app written by somebody else that's kind of similar and you could probably understand that as well and understand all the different pieces that are going on there so all of a sudden you've tricked yourself into thinking you actually know how to do that on your own but reading code that somebody else wrote and understanding it is a lot like watching your good buddy do a backflip he watched the same tutorial as you but it's a week later and all week long he's been practicing and you haven't been and now he can do that standing back flip and you stand there and you nod along and you go yep I know how to do that too well yes you know how he managed to do that but you're not actually able to do it understanding something is not the same as being able to do something we have different stages in learning and the first one is when we gain an understanding of something I can understand what those steps accomplish I can understand everything that's happening but if all you do is follow along line by line with tutorials or even worse just passively watching tutorials you're never going to progress beyond that understanding stage now granted sometimes this is actually why we watch a tutorial right sometimes I don't want to learn how to do a new thing I just want to learn about a new thing I'll see a YouTube tutorial pop up from another channel on something new and I'll open it up and watch it probably at 2x speed just to give myself an idea of what it is this new thing can do right I just want to learn I just want to gain like a general awareness of what that thing actually is and then if a situation ever arises where that could be useful well then I'm going to go and find that tutorial again or I'll go read the documentation and I'll learn how that thing can actually work so then I can implement it where it would be useful for me and that's what we need to do if we want to learn how to do something we have to use it and we have to practice using it and this can start really really simple too you can watch the tutorial like you've been doing but then instead of just moving on to the next tutorial you can delete all the code and start over and just try and recreate it on your own I almost guarantee it you won't be able to and you're going to get stuck on different things but that's completely fine and that's actually a good thing when you're getting stuck because that's how you're going to learn you're going to find the parts where you're not sure what's going on or you're forgot something and there's holes in your knowledge and learning is all about filling in these holes in our knowledge so you get stuck on something you go back to the tutorial you see what it is you forgot put the tutorial back away and then you go and Implement that in your project and then maybe it was a to-do app you made but you had an idea for a better version of the Todo app or an extra feature that you can add and then you try and Implement that in there and you're going to be using a lot of the things that you've learned but now you're using them in slightly different ways and you're going to be learning the entire time that you're doing that because you're applying things without looking at exactly what to write you're trying to remember what you need to do and try remember how different features work and that's sort of the point is you want to get stuck so you know where you need to fill in some knowledge gaps and this is something you're going to do over and over and over again and every time it just helps that knowledge become a little bit more sticky and then eventually you will be able to do it on your own but that's why if you followed along with like 10 different projects and tutorials or courses to like accomplish different things but you never did anything other than just following along line by line through all of those l lessons you have no idea where to start you've had your handheld the entire time and you've never actually had to actively figure out any of the steps on your own you're not relying on the knowledge that you have you're relying on having the code right there for you and so instead of a few small stumbling blocks everything is a stumbling block now right you you haven't been slowly filling in all these knowledge gaps you're just getting to this point of trying to build something on your own and none of that knowledge is there you're you're starting at square one even though you could understand understand what all of that code was that you were doing originally and if this is happening to you it's very important to understand because it's insanely infuriating when it does happen but it's so important to understand that it's very normal and you're definitely able to learn and get past this part but please just don't let looking at some code and understanding what it does Trick you into making you think you understand how to do it by yourself and now Switching gears a little bit we're going to move on to the other awesome stuff from around the web section of this podcast and if you've watched any of my videos you probably know that I like custom properties a lot and I actually have like a numbering system that I use for my colors and my font sizes like 400 is my base and then I go lighter and darker from there and I also like to prefix my custom properties as well so I'll use like forward SL slash you know which we we need for a custom property but we have the forward forward SL and then I'll do like CLR for color or I'll have the F uh FS for font font size or FW for font weight you know just to make it really clear that that's what that thing is for the prefixes help and for me the numbering helps a lot as well and for like simple things like that the naming and the numbering can be pretty straightforward and it just it for me helps a lot with naming things and naming my custom properties because in general as you might know naming stuff is maybe the hardest part of CSS but once you get past those like basic things if you have a robust system in place that has a lot of custom properties being defined it can be hard to come up with good ways to name them and you just start to get a little bit lost sometimes which is where this other stuff from around the web is going where recently Jonathan Dallas uh put out an aptly named article called naming variables in CSS and Jonathan offers up a few suggestions in that article to help with naming and one of them which when I first saw it I said I'm not too sure about this but it's mixing Kebab casing with camel casing but it's actually in a way that I can totally get behind I'd really recommend checking out the article to understand like why mixing the two of them but um it's sort of like the Kebab case is almost like if you're screening together all the prefixes and then you'll get to like you know you might have a color that's not red it's I don't know you have a longer name it's you know cherry red so instead of doing Cherry hyphen red then you use camel case there at the end because it's just a color name or uh this could be for your font sizes of different things or you know heading one and it's like heading Capital One you're writing the whole word one out so the font size might be Kebab case and then you have the camel casing for after that but anyway I would definitely recommend checking out the article to get an idea of what he's suggesting there CU I think he raises a lot of really good points throughout the article and it could really help out if you are ever struggling with naming things especially your custom properties there is one thing though that he mentions in the article when it gets into the World of Color that I actually disagree with the colors in general are a point of contention for a lot of people and I think it often comes down to personal preference and the part that I don't like like is that the way he goes into the naming things relies a lot on knowing the names for different shades of colors for you know for example in it he uses Ferrari red or sunflower yellow to sort of say like that's actually more descriptive than maybe having you know what's a red 300 versus you know a yellow 700 or whatever it might be and I understand that idea and well you know Ferrari red I think most people would know what that name is but another example he uses is bondie blue and he also uses Cadet blue and for those I actually had no idea what to expect and I even Googled the two of them and especially with Cadet blue after Googling it I still have no idea what the color would actually be because the first five results within Google were actually completely different from one another going from something I would consider almost a teal all the way into like a pretty rich just blue and I completely get why he prefers that naming system he's far from alone in preferring to name colors that way I just feel like it leaves things a little bit too abstract in a sense it relies on people's interpretation of what you know what's ocean blue for example there's lots of different colors in the ocean and well we have some color names that definitely I think sky blue more or less most people could agree on it just leaves things up to a lot of interpretation and it also doesn't take into account that a lot of the time English isn't somebody's first language and in those cases there's probably even a bigger chance they have no idea what that color might but just because I don't like what he proposes for how to name colors it doesn't mean that I can't get behind other things that he's saying in the article and I think these days people do that a lot where they see one thing they don't like and they attach themselves to that and what just won't listen to the entire thing I can totally get behind that the camel case and Kebab case mixing thing as I mentioned earlier and I think you know just because I don't like that way of naming colors doesn't mean that you might not get something from that or some other ideas from it as well so so I would definitely recommend checking that out cuz it might give you a better way to name your custom properties and speaking of custom properties I had a video out this week actually where I explored how people don't make the most of them and that's because people set them up often on the route and they just use them throughout their project and yeah that's good I think custom properties are really handy and just for doing that but in the video I explore the idea of using locally scoped custom properties and even that's like building on top of maybe the Global custom properties you have and also how we can sort of bring in this idea of private properties with like this locally scoped ones which is an idea that Lea veru proposed and that I've really gotten behind and it it's a little bit different from how I've used the private property idea before I've went more into how Leia actually proposed it and suggested it within the video if you're using custom properties a lot already but you're not using them locally you're just using them up in the route definitely consider using them locally and if you're not too sure what are you know the best practice for that is or ways that you could actually take advantage of that well you can check out that video that I put out this week I also put out a very beginner friendly video looking at how we can create and style lists with HTML and CSS really going over the basics into you know how we can style the map at images icons and just the spacing between things all of that sort of more beginner friendly stuff uh that you might have with list and I also put out a short this week where I looked at how useful the empty pseudo class can be where I used a Cho app speaking of them where I removed an empty unordered list when the twoo app doesn't have any items in it so the entire list is is taken out of the document so you don't have this thing floating in there that you don't need a lot of the pseudo classes tend to have that one specific purpose for them but it can really come in handy in The Right Use cases and that's it for this week if you'd prefer a written version of this instead of hearing me talk about all of these things the link to my newsletter is in the description as well as links to my socials and every other thing that I've mentioned along the way as well thank you so much for listening and until next time don't forget to make your corner of the internet just a little bit more awesome