People assume I learn fast because I'm smart. I get why — it's the flattering story, and I spent most of my life happy to let it stand. But it's wrong, and the wrong version actually held me back for years. The truth is more boring and more useful: I follow a method. Give me thirty days and a skill I've never touched, and I'll get embarrassingly far up the curve — not because I grind harder than you, but because I refuse to start until I've figured out where everyone else is wasting their time.
So here's the actual thing, the part nobody puts in the motivational montage. There are three moves, in order, and the order is the whole game. Then there's the worldview underneath them that makes a generalist life rational instead of scattered. And then there's the honest counterweight, because I'd rather hand you my flaws than have you find them.
Hard work isn't the secret — and that's the secret
Hard work and consistency matter enormously. But they are not enough, and pretending otherwise is why you see people grind for years and stay stuck.
“People parrot ‘work smart, not hard’ without knowing what it actually means.”— Day 14: Why Hard Work is not enough
Here's what it means, concretely. Effort only compounds if you're practicing the right thing and you can see whether it's working. Pour ten thousand hours into the wrong drill and you don't get a master — you get someone who's exceptionally good at a bad habit. The hours aren't the variable that's broken. The hours are fine. What's usually broken is everything that's supposed to happen before and around the hours. Fix that, and consistency stops being a virtue you have to summon and becomes a thing that just pays out.
That's the takeaway I keep coming back to, and I want to state it cleanly before I earn it:
“consistency is the only differentiator between the best and the mediocre.”— Day 14: Why Hard Work is not enough
Only after the three moves below. Consistency is the tiebreaker, not the strategy.
Move one — research where the common advice is wrong
The first thing I do when I pick up a skill is not the skill. It's a couple of days of pure research — YouTube, articles, ChatGPT, anyone who's already done the thing — before I let myself touch the actual work.
This sounds lazy. It is, in the good way. I'm the kind of lazy that will happily spend ten hours finding the path that saves a hundred. Most people skip this step because starting feels productive and reading feels like procrastination. But jumping in blind is how you bake in bad form, pick a slow route, and then spend months unlearning what a few hours of research would have warned you off.
The real move isn't "research." It's finding where the common advice is wrong. Almost every skill has a piece of folk wisdom everyone repeats that turns out to be the bottleneck. "Just immerse yourself" for languages — a myth on its own; immersion is the cement, not the bricks. "Grind ranked" for a competitive game, when the actual lever is settings and fundamentals nobody talks about. I go looking for that wrong thing on purpose, because finding it is worth more than any amount of effort I could spend not finding it.
“Don't just jump in blindly—learn from others' experiences. Spend days watching YouTube videos, reading articles, and using ChatGPT to find the best practices before you even start.”— Day 14: Why Hard Work is not enough
This is the same move I run when I build software — find the real bottleneck, not the one that feels hard — which is why I think of building and learning as the same engine pointed at different problems. The domains change; the method doesn't.
Move two — build a feedback loop
This is the one I'd tattoo on something if I were the tattoo type. Without feedback, you cannot improve. You can only repeat — and repetition without feedback is just rehearsing your mistakes until they're permanent.
Some feedback is free and obvious. Your shot hits the net; you missed. The compiler throws an error; you broke something. But the dangerous skills are the ones where the feedback is silent. Sing "Do Re Mi" for hours with no way to check the pitch and you're not practicing singing — you're practicing being confidently flat. The note feels right, which is exactly the problem. Most of the bad habits that follow people through entire careers are habits the feedback loop never flagged, because nobody built one.
“Without feedback, you won't know if you're improving—or worse, reinforcing bad habits.”— Day 14: Why Hard Work is not enough
So I build the loop deliberately. A coach, a tracking app, a recording I review, a pitch meter, a friend who'll tell me the truth — whatever turns an invisible signal into a visible one. And I keep iterating on the loop itself, not just the skill, because the early feedback matters most: a wrong rep on day one becomes muscle memory by day ten, and muscle memory stacks.
The most me version of this didn't involve a skill at all. I'd plateaued losing weight, so I treated my body like any other system with a bug — I used my computer science degree to debug my weight loss. The problem was signal-to-noise: real daily fat loss is tiny, buried under a couple of pounds of water and food swing, so the bathroom scale is almost pure static — like trying to hear a whisper in a thunderstorm. The fix was to stop reading the noisy number and track the delta from a target line dropping a little each day, where the error accumulates and the real signal climbs out fast. Suddenly every morning was a clear instruction instead of a coin flip. That became Weave; my mom lost 17 pounds with it after years of trying, and I lost 16. The app was just where the feedback loop happened to land.
Move three — spread the practice across days
The third move is the one that feels like cheating, because it asks you to do less.
Cramming has sharply diminishing returns. Four hours in one sitting is worse than twenty minutes a day for a week, and not by a little. The reason is sleep. Sleep is when your brain actually files what you practiced — it consolidates both muscle memory and knowledge overnight. Skip the sleep, and you're trying to build on a foundation that never set.
“Too much in one day has diminishing returns. Sleep solidifies both muscle memory and knowledge learned. This lets you do more with less.”— Day 14: Why Hard Work is not enough
This is also why "30 days" is the unit and not "a weekend." The month isn't there to let me grind longer. It's there to give sleep thirty chances to do the part of the work I can't consciously do. A little, daily, with rest in between, beats a heroic burst every time.
The proof I trust most is my own. I taught myself enough Japanese to hold a conversation — A1, somewhere north of a thousand words — in roughly twenty active hours, done in short sessions of about twenty minutes a day, spread across weeks. (People sometimes hear "three months in Japan." That was the immersion that cemented it; the actual learning was the twenty hours.) Twenty minutes a day shouldn't be able to do that. Spread across days, with sleep doing the filing, it does. That experience is the seed of Flua, and the longer version of the language story lives over on the learning page.
Why learning everything is the actual cheat code
Those three moves are how. Here's the why — the belief underneath all of it, the one that makes my whole scattered-looking life make sense.
Most people pick one thing and grind it for a decade. I think that's usually the worse bet, and the math is on my side. The Pareto principle applies to learning too: the first chunk of effort buys you the bulk of the skill, and the long tail of mastery costs wildly more for less.
“In just two years, you can learn 80% of a skill. Instead of spending 10 years perfecting one thing, you could be 80% good at FIVE.”— Day 11: The Real Cheat Code to Growth
And here's the part that turns five separate skills into something exponential rather than just additive: everything is interconnected. Singing makes you a better speaker. Video games train you to perform under pressure. Art sharpens your eye and your sense of how to imply detail. Learning a language rewires your brain for pattern recognition, which quietly improves your problem-solving and your code. Each skill feeds the next; the connections compound.
“The best ideas come from combining insights across fields. That's why Steve Jobs' calligraphy shaped Apple's design. Roger Federer played multiple sports before dominating tennis. The biggest breakthroughs don't come from mastery—they come from mixing skills.”— Day 11: The Real Cheat Code to Growth
The point of breadth isn't to do more things. It's to think better — to have more angles to attack a problem from, more borrowed intuitions, more places where two unrelated fields suddenly rhyme. Debugging my weight loss taught me product design. Game design became my master metaphor for life. None of it was a detour.
“If you want to be truly unstoppable, learn everything. The connections you don't see today will make you insanely powerful tomorrow.”— Day 11: The Real Cheat Code to Growth
The rubber duck — my best trick and my worst flaw
There's one technique that does so much work across all three moves that it deserves its own section, and it's free.
You know the feeling: you're stuck on a problem, you go to complain to a friend about how impossible it is, and somewhere in the middle of explaining it — click — you solve it yourself, before they've said a word. Programmers have a name for this. They keep a rubber duck on the desk and explain the bug to the duck, because the duck works just as well as the friend.
It works because of how your brain processes information. Daniel Kahneman's framing in Thinking, Fast and Slow is that explaining something out loud flips you from fast, intuitive thinking into slow, analytical thinking. Cognitive scientists call the win the self-explanation effect — you understand more when you're forced to articulate it (Chi et al., 1989) — and the trap it rescues you from the illusion of explanatory depth — you think you understand something until you actually try to explain it (Keil, 2003).
Here's the mechanism, and why it's so reliable:
“when you speak, you're forced to linearize your thoughts—turning a messy, jumbled idea into a clear sequence of logic. And the moment you do that, gaps in your understanding become obvious.”— The Rubber Duck
That's the whole method in miniature. Articulating something is a feedback loop — it surfaces exactly where your understanding has holes. So I do it constantly: I talk through what I'm learning, out loud, to a duck, a wall, or whoever's nearby.
“the best problem-solvers don't just think harder—they think out loud. … sometimes, the smartest person in the room... is you.”— The Rubber Duck
And now the honest part, because I'd rather say it than have you notice it: this is also my single biggest social flaw. The thing that makes me learn fast — running constant out-loud explanations — is the exact same thing that makes me monologue at people instead of listening to them. Same mechanism, two completely different reviews. I'm working on aiming it at the duck and not at my friends.
The counterweight — I'm not a grinder
If this all reads like productivity gospel, let me break character, because the most important thing I can tell you about my own method is where it doesn't apply to me.
I am not a grinder. I think sixteen-hour days are mostly counterproductive — I've done them, and they cost me more across the week than they bought me on the day. I aim for something like a thirty-to-thirty-five-hour work week and I protect my fun on purpose. So when I say "thirty days," please don't picture a war room.
My real bottleneck has never been stopping. It's starting. Almost everything I optimize is the on-ramp — the first rep, the blank page, the friction right at the beginning — because that's where I lose, every single time. I start far more than I finish, and I know it; it's the same honest gap that runs through everything on the Maker. The method in this essay is genuinely how I learn fast. It is not a story about superhuman discipline. It's a story about a lazy person who got very good at finding the path that needs the least of it, and who is still, slowly, learning to walk it all the way to the end.
So: research where the advice is wrong. Build a loop so you can see. Spread it across days and let sleep do its job. Stay broad, because the connections compound. Talk it out loud — to the duck, ideally. And if you like taking a skill apart to find where everyone else is wasting their effort, come say hi — it's a lot more fun with company.