4,040 karma · joined April 26, 2013
[1] Most people do. White bread has a high glycemic index.
The real issue is, and the author's real point (whether he knows it or not), is that non-scientists don't, and currently mostly can't, know anything about nutrition. To get a decent, self-respecting nutritional fact, you need to trace it back to the studies (to make sure it's not corporate BS,) make sure these studies are relatively recent (so that they're not deformed by the various assumptions and flawed conceptual frameworks that dominated the field a couple decades ago,) and ensure that the researchers and statistics at work are reasonably trustworthy (to make sure it's not some of the bad research that is still being done[1].) This is not something that most people can do, and that's simply to access the limited and uncertain facts we currently have. To the typical highschool graduate trying to make dinner, it's worse than useless.
([1] Which is, again, not unique to nutritional science. Bad papers are published in every field.)
More than a lack of knowledge, we have a lack of trustworthy authority. If someone wants to know about chemistry or math, trustworthy sources are easy to find, and their pronouncements can be taken on faith if the student doesn't want to get bogged down in the details. If someone wants to know next week's weather, the available answers will be uncertain and untrustworthy, but everyone at least knows the right people to ask, and has some idea of how to deal with "50% chance of rain." In nutrition, no one knows where to ask, and no one knows how to deal with what information that is available (for instance, raise your hand if you know the glycemic index of your most recent meal.) The answer to this can't be the scientific method; it's a social process.
Incidentally, the present nutritional wisdom is probably best summed up by Michael Pollan's "eat food; not too much; mostly plants." From that you'll be fine. (If you want to be really fancy, know the calories-per-serving of the ~10 most common foods you eat; by then you'll be eating healthier than about 95% of Americans, most likely. Know the glycemic index and you're past 99%.)
I consider it a reason to be optimistic.
I mean, even if autonomous cars are x100 times safer to be around than human-driven cars, they're still orders of magnitude more of a risk factor for ordinary (U.S.) citizens than say, terrorists, or sharks.
The article mysteriously doesn't cite Roux, and I don't have time right now to track it down, but it's probably similar.
[1] https://www.theguardian.com/world/2018/mar/17/china-reappoin... [2] https://phys.org/news/2017-02-china-severe-weather-patterns-...
Meanwhile, in terms of the parent article, yes- it turns out that "bioelectricity" is an important part of the embryonic development. But this is not at all serving the same role as DNA; DNA stores durable information, whereas these fields are being used for, essentially, intercellular communication. I would think that the fact that the researchers successfully replace a frog's entire brain, for developmental purposes, with a simple tweak to an ion channel, pretty clearly demonstrates that the amount of vital information being carried this way is minimal.
But how many of those criteria do you think that even Page could get, simultaneously? Two, maybe three? Flying cars are known for being a somewhat difficult engineering problem; that they've been hard enough to prevent partial solutions may turn out to have been a blessing.
And it's not like there aren't other solutions to transportation issues, either.
A lot of applications and environments seem to be built with the assumption that they can add arbitrary complexity to their interface, since they're only going to be used by "experts" who can be expected to know everything of relevance and work through a thick documentation to understand the system. In truth, the "experts" who use your programs are going to also be using a dozen other applications, each with their own piles of documentation (or equal amounts of lack-of-documentation,) and have little brain-space left for the intricacies of your framework. So, they're going to use your system while knowing the minimum possible amount about it; if that system contains traps that cause problems for this kind of user, that's bad design.
> Why are we the way we are? Is Kenneth Eng a schizophrenic whose illness finds expression through florid racism? Or is he a racist asshole who is also schizophrenic?
In psychology there's the assumption that mood disorders and antisocial delusions can be distinguished from non-pathological "being an asshole." I'm not nearly well enough informed about psychiatry to say how this is done clinically, or how quantitative these methods are. But cases like Eng show that as a society we barely even try to make the distinction, or that our ability to do so is profoundly lacking.
There's thousands of homeless people who are on the streets because they're incapable of getting along socially or holding a real job. And a substantial portion of humanity is prepared to leave it at that; they didn't do anything to earn money or companionship, and they don't have what they didn't earn, so all is well. But when you can quite clearly see that one of these people is where they are because of an illness that, in better conditions, would be treated and leave them a productive and happy member of society, that rings hollow. The fact of the matter is that an amount of what we call "motivation," "agreeableness" or even "talent" come down to the functioning of relatively simple, purely mechanistic biochemical processes, which can be subject to incidental malfunction just as you can dislocate a joint or get an ingrown toenail. If you want to assign blame the individual for one and not the other, you have a lot of philosophical explaining to do.
Is this part of some diplomatic tit-for-tat against the Russians over the attack in Syria last week? That's the most reasonable explanation that occurs to me, which is saying something.
Saying "find the jobs that AI can't do" like it's this obvious thing; we haven't the slightest clue what AI can't do in five years. Practically yesterday Go was the go-to example of what computers couldn't do, and now it's the go-to example of how they kick our ass. Well-informed predictions for widespread self-driving car deployment range from "in five years" to "half a century at best." And the jobs that aren't threatened by AI, and that are accessible to most people, are threatened by much "dumber" kinds of automation. Human-facing "empathetic" jobs are often considered safe, but what positions actually need a human, anyway? People are happy to do a bit of extra work to get "expert advice" from a database when it comes to travel, law, or finance; stores are happy to let customers use automated checkout rather than talk to a cashier. Dextrous, highly-physical work is still safe (pending advances in robotics, which seems to move a bit slower), but only until someone figures out a way to offload the dexterity-requiring bits onto a factory, or render the whole thing obsolete. And finally there's second-order effects of the resulting economic turmoil; if most of the middle class can't count on keeping their jobs, not enough people are going to be ordering fancy lattes to pay for your role as a barista. Planning a relatively low-skilled career (anything less than a four-year technical college degree) is walking a minefield.
Us highly-educated technical generalists are probably fairly safe, but not everyone wants to study for 6+ years after highschool- and regardless, they could expect to have to relearn all the applied skills in their chosen field when the tool they originally studied gets replaced by something completely different and orders of magnitude better. The old model of "learn a skill, get a job applying that skill, eventually retire" will no longer reliably work on any point of the scale.
Good odds the Minds all sound remarkably like Alexa. :)