Why we teach this way
Show someone a knot and they've seen a knot. Explain it — the working end here, under, around, back through — and they've heard an explanation, and it sounds, by the third repetition, like they understand it perfectly. Ask them to tie it themselves, ten minutes later, with the same rope, and watch the certainty leave their hands.
There was a rigger at the yard in Sag Harbor who tied a bowline slower than anyone needed him to, every single time, in front of anyone who asked. Not because he'd forgotten how. Because he'd learned, watching hundreds of people watch him, that the demonstration wasn't the lesson. The tenth try was the lesson. He'd hand you the rope after the second turn and walk away.
(He was, by his own account, terrible at explaining things. He didn't disagree.)
We build the same way. Not a walkthrough you follow along with, nodding, certain, and then can't reproduce alone on a Tuesday. An actual application, built by your own hands, wrong more than a few times before it's right — because the trying is the part that stays.
You will not simply be told how this works. You'll know, because you'll have done it.