1,985 karma · joined August 4, 2008
My opinions are my own, and do not necessarily reflect the views of my employers, past or present.
Some people think it's fine for the process to have low precision but high recall. Low precision is that of the number of conversations the process flagged as a positive, some unacceptable (to you) percentage turned out to be a not/false "positive". High recall is that of all the actually positive conversations, the process flagged an acceptable (to you) percentage of them as positive (i.e. only "missed" a few/false negative).
What does it cost to wrongly identify conversation a positive when it's really not a positive (false positive)?
What does it cost to wrongly identify a conversation as a negative when it's really a positive (false negative)?
You decide.
That being said, in this case, I agree with your manager. Both the QA team and your team had fundamental problems.
Your team (I assume) verified the functionality which included X set of changes, and then your team made Y more changes (the flag) which were not verified. Ideally, once the functionality is verified, no more changes would be permitted in order to prevent this type of problem.
The fundamental problems on the QA team were…extensive.
Edit: In fact, it works so well, you can ask what it does for you.
On the other hand, if the private property was constructed with public monies, which MSG probably was, that’s an interesting debate. Should the involvement of public money confer first amendment protections of some sort? I think it should.
Edit: You can’t use “my” money to build something and then ban me from it because I said something (non-protected) about the CEO of the company that owns it.
A key part I think people miss is to make _sure_ your input metrics and output metrics are correlated. You would intuitively think that, say, lowering outage minutes would be correlated with revenue. And as a result, you should invest engineering and other resources in reducing outage minutes. But maybe experimentally or via some other type of analysis it isn't. Maybe users will tolerate some amount of outage minutes without materially impacting revenue. You can then utilize that knowledge to prioritize. Rather than investing in resiliency to improve outage minutes, you invest in something else because that will have a bigger impact on revenue.
I don't see how this weakens SEC enforcement. They can still seek enforcements. They just have to seek them via a trial by jury of your peers, which is one of the most foundational aspects of American law and one of the issues that led to the American Revolution.
We as a society need to continue trying to solve the problem of homelessness. However, leveraging the 8th Amendment, in part, to do it doesn’t make sense.