Building My DevRel Practice in Public
Why documenting openly is becoming my default way to learn, not just a distribution tactic.

Sample placeholder image for post layout preview.
I used to think writing in public should only happen after I had a polished framework.
Now I see it differently.
Writing while I am still learning helps me:
- capture context before memory edits the story
- notice patterns between projects faster
- create a record of decisions I can revisit later
For DevRel, this matters because the work often looks different depending on the company stage. What worked in one environment can fail in another if we copy tactics without checking assumptions.
My current rule is simple: publish the lesson when it becomes useful, even if the story is still in progress.