- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
the first one listed here, about the sensitivities seems perfectly fine as it is. No "errored" here at all IMHO.
Edit Admin
How do you write code to generate a year of -4712?
Admin
I'm sure it's in some way related to the most WTF date format in the world: MM/DD/YYYY.
Edit Admin
I agree with you, the first one does not seem to be a WTF because they are sensitivities for two different aspects of motion detection:
The first is for the sensitivity of motion detection, and the way I read it is:
The second is for the sensitivity threshold for the detection of human-like shapes, and the way I read it is:
Ergo, no WTF here.
Admin
Maybe not the problem with "sensitivity" settings per se, but definitely a UX/usability problem. At least two programmers commented here that think everything is as it should be instead of talking about how that interface is confusing (it indeed is).
Admin
Maybe they should use "specificity" for the Humanoid Detection setting (ref: "sensitivity and specificity" as used in the medical field). https://en.wikipedia.org/wiki/Sensitivity_and_specificity
Edit Admin
Exactly. The error is not in the sliders. The error is in using the term "sensitivity" inappropriately. And especially using it i opposite sense nearby each other.