2,004 karma · joined June 26, 2022
ME by education, Software Creator/Exec by profession, EE by interest. Amateur boat builder.
The state machines use JSONata for the sweet, sweet power vs JSONPath. Generally I have a Parallel state that splits the different parts of the page and Map states for data driven repetition (usually some data pulled from DDB). I have a simple JSONata method for replacing placeholder values (aka data binding). Zero Lambda at the cost of come copy paste.
I’m not unhappy with it despite the warts.
I can see how rough location information is helpful for support and business information. Maybe country, maybe even zip code. But precise GPS was a bit overkill. Maybe it was easy, maybe it was nefarious, but not encrypting it over the wow was just plain dumb. I guess there is a razor for that.
How would this exfiltration happen though? Aren’t these cameras going to be behind a firewall? Without a request originating internally no external packet will make it past, right? Does the firmware make the first request? If so, I missed it.
I’m more mystified by the fleet wide certs. Old manufacturing tech that makes per-device firmware difficult, perhaps?
Blood sugar in non-diabetics is boring, rarely moving in any significant way.
One impact could be dispelling misconceptions if you have them. Another could be discovering pre-diabetes.
I’m having trouble with this one, and am tempted to write it off as playing with mice in a lab. The extrapolation to human conditions is hyperbolic, maybe worse.
Given the number of people with continuous glucose monitors and activity tracking watches in the world, why not study that data directly? Causation by activity would be more apparent, more relevant and more significant (if present) wouldn’t it?
To those saying it’s the work of an LLM: if it is I don’t care. It’s good.
The only path that isn’t disastrous is threading the needle of “just right” productivity gains. The people in charge aren’t smart enough to give me warm fuzzy feelings on that.
If the customization can be done after the fact it lowers the risk of buying.
Makes sense to me.
The realtors I’ve met understand economics and markets very well. Not as academics but as practitioners.
The folks I’ve worked with have been as dedicated to their career path as anyone, and while their expertise and skill varies that isn’t different than any job. I understand your point, but your (mis?)characterization hits me as a little biased and shallow.
It’s not “theory”; it’s literally what they do.
also, they don’t get paid if something doesn’t sell for being overpriced.
it’s a market system.
I’m not sure how or why this article got published by an organization that should, given its very nature, understand economics. The article doesn’t paint them or their members as people I’d trust in either side of a major financial transaction.
I’ve enjoyed the combination with Range headers for paging, despite this tidbit:
> It is expected that these built-in features will be used instead of HTTP Range Requests
Using the QUERY request as the definition of a set, and Range to retrieve subsets seems very natural.
That’s weird. I grew up around farming and farmers. A group also very proud of the work they do, in a profession where the wage is also indirect — sometimes negative, sometimes a fortune, always based directly on the work they’ve done. Year after year, the work.
That’s different.
I’ve always identified two sets in the realm of entrepreneurs: those that want to “be rich”, and; those that want to “become rich”. The latter group is perhaps more admirable as they acknowledge the process and the value creation whereas the former seek only the status. But neither are often interested in the work of it.
Maybe at some point S3 will have a native implementation of something like this.