"Practicality beats purity"
813 karma · joined December 1, 2013
I used ML techniques to help smooth over some of the difficult parts (there are many difficult parts). The hardest cases are ambiguous names, for instance delineating Hispanic vs. Puerto Rican naming conventions (they're different). The fundamental approach involved pushing all ambiguity up to the end user, so they always have the option to correct the system.
You shouldn't ever use first/last name fields, because they force users to adapt around your system (many names don't follow this structure). A long unstructured text fields is best, because it can accommodate nearly anyone who's name can be spelled with unicode. Finally always check your interpretation of a name with the person in question, seeing as they're the end authority.
>>> wiki_list = []
>>> wiki_list.append(wiki_list)
>>> print(wiki_list)
[[...]] >>>list(zip(*[(1, 2, 3), (4, 5, 6), (7, 8, 9)]))
[(1, 4, 7), (2, 5, 8), (3, 6, 9)]Digging a little deeper it appears like McDonalds may have actually invented the sauce to appeal to the Dutch market, where fritessaus is popular (instead of tomato ketchup). Because McDonalds is American, their take on fritessaus grew into it's own thing called "American Fritessaus," or simply "American Saus."
https://www.hollandsupermarket.eu/remia-fritessaus-american-...
http://www.typicaldutchstuff.com/ahamericanfritessaus-pi-364...
https://cf.geekdo-images.com/camo/271763ae14b82c0f612b6b9f61...
This is what I'm referring to.
Digging a little deeper it appears like McDonalds may have actually invented the sauce to appeal to the Dutch market, where fritessaus is popular (instead of tomato ketchup). Because McDonalds is American, their take on fritessaus grew into it's own thing called "American Fritessaus," or simply "American Saus."
American Sauce in the Netherlands comes to mind.
The reason why I bring this up is that antimicrobial resistance is an externality of widespread antibiotic usage. Unfettered access to all drugs would probably accelerate antimicrobial resistance, because people tend to overuse/abuse antibiotics when they have the freedom to.
(Not trying to be mean/inflammatory/pedantic, I'm genuinely curious how HN would reconcile these stances.)
There are lots of strange physiological links that aren't necessarily logical, due to the imperfect nature of natural selection (it strives for the local optima and "good enough," over the global optima). For instance it's well documented that consciously smiling improves mood, even though the causality is "backwards."
Accurately cleaning the input data proved to be extremely important, because there's a tremendous amount of "noise" at the individual level when dealing with living organisms, so lots of high-quality data is necessary to tease out relationships. Establishing causality was also important, considering the potential for confounding variables.
It also gave me a chance to brush up on my React/front end skills, but that was more ancillary.
Dynamic typing means that types can be changed arbitrarily at runtime, compared to statically typed languages which define all types at compile time.
Strong/weak means that type coercions rarely/never happen automatically. For instance JS has some interesting behavior enabled by weak typing `[] + [] -> ""`. Whereas Python rarely coerces things for you. The division operator in Python 2 was strongly typed, while they changed it to weak typing in Python 3 (inline with the practicality vs. purity convention).
I always treated this a bit like single underscore private functions/methods, i.e., follow a convention that produces code that's easy to reason about, even if it's not strictly enforced by the language/compiler. So in practice this equates to separating out modules that mutate global state, and placing the majority of logic in "strict" modules that only declare a bunch of "pure" classes/routines. So the "non strict" code is really just a thin layer of wiring gluing everything together. For instance my Celery task files tend to be very thin.
That's changing with the advent of progressive web apps. It's possible to write web apps now that are robust in the face of network problems, e.g., the web app renders and is functional even without a connection.
Pretty much, fortunately it's very rare. However you shouldn't eat sport caught shellfish without first checking for local warnings regarding harmful algal blooms.
At least in the US/Canada all store bought Seafood is thoroughly screened for this specific problem, because ASP was discovered in Canada after a mass poisoning event in the late 1980s.
Alfred Hitchcock's film The Birds was loosely based on an invasion of tens of thousands of delirious seabirds thought to be suffering with ASP in Santa Cruz in 1961.
However research has shown that some specific types of long term memories can be still be made. For instance if an amnesiac individual is asked to draw the same image repeatedly, they may still improve in speed and efficiency without any apparent conscious memory of having drawn the image before.
Rediscovery of "extinct" species is common place, because of the inherent difficulty in proving that all individuals of a given species are dead. Combine this with the robustness of biology, allowing species to quickly boom under favorable conditions, and then false extinction ends up happening more often than you would probably suspect. It's normal for many healthy populations to fluctuate wildly around a given carrying capacity. r-selected organisms are particularly notorious for having like 95% of the population die off regularly, and then bouncing back in a few years.
In the case of the thylacine, it's a macro organism so it probably has a higher profile when compared to a small gecko. So the likelihood that they're still extant probably isn't quite as high, unfortunately.
Just a quick google search found these:
https://algorithmia.com/product
(I'm not affiliated with them in any way, and haven't ever used their services.)