Venturing into the world of full stack web development (Part 4)

 How to learn it

For those who have taken their time to read the first four parts of this article, you can proceed. For those who haven't, I suggest you go back and read them before proceeding.

Now that we have an idea of what full-stack web development is and what we should learn, it's time to delve into how to learn it. It's important to note that while the knowledge is available, full-stack web development is not a cheap venture. Think about it: if you had valuable information, would you give it away freely?

One thing you need to know is that learning tech isn't cheap or free. Even with a free course, you'll need data to access the internet and take them, so it requires money. But trust me, no matter how little you have, you can go far in tech if you have the drive.

Now, let's dive into how you'll learn:

Tech doesn't spoon-feed its students. If you want to learn, you need to do a lot of research and constant practice, as this experience will shape your job readiness.

First, research what field of programming you want to venture into. Since this piece talks about web development, I'll assume you've chosen that, hence reading this article.

Second, look for a course. If possible, consider paid courses. Not saying free courses won't do good, but trust me, paid courses are often better. However, if this is your first programming course, start with a free one. If you pick a language you don't like and pay for the course, you can't get your money back. So, test the waters with a free course to see if you'll love it before fully committing. This way, you'll have a better understanding before paying for anything.

Next, figure out what type of learner you are: visual or auditory. I met someone at the beginning of my journey who claimed he learned programming by reading a book, so I tried it. After reading an entire book, I was more confused than when I started! Funny, isn't it? Eventually, I started using videos and audiovisual materials, and I saw progress. Later, I went to a tech guy for my first physical classes, which gave me a better insight into programming and helped shape things. Figure out your learning style and get those materials.

NOTE: No matter your learning style, thanks to Indians, YOUTUBE must be your best friend. Thank you, INDIA... lol!

Next, get a mentor in your field. No matter how committed you are, you'll get less results without one. You might spend years learning things you should have mastered in months and still make no progress. When I decided to go into tech, I started alone. After 3-5 years, I wasn't progressing and almost gave up, thinking I needed millions for a course. I kept pushing with little progress, even when someone offering a job needed proof of my skills. I was just too low in knowledge. Then, in university, a lecturer offered free Laravel training during a strike. By the second month, I was the only remaining student out of 30. He decided to mentor me. Fast forward to the following year, he got me an internship with his company. What I learned in 5 months was more than what I'd tried to do for 6 years! Between the internship and 8 months later, I started and finished 5 websites by myself. While they were done as final year projects and never deployed, they proved my ability to handle a project and opened doors for job opportunities. So, get a mentor and avoid going in circles.

Next, PRACTICE. You haven't learned anything if you haven't practiced it. Even when it seems like you haven't made much progress, keep practicing. Once you stop practicing, you stop learning. I repeat "PRACTICE" because it's as important as, if not more important than, any learning material! Practice until you can't practice anymore, and then practice some more. By "PRACTICE," I mean implementing what you've learned repeatedly until you can do it in your sleep.

NOTE: Practicing will be difficult at first. It might feel like the more you do, the less you see. But as time goes on, you'll make mistakes, realize them, solve them, and gain valuable knowledge from that experience.

Finally, work on real-life projects, no matter how small. My first project was a basic and functional CGPA calculator with a messy frontend because I focused more on improving my backend skills. This project was before my mentorship, but I still have it and use it.

I hope I've given you a workable and simple guide to productive learning. In the final part of this series, we will be finding out where to learn. Stay tuned!!!