Engineering notebook / Notebook

A notebook for the things I build

A starting point for notes on code, infrastructure, and the workbench.

Starter content: This article demonstrates the new blog layout. It is not a migrated Hashnode post.

From an idea to a useful note

This notebook has room for Go, Cloudflare Workers, Linux administration, and OpenSCAD. The common thread is understanding how things work by building them.

A useful engineering note can be small. Start with a question, show a minimal example, and record what you learned.

A format worth keeping

  1. Describe the problem and the environment.
  2. Include enough context to reproduce the result.
  3. Explain the decision, including its trade-offs.
  4. Finish with a way to verify the outcome.

Code, diagrams, and commands should support the explanation. They do not have to carry the whole story.

What belongs here

Area Questions to explore
Go How can a small tool stay easy to understand?
Cloud infrastructure What makes a system easier to operate?
Linux What can the terminal tell us about a problem?
Parametric modeling Which dimensions should be adjustable?
Browse all writingSubscribe via RSS