My Learning Journey

Learning in Public

There’s something powerful about sharing what you’re learning as you learn it. It’s not about being an expert — it’s about being honest about the process.

Why I Write

I started this blog for several reasons:

• Reinforcement — Writing about a concept forces you to truly understand it
• Accountability — Public commitments are harder to break
• Community — Others on similar journeys can relate and contribute
• Future reference — My past self documents for my future self

The Imposter Syndrome Problem

Let’s talk about the elephant in the room. When you’re learning in public, there’s always that voice saying “Who are you to write about this?”

Here’s what I’ve learned: everyone starts somewhere. The developer who wrote that framework you admire? They were once a beginner too. And chances are, they learned by sharing their journey with others.

The best time to write about something is while you’re learning it. You remember the pain points, the confusion, and the “aha” moments that experts have long forgotten.

My Approach

I follow a simple framework for learning new technologies:

1. Read the docs — Start with the official documentation
2. Build something — Theory without practice is forgettable
3. Break it — Understanding failure modes deepens knowledge
4. Write about it — Solidify understanding through explanation
5. Teach someone — The ultimate test of comprehension

Tools I Use

Tool	Purpose
Obsidian	Note-taking and knowledge management
GitHub	Version control and project hosting
VS Code	Primary code editor
This blog	Publishing and sharing learnings

Looking Forward

I have a long list of topics I want to explore and write about. This blog will be my living notebook — messy, evolving, and hopefully useful to someone out there walking the same path.

If you’re also learning in public, I’d love to connect. Reach out on any of my social links!