On Learning by Doing (and Writing It Down)

I’ve learned most of what I know by doing, not by reading about how something should work. Whether it’s technology, systems, or the way people actually use tools, real understanding has almost always come from trying, failing, adjusting, and trying again.

Writing has been the other half of that process. Not as a way to teach or persuade, but as a way to slow down and make sense of what I’ve just experienced.

This site exists as an extension of that habit.

Learning by doing

Over time, I’ve noticed that the things I truly understand are the things I’ve struggled with directly. Documentation, training, and theory all have their place, but none of them stick in the same way as friction does. Something not working as expected, a process breaking down in practice, or a tool behaving differently in the real world forces you to engage more deeply than passive learning ever will.

Those moments are rarely neat. They’re often frustrating and occasionally humbling. But they’re also where the most durable learning happens. Once you’ve had to untangle a problem yourself, the understanding that comes out the other side tends to stay with you.

That pattern has repeated itself enough times that I’ve learned to trust it.

Why writing it down matters

Writing is how I make sense of that friction.

It’s easy to think you understand something until you try to explain it, even if only to yourself. Writing has a way of exposing gaps, assumptions, and half-formed ideas that stay hidden in your head. It forces clarity where vagueness is comfortable.

More than that, writing slows things down. In environments that reward speed, decisiveness, and constant motion, writing creates a pause. It gives me space to reflect on what actually happened, what I learned from it, and what I might do differently next time.

This site isn’t meant to capture finished answers. It’s meant to capture thinking in motion.

Learning with AI, not replaced by it

More recently, AI has become part of that learning loop. Not as a replacement for my work or my thinking, but as an accelerator for it.

I’m not shy about using AI in how I build, write, and learn. Used well, it doesn’t remove the need for judgment or experience. It sharpens them. It helps me move faster through the parts I already understand so I can spend more time on the parts that still surprise me.

In writing, that often means using AI as a conversation partner. I’ll draft an idea, go back and forth on structure or clarity, challenge my own assumptions, and refine a piece before it ever reaches a reader. The final words are still mine, but the path to them is often shorter and more deliberate.

In learning and building, it’s similar. I’ve been teaching myself how to run and experiment with large language models locally, exploring how they behave, where they fall short, and how they can be integrated into real workflows. The goal isn’t automation for its own sake, but understanding how these tools can extend the way I already think and work.

Over time, I’d like to push this further. I’m interested in building systems where a simple prompt kicks off a back-and-forth conversation, allowing ideas to be explored, challenged, and shaped before a final piece is ever written. Not to remove the human from the process, but to give the human more room to think.

That’s ultimately what matters to me. AI hasn’t replaced the parts of my work I care about. It’s given me more time for them.

What this site is (and isn’t)

This site isn’t meant to be polished thought leadership, exhaustive tutorials, or a running commentary on trends. It’s not optimized for performance or designed to say the right things in the right order.

It is a place to document what I’m learning, reflect on work as it actually happens, and occasionally step back to make sense of it all. Some posts will be more structured. Others will be closer to personal reflections. All of them are part of the same process.

Closing

I don’t know exactly where this will lead, and I’m comfortable with that. What I do know is that learning by doing, and writing things down along the way, has consistently helped me work more clearly and intentionally.

Tools change. The habit of thinking carefully about what I’m doing, and why, doesn’t.