Performance work is product work
Why runtime improvements, profiling, and algorithm cleanup are not side quests when the product lives inside Office.
Notes
Short writing for the engineering patterns that keep paying off.
This section is intentionally small for now. The goal is practical notes, not content marketing: performance work, delivery leverage, hands-on architecture, and the kinds of engineering decisions that compound over time.
Delivery leverage beats busywork
Notes on the kind of tooling, CI, and workflow improvements that quietly compound into a much stronger team.
Hands-on architecture
A working definition of architecture that still stays close to code, operational detail, and product reality.