Writing about software can begin with one question that became a little clearer.
A useful note might explain a small decision, compare two approaches, or describe an experiment that did not work as expected. The useful part is making the thinking visible.
Start with one concrete thing
Choose a question small enough to explore in a page:
- What happens when this request is sent twice?
- Which part of this example needs to know about the database?
- What does this diagram leave unexplained?
Keep the example close to the question. A reader should be able to follow it without reconstructing an entire project.
Leave room for revision
A published note can change. If a better explanation appears, update the post and explain what changed. Being precise about uncertainty helps a reader decide where the explanation is useful.
The goal of a notebook is to make the next thought easier.
Writing in two languages adds another chance to examine an idea. If an explanation becomes awkward in translation, it may be worth simplifying the thought itself.