I’m a software engineer learning backend systems, networking, cloud, and Go by building things from first principles.

I write to polish my understanding, not to present myself as an expert. Most posts here start with something that confused me — a blocking call, a protocol detail, a design choice — and end with a clearer mental model.

This Substack is my public notebook:

  • evolving ideas

  • small discoveries

  • lessons learned the hard way

If you’re learning Go, backend engineering, or distributed systems and prefer understanding over shortcuts, you’ll probably feel at home here.

User's avatar

Subscribe to The Engineer’s Notebook

A long-form notebook on backend engineering, Go, distributed systems, and cloud architecture. Written while learning, building, and thinking deeply—one concept/system at a time.

People