Alisina KarimiField notes on software

Engineering notes · 01—∞

Past the
happy path.

Notes from building software that has to hold up outside the demo: production systems, distributed storage, and tools for seeing what changed.

Observe, compare, repair A systems loop connecting observed state to a comparison and then a bounded repair. OBSERVECOMPAREREPAIR A SYSTEM IS A STORY ABOUT STATE
One useful loopState → evidence → action

Recent notes

2 field notes · systems & tools

01 / SYS A copy is not convergence. Replication moves bytes. Convergence is the work that starts after a peer misses one, loses an acknowledgement, or comes back late. 02 / MAP An architecture graph should know what it doesn't know. A diagram becomes dangerous when it draws a route it has not verified. For architecture tooling, uncertainty belongs in the output.

The thread / About

When a system changes, can someone follow the evidence?

I work across production software and independent systems projects. The subjects vary; the question underneath them tends to be the same: what happened, what changed, and what can we actually prove?

  • Production systems
  • Distributed software
  • Evidence & measurement