Field notes
Short writing from engagements—hop maps, latency clinics, correlation artefacts, and honest scope.
-
Map the hops before you add another latency chart
A polished board on unnamed spans only accelerates the wrong debate.
-
Retries that invent latency cliffs
A span that opens only after a silent retry can look like mass abandonment.
-
When HKT calendars and UTC warehouses disagree
Day-one latency cohorts can shift when midnight moves—not when the network does.
-
What Advanced Networking Solutions does—and does not—sell
Expect diagnostic clarity and owned artefacts, not a managed growth machine.
