How I Actually Learn New Skills (No Tutorial Required)

I used to think learning meant reading, watching, absorbing. Now I think learning mostly means breaking things and finding out why.

The loop that actually works for me: learn → attempt → debug → understand → ship → reflect. Not learn → learn → learn → maybe someday attempt. The tutorial-first approach always left me with a weird kind of knowledge — I could follow along, but I couldn't tell you why any of it worked, and the second something didn't match the tutorial exactly, I was stuck. What actually sticks is trying something, watching it fail in a specific way, and having to figure out why that specific failure happened. That's not a bug in the learning process — that's the whole mechanism.

And I write things down — publicly, even the messy parts. That's basically the whole premise of my open learning notebook: field notes, half-formed thoughts, and the connections I'm making as I go, with no curriculum behind any of it. Writing something out is often the moment I actually understand it, not just the moment I record that I understand it — and keeping that record public means I can't quietly pretend I learned something faster or cleaner than I actually did.

And I've stopped trying to impose order on top of that. No color-coded study plans, no structured syllabus. Just: what's the smallest next thing I can actually attempt today? Small concrete next actions beat ambitious productivity systems every time, because the systems are things you plan and the actions are things you actually do.

Consistency over intensity. I used to swing between all-or-nothing — a manic week of nonstop learning followed by weeks of nothing, restarting from scratch each time. What works better is showing up smaller, more often, and not breaking the thread. Leaving myself breadcrumbs. Picking up exactly where I left off instead of re-deciding where to start every single time.

I want to understand the "why," not just get a working answer. This matters a lot right now because I use AI a lot in my own development work — and it would be very easy to let it just hand me finished code. But that's not the point for me. I want to come out the other side of a problem actually more capable than I went in, not just holding a solution I can't explain. AI as a pair, not a replacement — something that helps me think through the architecture and tradeoffs, not something that thinks for me.

None of this is a system you can buy or a framework with a name. It's just what's actually true about how my brain learns, after paying attention to it for a while instead of trying to force myself into someone else's method.