Robert Ta explains how to use Claude Code as a teacher rather than a tool. Ask it to explain its reasoning on complex code instead of relying on tutorials, and request three different implementation options with their trade-offs. Real projects, not generic lessons, teach you fastest.
Not to flex, but I'm pretty fucking good at using Claude Code. If I had to wake up tomorrow and master AI-native development from scratch, this is what I'd do. When Claude does something complex, don't just move on. Ask it to explain why. I had to refactor a massive frontend file recently for the website. I didn't quite get the logic at all, so I paused. I asked, and the response came back, and it taught me more than all of the trash YouTube tutorials on Claude Code would ever do because it was explaining using my code, not some generic example. Second, never just accept one solution. I always ask, show me 3 different ways you might do this and the architectural tradeoffs. I did this for an automated landing page where I'm trying to automate CRO and learn more about front-end architecture in those 5 minutes than weeks in some classroom. Your project is the classroom. Maria Montessori said this in 1907. We learn fastest when working on things that actually matter to us. Today, the terminal is the instrument of your mind. Now go ask Claude Cohn why.
