<img src="https://media.daily.dev/image/upload/s--2Tet1HM1--/f_auto/v1765828581/ugc/content_64b5bf81-974f-4153-8305-ce027d9881a9?_a=BAMAK+ZW0" alt="80f516f9-1c02-442d-8781-4ec3738446db">
I’ve been putting more intention into how I document my learning as a developer.
Instead of only tracking finished projects or milestones, I’m trying to document the process itself — what I’m learning, what I’m testing, how I structure my work, and how my understanding changes over time.
The goal isn’t productivity or optimization. It’s clarity and consistency over a long time horizon, especially when learning starts to feel overwhelming or scattered.
Lately, I’ve been thinking of documentation as a skill in itself — something that improves decision-making, reflection, and long-term growth.
Curious how others here approach documenting their learning (if you do at all). 
Do you keep notes, write things down as you go, or mostly rely on memory and repetition?

Smiley Face

Developer's Journey is a place where we share our stories, career growth, technical adventures, and personal milestones, no matter where we are in our journey.

Developer's Journey

A developer shares their approach to documenting the learning process itself rather than just finished projects. The focus is on capturing what's being learned, tested, and how understanding evolves over time for clarity and consistency. They view documentation as a skill that improves decision-making and long-term growth, and invite others to share their own learning documentation practices.

Documenting my learning as a developer — focusing on process, not just outcomes

I use Siyuan Note when taking courses or write down something important. I can export them to structured markdown notebook. Then upload them to NotebookLM, then start to digging up the ideas with the AI.

I feel like as developers we don’t really use <a href="http://README.md" target="_blank" rel="noopener nofollow">README.md</a> as much as we should. I am trying to adopt a habit where I write as much as I can about the project I am working on inside <a href="http://README.md" target="_blank" rel="noopener nofollow">README.md</a>. Then later on if it’s necessary I can break it out into actual docs and expand those thoughts I had while building the project.

I am exploring Personal Knowledge Management, but still strugling finding a system i can settle with. Already refactored the whole system multiple times now…
I mostly take braindump, implementation, research and inspiration notes for my projects. i heavily use Inbox folder inside each project’s folder and just tell myself I can order things later. so i remove friciton. also began taking lot’s of voice note to braindump on the go wherever I am, cause note taking i like it more behind a pc.
Planning on using Quartz for Static Site Generator for hosting a website for all notes to be available online as alternative to obsidian publish.

I created my Second Brain, based on the P.A.R.A. system.
I try to document as much as possible from my life, especially learning related stuff.
It has become already very large within only a few years.
I regret not creating and using such a system decades earlier. It would’ve been more worth than a gold mine by now, with tons of invaluable information.

It is very good to document your learnings and activities