React devs probably have a moment when react suddenly makes sense.
In all four cases (bicycling, music, pointers, react) what makes the difference is dogged persistence. One day you'll wake up and things will seem simple -- and the next challenge impossible. Rise and repeat.
It wasn't literally sudden, more so a realization over the course of an hour after the usual reading and re-reading of various tutorials and documentation that I had already been doing. I'd say a few hours into programmer flow was when it all came together.
I liken it to when I first grokked Lisp back in high school. A shedding of mental fog leading to a sort of "now I finally get how somebody could program a game in this without being some hack-the-planet-level computer whiz."
Strangely enough, I don't think I do. There was a spectrum where I didn't get pointers, I thought I sorta got pointers, I thought I got pointers, I thought I get nothing, and over time I got a bit better at understanding pointers thanks to C++ and Rust. Definitely more of a continuum.
I did have a lightbulb moment for understanding recursion, though, thanks to an assembly course.
She mentioned the other day that she's a bit sad she can't find any aspect of React she doesn't know. But now she's been banging her head against react native for the past few months, so there's no shortage of challenges. She's the primary architect of a startup's frontend webapp (and now their mobile app). I keep trying to push her to write and post her stuff, but she still feels like she doesn't know anything. But that feeling seems like the main reason she knows so much now, several years later.
I would like to add as well, as a career move, total slam dunk.