J.P. Stewart

He/Him Ring-holder in the Order of the Engineer - I love designing small networks - Tech Geek - I love finding/taking engineering hardhat tours - Gluten Intolerant 

Landing Page: https://jpstewart.org/

Last Notes

2025-09-28 21:09:45 UTC

- reply

Everybody loves baklava!!!
(lol. This is a catchphrase of mine just because of this commercial.)
https://youtu.be/BeokSqp2VBU?si=ZzJKfzSX63taNbFz

2025-05-15 15:50:30 UTC

- reply

wiiiiinnnnnnnssoooooock
(Ok see namespace service providers for the real answer. Also use the powershell resolve-dnsname for the nslookup equivalent through the winsock stack.)
https://learn.microsoft.com/en-us/windows/win32/winsock/name-space-service-providers-2

2024-12-23 20:38:29 UTC

- reply

It's so hard having a detailed conversation on this inside of 500 characters. :)
I wrote a detailed internal "measure engineering manual" on this topic and more for example.
- "Data" isn't magic. If you don't know what experience the values mean, there aren't any potential insights from gathering that data.
- Even if there is a change/regression in data seen, if you don't know in advance how to describe the impact of the failure, then no one will want to spend time to fix it.

2024-12-23 20:33:40 UTC

- reply

Software is complex. There are millions of potential data points to monitor / measure, more than there are humans to do something with that information (yes, even with the efficiency of automation).
The best way to approach this is to focus on measuring customer-centric metrics. What will cause a bad experience if it fails?
Engineers are incredibly bright/curious. Often there are asks to monitor something shiny without knowing what to do with the data. What is the experience?

2024-12-23 19:45:12 UTC

Ever wonder what it's like being a data engineering manager? It's asking: "What is the experience impact to users with that measure/data/telemetry?" on repeat.... forever.