It depends. What projects did you make, and what were your solutions to the problems?
Did you hack-and-slash your way to passing? Or did you execute a hack so elegant it should be appreciated like fine brandy? There are many ways to solve a problem with code.
There is no simple answer to your question. Virtuosity is one axis. Total person-hours of labor spent is another. Retention percentage is another. However, if you multiply all three, you may get a product that portends the ease with which you will learn more frameworks, languages, and patterns.
Hmm, I was assuming that completing the challenges without cheating and through your own code creation would imply competency and I suppose that’s the level I’m aiming for, competent enough. So I guess that’s how I’m framing the question. How long would it take to finish the challenge assuming that I finish it and become competent enough in the process (basically not just finishing it for the sake of finishing)
The time estimates are just that. Estimates. If you have no prior experience, syntax errors may waste a lot of your time. You could simply divide (300 Hours/ numHoursYouHaveToDedicateToLearningPerDay) and get a result in days, but that means you never “wandered off the path” to tinker around with CSS on W3schools. You never opened up a pen or a fiddle and answered a question you had for yourself. To quote Tolkien, “not all who wander are lost.” You want depth, but also breadth in your learning journey.
that’s a long ass variable right there. That’s a sign you’ve been coding too much, hahaha.
Thanks a lot for this dude. This is the kind of insight that is immensely useful and helps a lot in terms on what to do next and when to know when “next” is. I appreciate the input dude!