Entry № II · I · V · MMXXVI
On building in public
Reflections on sharing the process, not just the result — and what I learned by writing while coding.
- Entry
- № II
- Date
- Reading
- 1 min read
- Topics
- reflection · career
A year ago I started documenting what I built — not polished tutorials, but raw process notes. What worked, what failed, what I thought at 2am debugging a pipeline.
Why share the process
Final results impress for seconds. Processes create connection. When I share that a chunking strategy failed three times before working, other people feel less alone in their own bugs.
The invisible cost
Writing while building has overhead. Sometimes it feels like doing two things halfway. But I realized writing forces me to understand — if I can't explain it, I didn't truly get it.
What changed
- I get messages from people in similar situations
- My portfolio stopped being a project list and became a narrative
- I learned to communicate trade-offs — an underrated engineering skill
An honest note
Not every day is inspiring. Some posts are just "today I broke production and fixed it." And that's fine. Authenticity > perfection.
If you're thinking about starting: don't wait for the perfect post. Publish today's note.