An independent notebook
Observations on software, networks and the quiet work of keeping things understandable.
A useful maintenance note records the original state, one specific change and a repeatable check. When something behaves differently, a small record makes the next decision easier.
Save configuration before editing it. A backup is most useful when its location and restoration steps are clear.
An open port is only the beginning. Name resolution, secure connection setup and the final application response each tell a different part of the story.
Repeat the same request before and after a change. Keep timing samples in context rather than treating one result as a promise.
This is a small, self-hosted collection of personal technical notes. The pages are static and can be read without an account or client-side scripts.
The aim is straightforward: fewer moving parts, clear explanations and practical maintenance habits.