Tech — Work — Ramblings

by Mike Kalvas

I see you're not using JavaScript (which is awesome!) on one of my pages that uses it to provide a better experience. If you see something not working right, please let me know. My site should work exactly the same without it apart from any exceptions noted here.

I use prism.min.js to do syntax highlighting. It clocks in at 23kb total in size. Since the majority of the writing I do involves coding, I personally find this to be a worthwhile trade off. If you choose to keep this disabled, rest assured, the code examples are still there, they just may have some extra whitespace and obviously no syntax highlighting.

I do no tracking at all and am a zealot about keeping my pages as small as possible. If you're reading a page of mine that transfers more than about 250kb over the wire (including my most gratuitous indulgence — fonts) I've messed up.

So, if you'd like to have a slightly richer experience, consider enabling javascript for my site and I promise your trust won't be misplaced.

202402171455 Feedback can only affect future behavior

While mostly tautological — or physical based in relativity and information transfer — the statement that feedback can only affect future behavior is important. It describes “lag” and requires our attention to the lag time — if I’m ordering stock for my store inventory, I need to account for the continued outflow of inventory as the resupply of inventory is arriving after ordering it.¹

More generally, it means that flows can’t react instantly to other flows. They can only react to changes in stocks and after a delay. (huh? #wip)

Meadows, D. H., & Wright, D. (2011). Thinking in systems: A primer (Nachdr.) (pp. 39). Chelsea Green Pub. ↩