This is my first #100daysofcode challenge(from 21 July 2023 to 28 October 2023) which I completed. In this journey, I have learned a lot of things from HTML to JS and explored hundreds of things like DSA, hackathons, GSoC, and open-source which I learned recently from Contributing to hacktober-feast. Although I made many mistakes too like not tweeting about it every single day on Twitter with #100daysofcode or documenting my everyday journey which I will try to fix in the future. Here, I will share the lessons that I learned during these 100 days of code (), so let's start with a smile...

1. What is Tutorial Hell and How I Quit it?

I was always familiar with this so-called famous scary-looking word Tutorial Hell but wait, is it the name of some kind of bird? absolutely no, Whenever we watch something like any kind of tutorial it generates a false self-confidence in our mind that I watch it fully now I can change the world with this one tutorial I can do anything just give it to me. This is the False sense of achievement that I am talking about. Yes, my friend, I have gone through this even though I know what is Tutorial Hell that's funny I know let's move forward, at this stage I was in my false belief that I was learning CSS but I was learning nothing in reality or you can say that I was learning but very less that y whenever I went to make project that time my mind went completely blank. I wasted a lot of my time on this false belief.

Now come to the second part, This time I started to watch the tutorial, and alongside that, I also tried to write code at the same time. now is the time when I used to say to myself that I quit tutorial hell, now I can do anything just give it to me. with this great thing, there is also one great thing that came to me that's overconfidence which was totally wrong.

Now, it's time to come to the main part how to quit it and what is the right way to do it. let's understand this in simple steps ...

Step 1: Follow any good tutorial with good projects and don't ever think to find any shortcuts like short videos which I have seen many on YouTube and Udemy too. YouTube is already famous for these all things stay away from that, please. Udemy these days too, I have seen some courses of full stack web dev in 65 hrs videos ❌ no one can teach you full stack properly in 65 hours you will just end up wasting your precious time. Only javascript will take 65 hrs if you are willing to do it properly with projects. Coding is not some kind of Pokemon game where you catch a Pokemon then suddenly catch another one and go up like this. come to reality, here you will have to give a proper amount of time to one language and then move wisely to another one. You can take the help of roadmap.sh to see the roadmap for any role you want to pursue and can cover each topic separately with a proper amount of time.

Developer Roadmaps - roadmap.sh | https://roadmap.sh/

Step 2: If you have already watched any tutorial like javascript and done the projects that are part of that tutorial then it is okay, you are in the right direction but it is not only enough to take you away from tutorial hell because thousands of people have already done this. That will not make you out of the crowd. yes, you heard it right. Now, let's see what you have to do to stand out from the crowd. Now it is time for the real things after you watch the tutorial of javascript or any other thing then try to make a clone of something similar to that tutorial like any website with full functionalities in it with the help of javascript. but this time you don't have to watch the tutorial you have to think on your own and implement what you have learned. This is the time when real pain comes into our head and that's the time when we start to learn something in reality. you can make an Apple clone like I did after learning JavaScript if you can able to make it without watching any tutorials then it's fine. If you still have to get help from the tutorial then it's also fine but try to make it on your own first or you can take a little help from the tutorial its okay.

Step 3: If you have already done the above two steps then it's the last stage where you have to make another clone of something upper level of what you have learned but this time you don't have to watch the tutorial instead you can take the help of documentation. if you are able to make it and implement it on your own then you are out of the crowd and out of Tutorial Hell. congratulations to you ......😊 This is how I quit Tutorial Hell.

1. Never try to do or learn multiple things at the same time.

Have you ever tried to learn multiple things and end up being nothing then it's an error. I have always tried to do many things at the same time which is wrong but because of my curiosity to know about everything I always start up doing this and end up being not able to complete anything properly. It is fine to learn one or two things at the same time according to me but not more than that. so, please try to stick to one or max two things at a time.

1. Don't attempt to cram all your studying into one session.

Ever find yourself up late at night expending more energy trying to keep your eyelids open than you are studying? if so, it's time for a change. Successful students typically space their work out over shorter periods of time and rarely try to cram all of their studying into just one or two sessions. if you want to become a successful student then you need to learn to be consistent in your study and to have regular, yet shorter, study periods. I believe in hard work but now I believe in consistency more than hard work.

1. Give your brain and body a break.

If we don't take breaks then I don't think that our brains will be able to save our progress effectively. hey, I remember a guy who used to say Programming is a marathon, not a sprint. yes, you are right he is Leon (100devs). so, taking a short break is the best thing you ever do. plus, you will come back fresh and will be excited for the new challenges. You can also do whatever you like in this short break like playing games which I like the most, watching anime or the best you can do is write blogs. Take a break otherwise, you will face burnout or you will hate what you do and in the worst case scenario, you will fall sick.

1. Making Notes for Yourself

It helps me a lot whenever I forget about something or am stuck somewhere that I learned then I don't have to go, search, and watch a complete tutorial because I have my notes. At the start, I also thought that making notes was just a waste of time but then suddenly I realized my problems about forgetting things that I had learned recently. it also helps to track down what you have learned recently. you can also use some note-taking apps which I don't really like, I always preferred git & GitHub over all note-taking apps. I also don't like to make notes on paper, I tried it some days but it was too overwhelming for me to manage it and I quit later when I realized GitHub works better for me I just threw my pen and paper. As you know, documentation is also an important part of software engineering as well as notes. This was my personal preference, you can do it according to what you like.