Learning in Public

For years, I only shared finished work. Polished projects, refined thoughts, conclusions I was confident about. The messy middle—the confusion, the dead ends, the half-formed ideas—stayed private.

I’m trying something different now.

The Case for Messiness

There’s value in sharing the process, not just the result:

For others: Finished work can be inspiring but also intimidating. Seeing someone’s struggles and iterations is often more instructive than seeing their success.

For yourself: Writing about what you’re learning forces clarity. You can’t explain something you don’t understand, and the attempt to explain reveals gaps in your understanding.

What This Looks Like

For me, “learning in public” means:

• Writing about technologies I’m exploring, not just ones I’ve mastered
• Sharing projects in progress, not just finished ones
• Documenting questions I’m wrestling with, not just answers I’ve found
• Being honest about what I don’t know

The Discomfort

This is genuinely uncomfortable. There’s a vulnerability in saying “I’m figuring this out” rather than “here’s what I know.” It invites criticism. It risks looking foolish.

But I’ve noticed that the people I learn from most are often the ones willing to show their process. They make learning feel possible because they make it visible.

An Invitation

If you’re learning something—anything—consider sharing it. Not as an expert, but as a fellow learner. Write the blog post you wish existed when you started.

The internet has enough definitive guides. What we need more of is honest documentation of the learning journey.

You don’t have to have it all figured out. None of us do.