Why I write
Someone asked me recently why I put time into writing notes and how-to guides when I already have a full-time job. It's a fair question. The honest answer has three parts — and none of them are about building a personal brand.
Writing is how I find out what I actually know
There's a version of understanding that feels solid until you try to explain it. You've been doing something for years. You think you know it. Then someone asks you to walk them through it and you realize there are gaps — places where you were running on pattern recognition, not real comprehension.
Writing forces the gaps to surface. When I write a how-to guide, I can't handwave the steps I usually skip. I have to think through the whole thing, in order, in plain language. The parts where I slow down and struggle are exactly the parts I didn't understand as well as I thought.
I've learned more by writing about what I do than I ever did just by doing it.
Readers teach me things I didn't know I didn't know
The second thing I didn't expect: the questions.
When someone reads what I wrote and comes back with a question I hadn't thought of, that's the most valuable feedback I can get. Not because they found a mistake — sometimes they did, sometimes they didn't — but because it shows me the edges of my thinking. Where my mental model stops and someone else's begins.
A 1:1 conversation only reaches one person. Writing reaches whoever finds it, and every question I get back makes the next version better. The more people read, the better I get at understanding the problem I was trying to solve in the first place.
The flywheel: You write to understand. Readers find gaps you missed. You understand better. You write better. It compounds. This is the core argument for writing in public — the feedback loop is faster and richer than anything you get working alone.
I want to be known by what I gave, not where I worked
This is the part that matters most to me.
I've spent 20 years in enterprise software. Right now I'm at Oracle. Before that, somewhere else. After this, somewhere else again. The company on your LinkedIn profile changes. The title changes. What doesn't change is what you left behind for people.
The version of success I'm aiming for isn't someone saying "oh, he was a PM at Oracle." It's someone saying "Edson helped me figure this out" — and meaning it about something real. A how-to that unblocked them. A note that reframed a problem they were stuck on. Something they actually used.
That's the kind of footprint I want to leave. Not a resume. A track record of being useful to people outside the walls of wherever I happened to be working at the time.
Writing is the most direct way I know to do that.