Clover Health | San Francisco, New Jersey | ONSITE | Full time
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 | San Francisco, New Jersey | ONSITE | Full time
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.
If you're wondering why comments are a factor at all, and aren't just discarded by the lexer, remember that comments in JS are preserved and available to things like `Function.prototype.toString()`. I've seen this used to do evil multiline string support a few times. Slap the multiline string or template into a comment inside a function and then have another function that toStrings it and strips the boilerplate.
This sounds like a horrifying hack but it's also pretty similar to how Angular's shorthand DI works.
it's incredible that that project has 11,000 commits, a huge amount of effort has gone into it but the code is really unpleasant to read. I feel like I must be missing something about FOAM - who is using it and why?
The success of an endeavor is proportional to the number of shitty hacks that have come before it. Sometimes this it true in a literal sense -- sometimes a project consists of shitty hacks. But the astute reader will notice that a hack is only known to be shitty because someone did it, and had the courage to make their example public.
Do we reward their courage? No. We act like cliquish teenagers and rip them apart.
I don't mean to single you out. But this subthread consists of a developer at Amazon, an unknown, and a founder -- the very types of people I wanted to respect -- yet the content is little more than "Look at how stupid these people are." What kind of example are we setting here?
Be excited about X! Whether X is FOAM, Javascript, COBOL, C++, Python, Erlang, Scheme, NPM, ASDF, Vim, Stallman, or a song. Be happy. Be amused. Be anything but bitter.
In this instance, FOAM shows what's possible. Is it necessarily a good idea? Who cares! We've learned something new! Be excited!
How certain are you that an idea that strikes you as bad is actually bad? For every possible circumstance? What about with a slight tweak? In fact, "An idea that seems bad" is the short definition of "startup."
Most ideas that seem bad are, in fact, bad. But it's important to fully explore the problem space before dismissing them, else you'll dismiss Facebook.
This subthread is about a software technique, not a startup idea. But is it really such a different domain? Would the idea of Python have survived if it had been introduced in the era of Multics? It wasn't a compiled language, so it couldn't hope to survive back then. Yet its time was coming, whether or not it would have been dismissed at the time.
"Under what circumstances could this be a good idea?" That's the valuable question. And if you also have a good answer to "Why now?" then you may be onto something. In fact, you might be one of the first people to notice that an idea has flipped from bad to good. Seems like a pretty powerful position.
It seems like most influential work started as a hack. (TeX is a notable exception.) So if you want to do influential work, be delighted by hacks. It'll make them easier to explore, and you might end up in a position few others realize is valuable.
Most everyone agrees with you in general about the usefulness of "trashing other people's work", but I think your response here is disproportionate to the circumstance.
For what it's worth I was asking a genuine question, most experimental projects don't get 11k commits so I assume that people are actively using it - my question is, given the plethora of alternatives available, what is it about FOAM that leads people to use it?
I shouldn't have said that the code was unpleasant, which is obviously subjective, but I should have said "the code style is quite unusual for JS", which it is. It was certainly not my intention to "trash their work".
This isn't a totally new phenomenon either. I used to ride this stretch of the Metro to work every day back in 2009-2012, and I remember seeing these plants back then too. At the time they hadn't really taken hold at Cleveland Park, but Woodley Park was overrun with them.
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.
In the final example where he switches to int32 for Go (after "Let's make it use int32 consistently and try again"), he runs gopherjs twice instead of running go and gopherjs. I hope that's a typo.
The reasoning seems correct, but it'd be nice to have the benchmarks corrected to verify.
I really like Go and have definitely felt there's room for great integrated tooling there.
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 want to make sure it's light enough to run on netbooks/travel computers.
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.
Yep! It's in the backlog; to start we'll probably use srclib [1] under the hood to provide the code intel bits, and we'll do some special UI wrappers for bundler/gems.
We've been working hard to make srclib's backend more powerful, and we've just started to build features that take advantage of the new backend. I've sent you an email, and we'd love to work more closely as srclib nears v1.0.
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.
https://www.cloverhealth.com/en/about-us/careers