Notes on Learning in Public
A personal reflection on writing while learning, sharing unfinished thoughts, and using a blog as a long-term engineering memory.
Rizky Romadon//2 min readTL;DR
Learning in public is not about pretending to be an expert. It is about documenting the journey clearly enough that future you, and maybe someone else, can benefit from it.
Why I Keep Notes
Engineering work creates many small lessons. A debugging session, a design review, a production issue, or a new tool can teach something useful. But if I do not write it down, the lesson becomes blurry.
This blog is a place to keep those lessons alive.
The Value of Incomplete Thinking
Not every post needs to be a complete guide. Some posts can be field notes: what I tried, what surprised me, what I would do differently, and what still feels unclear.
That kind of writing is honest. It makes learning visible without turning the blog into a performance.
What I Want This Blog To Become
I want this space to collect practical thoughts about backend engineering, AI tools, product ideas, and the craft of building software. Some posts will be technical. Some will be reflective. The best ones will probably be both.
Conclusion
Learning in public is a quiet commitment: keep paying attention, keep writing clearly, and let the archive become proof that the journey is moving.