1. The Problem - Being Stuck in The Tutorial Hell
I remember when I was learning to code, I learnt the basics of web development includi...
For further actions, you may consider blocking this person and/or reporting abuse
Moving from theory to practice quickly is very important to break out of "tutorial hell", I totally agree. But after a practical crash course like suggested in your post (as you wrote, do this for about 9 months!) or better yet, starting in parallel:
I agree💯
There is always room for growth. Thank you!
Nice post 🙏. Small thing: depending on your goals, you may not need to do full stack : either front or back should be enough. Otherwise you will have shallow knowledge in both. It’s super hard to be a very good full stack dev
True, but I still recommend doing a fullstack project then choosing what to focus on more from there. You will know which one you liked most and you will have an idea of what happens on the other side when you start collaborating in teams.
If that is for choosing between the two, I definitely agree !
Like I can create a Fullstack app but I know my strong part is on the frontend, so usually when looking for freelance work and jobs, I usually go for frontend. But I have ideas of what happens on the api/database side which makes working with example data and intergrating later with the actual apis when they are ready easier.
I think backend devs should also have a clue of what happens on the frontend as well.
I could never follow programming tutorials unless it was something like algorithms or data structures. The way I learn any language/framework/stack is by picking an idea that resonates with me, deciding what technology I want to use/learn and just jumping straight into it. It's a bumpy road at times, but much more fun and motivating because it gives you a sense of ownership and constant dopamine hits from seeing little parts working and coming together. Then one day you look at the path you've taken and realize that you now feel comfortable with what you've been learning and can use it comfortably, even for professional work.
This is a very good path, just jumping right in is one of the best way.
But for a complete beginner they might find it hard because they might not know anything about coding, including the various tech options available or even on how to open a code editor. That's why I think a few tutorials at the beginning could become handy but someone should try to move away quickly from them.
You know, every single word you said here is true!!! If I had started projects first, I would've learned faster. Unfortunately when I attended a one-year coding school, they did not tell us anything about doing projects, or creating a portfolio. So it took me another year to develop JavaScript projects together with a portfolio and websites i had created, along with some other stuff I also do, like Graphic Design. So if anyone out there is starting a coding school, start doing projects, prepare a portfolio... move on. I had to learn everything all by myself, and thanks to all of you who talk about this all the time, or else I would've never have known. It's important to follow a DEV Community🩷🩷🩷🩷
Thank you for adding the emphasis, I also spent my first two years learning but couldn't create a project. I started in 2016 but created my first complete website in 2018. I think starting early with projects is the best.
Definitely.... hope many are reading this, so they don't make our same mistakes!!! Start creating projects immediately everyone!!!! 🩵🩵🩵🩵🩵🩵
Diving into coding challenges and crafting my own projects made a massive impact on my learning path. It turned out to be incredibly efficient since I could put theory into practice and sharpen my knack for solving problems—a true game changer in mastering programming concepts.
I can add this page also to find more learning projects aquadzn.github.io/learn-x-by-doing-y/
Awesome, combining coding challenges and crafting projects is really a good take. Coding challenges are also the best when it comes to interview preparations.
Another side of Tutorial Hell is just feeling like there's always more tutorials that you should be doing or that you think you aren't doing the right tutorials and you end up with a million different tutorials bookmarked! That's my kind of tutorial hell.
well, creating projects will help you know what you are missing and be able to look for the right tutorials.. so just start working on projects
Developing fast and scalable applications is a crucial aspect of web development. As your app expands, you and your engineering team will not want to rewrite the code to accommodate scalability.
To build complex functionality, it is best not to rely on resources that require a lot of time and effort. That's why we at ApyHub have created a catalog of pre-built services for developers. - to help them build applications faster, cheaper, and more scalable.
This is a good article!
I would like to recommend something though, and that is not to start with MERN.
Simply because in the real world: data is complex, most companies will use relational databases like PostgreSQL, MySQL, SQL Server, or Oracle. Most web apps are built using SQL relational databases.
NoSQL is good for time series and log-type data, but when you need to do complex reports - it is a pain and hard to work with. Rather learn SQL first, then learn NoSQL later.
Good advice, thank you for this!
This is really a timely topic. I've encountered a similar issue, and your solution really helped me understand the situation.
Great, start creating projects sooner
I liked it.
Thank you for sharing !!
Awesome, glad you liked it 😊
Great article. thank you so much for break it down for us.
No problem mate!