Writing
Design docs, post-mortems and final reports, written while the details were still fresh, mostly about the parts that did not work the first time.
Engineering write-ups: what was built, what broke, and what the fix actually was.
The full write-up of my Google Summer of Code project at Apache Fory: what shipped in both merged PRs, the reference-tracking divergence that broke Java↔Swift interop, why I now revert every fix to confirm the test actually fails, and what reviewing for degenerate input taught me.
Carbon-aware scaling is easy for batch. Stream processors are the awkward case. The design notes behind the operator: savepoint-before-suspend as an invariant, three scheduling policies compared over a fourteen-day replay, and a cost predictor that calibrates itself against its own history.
How the detection engine and the command center fit together: kernel-bypass capture through DPDK, Suricata for deep packet inspection, ML scoring over extracted features, and a SOAR layer that writes firewall rules at runtime.