I would really recommend updating the estimated time to complete the Full-Stack Engineer course.
For a beginner (and this course is beginner-friendly), I would say it takes at least 300 hours (double the suggested 150 hours) to finish the course. If the student follows all the instructions, completes the extra challenges, and practices the exercises properly, it could take even more time.
It’s quite frustrating to start the course expecting to finish it in 150 hours, only to realize it might take over 300—possibly even 500+ hours.
I’ve already studied for around 80 hours and have completed less than one-third of the course. It’s also clear that the most challenging and time-consuming exercises are still ahead.
But don’t just take my word for it. Consider running a survey with students who have completed at least 25% of the course. Ask them whether 150 hours is a realistic estimate—especially for beginners.
Lastly, this is just a suggestion based on how I’m feeling (frustrated), not a criticism.
150 hours does seem a bit off to me. Everyone learns at their own pace and that note of 150 hours is just an estimate, based on…well, I have no idea how they calculated it. But I’m sure it was based on asking previous students of the course.
I’m sorry you’re feeling frustrated. (If it’s any consolation, everyone does when they’re new to learning to code). Take as long as you need to go through the course to fully understand the concepts and then put them into practice w/projects and seeking out code reviews.
Thanks for your input, I appreciate you taking the time to respond.
However, if the 150-hour estimate was really based on feedback from students — which I honestly doubt — it was probably done before multiple updates and additional modules were included in the course. In my opinion, that estimate only makes sense if the person going through the course already has some experience. For complete beginners, it feels quite unrealistic.
You should make that suggestion when you contact them. They update courses all the time and perhaps it was overlooked to adjust the time it takes to complete.
I feel what you mean as well. I started in Codecademy on October last year, and I completed around 20% of the curriculum and, with the projects and stuff, it took me much more than what it was supposed to.
Because life happens, I had to quit studying and I’m back to it now from the beginning again because I wanted to review everything again. And, even having done it before and just reviewing it, it is taking me longer than the course says it will take for every module.
I did my schedule to work 4 hours every day, 5 days a week for 8 weeks to “complete” the course in the 150 hrs, but I know I will take me longer than that (probably around 12 weeks if not more).
So yeah, I feel your frustration about this matter and it is one of the things I wanted to give them feedback about whenever I get the chance. Specially because the projects are very broad, don’t give you any material and you have to research for them yourself as well. Definitely, I think they should update it and make it more realistic.
Thank you so much for taking the time to share your experience! I totally understand your frustration — it’s really discouraging to plan for 150 hours and then realize that it might not even be half of what’s actually needed. I hope you’re able to complete the course within your planned timeframe, and I’m rooting for you! You’ve got this!
