561 karma · joined January 17, 2009
I think he "got" it. He was certainly annoyed at the idea that something purchased could just be taken back. Maybe it'll stick and he'll be better able to understand why I'll push back on a new PlayStation or any digital only games.
Sometimes there aren't any docs. Sometimes the docs are wrong. It's important to be able to establish what the actual running situation is.
I only have the bandwidth to talk to a couple 10s of candidates since I have the entire rest of my job to do, so I can see the appeal of an AI interviewer. I'd never use one due to the issues brought up here though.
It is at the company I currently work for. We moved to Rancher Desktop or Podman (individual choice, both are Apache licensed) and blocked Docker Desktop on IT's device management software. Much easier than going through finance and trying to keep up with licenses.
“Teasers are usually rich kids with nothing to do. They cruise around looking for planets that haven’t made interstellar contact yet and buzz them.”
“Buzz them?” Arthur began to feel that Ford was enjoying making life difficult for him.
“Yeah,” said Ford, “they buzz them. They find some isolated spot with very few people around, then land right by some poor unsuspecting soul whom no one’s ever going to believe and then strut up and down in front of him wearing silly antennas on their head and making beep beep noises.”
-- HHGTTGSo, yeah, Calculator is a pretty important feature.
Apps market? Piwik (tracking)? Why would I allow these?
GEEK PERL CODE [P+++++(--)$]
My tendencies on this issue range from: "I am Larry Wall, Tom Christiansen, or Randal Schwartz.", to: "Perl users are sick, twisted programmers who are just showing off." Getting paid for it!
Sounds typical for construction.
Needs a copywriter...
If only...
BCP 38[0] is nowhere near usual. Lots of networks, including some very problematic big ones (cough Hurricane Electric cough), do not implement it as a matter of course. The AWS Route53 hijack last month which resulted in downtime for a number of sites plus a six figure coin theft[1] could have been prevented by adequate filtering.
0: https://tools.ietf.org/html/bcp38
1: https://arstechnica.com/information-technology/2018/04/suspi...
They're not pretending to be Amazon, they're pretending to initiate a connection to an Amazon domain. The "conversation" goes like so:
Clear text request: "Hello, I would like to speak TLS with souq.com"
Clear text response: "Why yes, let us do that with these parameters"
Encrypted request: "Please give me the page for signal.org/api/whatever"
etc...
I'm sure that there were ops teams working on it before then. The people involved in actually fixing the problem wouldn't have been posting to public mailing lists.
The current state of the technology is probably best described as "finicky": the sensor skin patch needs to be replaced every week or two, at which point it's much less accurate for a couple days. It also needs calibration inputs from a finger prick at least every 12 hours. In general if the sensor is reporting a high or low condition her first action is to double-check with a finger prick. More often than not the sensor is simply wrong.
With all that said, it's better to have the sensor than not. She is able to use an app [0] to track her glucose levels over both the short term and long term trends. She's been able to use that data to make dietary decisions which allow her to keep her glucose within range and she had very good A1c levels (5.4, vs a goal of "under 7" for many diabetics) at her last checkup.
I think the long term data collection ability means that a more connected sensor (as opposed to the linked tattoo) will continue to be beneficial for diabetics. The next steps in the useful technological development will be to integrate with insulin pumps (this technology is already in trials) and to integrate with diet tracking data e.g. from MyFitnessPal to assist with meal decisions.