Monkeywrench
Nobody wants to hear this, so I’ll say it plainly: the friction is the curriculum. Remove the friction, you removed the lesson. And you will not know what you missed until you need it and it isn’t there.
This is not a motivational speech. I find those 100% useless. This is a structural observation about how skills actually form, and why the entire optimization culture around learning is producing people who know how to follow instructions and nothing else.
The dominant advice right now is to remove all obstacles. Use the tool. Use the shortcut. Use the template. Get to the output faster. And if you’re building something disposable, fine. Go nuts. But if you are trying to build capability in yourself, every shortcut you take is a debt instrument. You borrowed the result without paying for the understanding. Somewhere down the line, the bill shows up.
I’ve seen it happen in IT for twenty years. Junior tech comes in, knows the GUI, knows the wizard, knows the tool that automates the configuration. Then the tool breaks. Or the edge case hits. And they’re standing there with nothing, because they never had to understand what the tool was actually doing. They learned the procedure, not the system.
That’s not a knock on them. That’s a knock on the pipeline that told them the procedure was enough.
When “Efficient” Is Just Another Word for Shallow
The harder version of this is that the pain has a shape. It’s specific. And that specificity is information you cannot get any other way.
When you break something and have to trace it back to find the cause, you learn the actual structure of the thing. Not the happy path. The whole topology. You learn what fails, under what conditions, and why. That knowledge doesn’t come from reading documentation. It comes from standing in the wreckage and having to reconstruct what happened.
Good documentation, when someone bothers to write it, is actually a record of that process. Someone broke something, figured it out, and wrote it down so the next person doesn’t have to start from zero. That’s documentation as an act of respect. But you can only write that kind of documentation if you went through the experience yourself. You can’t document what you skipped.
Here’s what nobody in the productivity space will tell you: the people who skip the hard parts don’t know they skipped them. That’s the nature of the skip. You don’t get a warning label. You just have a gap in your understanding that won’t show itself until exactly the wrong moment, under exactly the wrong conditions.
I’ve watched people spend a year optimizing a workflow they didn’t fully understand, building elaborate automation on top of a foundation they’d never stress-tested. Then one upstream change comes through and the whole thing folds. And they have no idea where to start because they never built the underlying mental model. They built the shortcut. The shortcut isn’t load-bearing.
The counterargument is always efficiency. “I don’t need to understand how the engine works. I just need to drive the car.” Fine. For driving, sure. But if you are trying to build something, fix something, or adapt when circumstances change, “I just need to drive the car” gets you stranded on a two-lane highway at midnight in the rain.
The culture around AI tooling right now is a perfect example. Everyone is racing to remove every point of friction from every workflow. Generate it. Automate it. Skip the draft, skip the iteration, skip the part where you sit with the problem long enough to actually understand it. Get to the output.
And the output is fine. The output looks right. But the person who generated it didn’t build anything. They retrieved something. Those are different operations with different residuals.
Retrieving something teaches you that the thing exists. Building something teaches you why it is the way it is, what it costs, and what breaks it. Only one of those produces judgment. The other produces people who are very fast at tasks they don’t fully understand.
Nobody is coming to tell you when you’ve skipped something important. The system doesn’t flag it. Your productivity metrics will look great. You will feel efficient.
And then the edge case shows up, and you’ll be staring at it with clean hands and no idea what to do.
