Re: good grief
Diagnostics are not telemetry (at least, I hope Borkzilla still maintains a distinction between the two).
As far as diagnostics are concerned, I have an explanation of the why because I am a developer and have been since 1996 (TLDR : I like diagnostics).
Whenever I write a script that must execute automatically without human intervention (ie at set time intervals), or executes in the background without pestering the user with error messages (because they're just ignored anyway), I want a log of that code's activity. I want to know the start environment, the data in input, the path that the code took and why and, if relevant, what the code sent back as response.
I want that information stored in a repository so I can consult it when (not if) there's a problem in production, because invariably, weeks, months, or even years after I wrote that code, I'm going to get a call to tell me that my code doesn't work anymore and could I fix that. Invariably, I ask what changed and, almost invariably, the answer is "nothing changed, your script is broken".
Yeah, sure, because I wrote chameleon code that overwrites itself. Pull the other one, etc. But you don't say that to the customer, do you ? Not when you're a freelance developer in any case.
So I know I have my logs. I ask permission to go on site and have access to the application. In customer environment, I access said logs and trace the activity back to where it was working properly, then I take the next log and find out, normally rather quickly, where the issue is.
Correcting the issue may be easy, or it may be hard, but I can print out that log and point to it as to why the code isn't working anymore (because you changed the date format of the server, doofus).
That, to me, is diagnostic data. Since I do not go and post that in The CloudTM, it is only accessible on-site and, therefor, as well protected as the client's server is (aka security is not my problem).
What happens after varies and is irrelevant to my point, which is : with logs, I spend at most 15 minutes finding out what went wrong. Without logs, it would take hours, if not days, just to find out what the issue is - especially when the customer doesn't want me accessing production data.
So I like diagnostics. They've saved my bacon (and my time) more times than I care to count, and they make me more efficient.
I'm just hoping that the term means the same thing for Borkzilla.