There was a period in my learning where everything looked right from the outside.
I was watching tutorials- Youtube videos and others.
I was reading guides-including PDF´s of code journals, W3Schools website and the in-depth coverage it gave in almost all programming languages.
I was following along, typing what I saw, and getting the expected results.
By most standards, I was “learning.”
But internally, something felt off. And so I felt.
I wasn’t lost, yet I wasn’t settled either. I could reproduce steps, but once the tutorial ended, the confidence faded quickly. The sense of flow I expected never really arrived. I could not actually connect the dots thereafter.
At that stage, my learning was mostly driven by consumption. Wait longer, it tends to dissipate-lost almost completely. And with a bit of frustration at how I could forget so soon, I would go back to try to fill the gaps again.
I moved from one tutorial to the next, assuming that consistency alone would eventually turn into understanding. Each video felt productive. Each article felt useful. And in isolation, they were.
But what I didn’t realize at the time was that I was collecting information, not owning it.
I could follow instructions, but I struggled to explain why something worked. If a small detail changed, I had to go back to the tutorial. If I faced a slightly different problem, the clarity disappeared.
The knowledge was there — but it wasn’t anchored.
This wasn’t a failure of tutorials.
In fact, tutorials helped me overcome fear. They introduced me to tools, concepts, and possibilities I might not have approached on my own. They lowered the barrier to entry and made learning feel accessible.
But they had a limitation I didn’t see early enough.
Tutorials are designed to show a path, not to build ownership. They guide you forward, but they don’t pause to ask whether you truly understand what just happened.
And I wasn’t pausing either. Just going.
The real issue wasn’t that I was learning the “wrong” way.
It was that I hadn’t yet learned how I needed to learn.
I mistook movement for progress.
I assumed that more effort will bring clarity and that staying busy meant things were sinking in.
But flow doesn’t come from repetition alone. It comes from clarity — and clarity only appears when you slow down enough to reflect.
That realization didn’t arrive as frustration or burnout. It came quietly.
I noticed that the moments where things finally made sense were the moments when I stepped away from the tutorial and tried to explain the idea to myself — sometimes in writing, sometimes mentally, sometimes by rebuilding something without guidance.
Those moments were slower. Less impressive. Less visible.
But they stayed with me.
That was the beginning of a shift.
I didn’t abandon tutorials. I simply stopped letting them lead the entire process. I began paying attention to what confused me, where I hesitated, and what I couldn’t explain clearly.
Writing became a tool, not for teaching others, but for understanding myself.
Documenting what I was learning forced me to confront gaps that tutorials had quietly allowed me to skip. Reflection turned passive knowledge into something more solid. Then the dots started connecting.
That’s when learning started to feel different.
This post sits between From Fear to Flow and the more structured journey that followed.
It represents the phase where learning looked productive, but understanding was still forming. It explains why documentation became necessary — not for content, not for performance, but for clarity.
The stages that come after this are shaped by that realization.
I didn’t need more speed.
I needed more structure.
And that’s where the next part of the journey begins.
This post is part of my ongoing learning archive.
→ My Tech Learning Journey — One Step at a Time
Obi'sDeck 