The real reason you're stuck in "tutorial hell" (it's not motivation)
Spent a lot of time watching devs stall out at the exact same spot: they can follow a tutorial line-by-line, but freeze the second the tutorial ends and it's just them and a blank file.
Here's the actual problem — tutorials teach you syntax, not decisions. You've memorized what a for-loop looks like, but you've never had to decide when to use one instead of a list comprehension, or why your API should return a 422 instead of a 400.
Three things that actually move the needle if you're stuck:
Stop finishing tutorials, start breaking them. Take any tutorial project and rip out a core feature, then rebuild it without looking at the solution. That struggle is where the actual learning happens.
Ship something that can fail in production. A script on your laptop can't teach you what a deployed API with real users can. Deploy early, even if it's ugly.
Get a feedback loop that isn't a YouTube comment section. The single biggest unlock for most self-taught devs is a room full of people slightly ahead of them who will actually review their code and call out bad patterns.
Curious what's actually kept people stuck longest — was it a specific concept (OOP, async, testing), or more the "I don't know what to build" problem? Drop it below.