People like to praise the value of tutorials. "There's so much you can learn on Youtube!" Tutorials are helpful for simple topics, for sure, but not so helpful for complex topics like computer programming and VFX.
People get stuck in "Tutorial Hell" where they watch tutorials for years but make little progress. They blindly copy what the tutorial did, like paint by numbers. They get lost when doing their own projects, because they don't have a solid core foundation. Tutorials are also misleading because what worked in their context may not work in the context of what you are doing in your project. Plus, if you rely on tutorials, what happens when there are no tutorials because you're doing something almost nobody has done before?
A better approach is project-based learning.
Do not start with big projects. Don't bite off more than you can chew. Start small and simple, do a bunch of projects where you learn a thing or two with each project, and gradually work up the complexity of projects. Your répertoire of base knowledge is built brick-by-brick.
Read the documentation first. Nobody reads the manual, but you need to. Documentation largely negates the need for tutorials and you will run into less problems.
I do not watch tutorials, except when coming across a tutorial while hunting for an answer to a specific task or problem, and only a small snippet of the tutorial will be relevant.
Tutorials can have value to see how someone else did something, but for that you need to already know what you are doing.
People get stuck in "Tutorial Hell" where they watch tutorials for years but make little progress. They blindly copy what the tutorial did, like paint by numbers. They get lost when doing their own projects, because they don't have a solid core foundation. Tutorials are also misleading because what worked in their context may not work in the context of what you are doing in your project. Plus, if you rely on tutorials, what happens when there are no tutorials because you're doing something almost nobody has done before?
A better approach is project-based learning.
Do not start with big projects. Don't bite off more than you can chew. Start small and simple, do a bunch of projects where you learn a thing or two with each project, and gradually work up the complexity of projects. Your répertoire of base knowledge is built brick-by-brick.
Read the documentation first. Nobody reads the manual, but you need to. Documentation largely negates the need for tutorials and you will run into less problems.
I do not watch tutorials, except when coming across a tutorial while hunting for an answer to a specific task or problem, and only a small snippet of the tutorial will be relevant.
Tutorials can have value to see how someone else did something, but for that you need to already know what you are doing.
