A tutorial usually has a known destination and a guide who already understands every step. Real software work is different. Requirements change, bugs appear, libraries conflict, and there may be several reasonable ways to solve the same problem.
Students grow when they have to navigate those decisions themselves. A project can expose weaknesses in planning, debugging, version control, documentation, testing, and deployment that are invisible while following a lesson.
The objective is not to reject tutorials. They are useful learning tools. The problem begins when a student confuses completing tutorials with being ready to deliver software independently.
A balanced path uses courses to learn concepts and projects to prove that those concepts can be applied.