HackerTrans
TopNewTrendsCommentsPastAskShowJobs

dopylitty

no profile record

comments

dopylitty
·2년 전·discuss
They're tracking movements. Apple has a doc on how it works here[0]

>Apple Watch tracks movement with triaxial accelerometer signals, which capture coarse motion of the body as well as fine movements including motion associated with breathing. Apple developed an algorithm that uses the accelerometer time series data to classify Breathing Disturbances that occur during sleep tracking, which are temporary interruptions in the breathing pattern.

> A total of 1499 participants were enrolled, with 1448 completing the study. The sensitivity was 66.3% (95% CI: 62.2% to 70.3%), and the specificity was 98.5% (95% CI: 98.0% to 99.0%), demonstrating that the feature meets the design objectives to confidently identify sleep apnea while minimizing false positives.

>It’s important to note that the specificity was 100% (95% CI: 99.7 to 100%) for the normal category, indicating that all participants with a “positive” algorithm result had at least mild sleep apnea. Also, sensitivity was higher in the severe category at 89.1% (95% CI: 83.7% to 93.2%), indicating that the large majority of severe cases were identified.

0:https://www.apple.com/health/pdf/sleep-apnea/Sleep_Apnea_Not...
dopylitty
·2년 전·discuss
I’d take it a step further. If a technology is impossible to secure it shouldn’t be used. Maybe it’s time to rethink all the parts of our lives we’ve handed over to software.
dopylitty
·2년 전·discuss
Not only that they blew $8 billion/year on dividends that could've gone into the business or to employees instead of being extracted and given to people who have nothing to do with the business.
dopylitty
·3년 전·discuss
Another variation on this I've seen is an 'agile' 'team' composed of several groups of engineers each reporting to different managers in the organization with a scrum master and product owner who reported to yet different chains of command.

All of these chains of command had different and conflicting priorities as well as political wars with each other. The product "owner" knew very little about the ill-defined product they owned yet they set the team's 'official' priorities based on wish lists from the business while the engineers also got different priorities from their chain of command and the scrum master was a glorified admin assistant.

The result was that no strategy existed and nothing of value was done but the engineers were still ground to a paste against the mill stones of the Jira board every two weeks.

It made me miss the simpler times of having a well defined waterfall project being done by a single team of engineers with a single engineering manager and a project manager to make the gantt chart and schedule the meetings.