Do Not Learn Frameworks – Learn the Architecture
The author is only partway through the learning process. There is a circular progression.<p>The total newbie just "learns the framework" and is helpless to debug through leaking abstractions. I agree 100% that you don't want to be stuck there.<p>So eventually she decides to just compose her own architecture. Now she understands all the pieces. But as she matures further as a programmer and architect, she starts to see all the myriad ways that her bespoke architecture is not as good as the more standardized alternatives.<p><i>It can't be</i>, because all the people spending their time on bespoke solutions are solving the same problems over and over again separately, whereas the people working on shared solutions keep building off each other. Over the long-run it gives a massive quality advantage to the shared solutions.<p>Her journey is complete when she circles back around and can pick up somebody else's framework with shared community conventions <i>and still understand all the pieces</i>. She's not intimidated by the prospect of debugging down through layers of abstraction. Because she's good enough to write a framework, <i>she doesn't have to</i>. She can just contribute to one, and benefit from everybody else who's also contributing.