pauljz
Joined 14 years ago
Joined 14 years ago
Clover Health is driving down costs and producing improved health outcomes with a unique health insurance plan. We use sophisticated analytics and custom software to direct our own clinical staff to coordinate care for our members. We have a proven model we're scaling out. We're focusing on elderly and low-income patients that stand to benefit from our model the most. Come improve people's lives and be part of a new way of thinking in an old, trillion dollar industry!
We recently closed our series C and are hiring across a whole bunch of roles in product, engineering, data science, security, compliance, marketing, clinical care, insurance ops, you name it.
Clover Health is driving down costs and producing improved health outcomes with a unique health insurance plan. We use sophisticated analytics and custom software to direct our own clinical staff to coordinate care for our members. We have a proven model we're scaling out. We're focusing on elderly and low-income patients that stand to benefit from our model the most. Come improve people's lives and be part of a new way of thinking in an old, trillion dollar industry!
We recently closed our series C and are hiring across a whole bunch of roles in product, engineering, data science, security, compliance, marketing, clinical care, insurance ops, you name it.
This sounds like a horrifying hack but it's also pretty similar to how Angular's shorthand DI works.
These stations also had a tendency to flood during particularly heavy rains, so it's no surprise that questionable drainage is the culprit.
It's interesting to note that these stations get no natural light where the ferns are growing. It's all manmade light.
The reasoning seems correct, but it'd be nice to have the benchmarks corrected to verify.
I want to do Go as one of our early code engines. We'll probably start off using srclib for early Go support and then build up some bigger features around the compiler tools, go fix, and so forth.
We've got a Dell Venue 8 with an Atom processor lying around that we're using as a test device to make sure things still run well under CPU constraints.
We haven't looked too close yet at one-directory deployment or running off a USB stick, but I just added a sticky note to our backlog to see if we can do it cleanly.
We don't have it pegged for a specific release just yet though.
"NuGet.org does not support permanent deletion of packages, because that would break anyone who is depending on it remaining available. This is particularly true when using the workflow that restores packages on build.
Instead, NuGet.org supports a way to 'unlist' a package, which can be done in the package management page on the web site. When a package is unlisted, it no longer shows up in search and in any package listing, both on NuGet.org and from the NuGet Visual Studio extension (or nuget.exe). However, it remains downloadable by specifying its exact version, which is what allows the Restore workflow to continue working.
If you run into an exceptional situation where you think one of your packages must be deleted, this can be handled manually by the NuGet team. e.g. if there is a copyright infringement issue, or potentially harmful content, that could be a valid reason to delete it."
(Source: http://docs.nuget.org/docs/Creating-Packages/Creating-and-Pu...)
I'm working at Clover Health - a health insurance company where we're using data and technology to improve the health and lives of the elderly, disabled, and chronically ill.