amattn

Collective Health, ( http://collectivehealth.com/ ), San Mateo, CA (Full time, ONSITE only)

We're tackling the employer-sponsored healthcare industry (our favorite analogy is how Tesla takes on several verticals at once, such car makers, dealers as well as the oil industry). We can lower both the first and second derivative of the rising health care cost curve, nationwide. There's some compelling evidence we can do so, if you'd like to chat.

The company just under a year and half old. We punch well above our weight-class with experienced founders, 60+ team members (~ one quarter is engineering), and paying customers.

If you're interested in some challenging work, you should let me know. We've got a ton of interesting problems to solve around distributed systems, data analytics and predictions, complex data modeling, ultra high-availability, security, privacy and more. We're currently looking for experienced SW engineers up and down the stack, back end, infrastructure, data, dev ops, test, generalist, etc.

Our tech stack is a mix of Go and Java components with Angular on the front end. We use a custom service bus to tie our SOA together, microservices style. We love Docker, CoreOS, postgres, riak, automated testing, and continuos integration.

As a company, we're strong believers in transparency, trust and balance. As an engineering team, we believe good code is easy to read and should have a short "time to understanding". We expect all of our engineers to continually teach as well as learn. We also believe that everyone should write good code, yet balance that against the need to ship.

https://jobs.lever.co/collectivehealth

We're super proud of the company mission, engineering culture and tech stack we've put together and would love a chance to explain it all in detail!

Collective Health, ( http://collectivehealth.com/ ), San Mateo, CA (Full time, ONSITE only)

We're tackling the employer-sponsored healthcare industry (our favorite analogy is how Tesla takes on several verticals at once, such car makers, dealers as well as the oil industry). We can lower both the first and second derivative of the rising health care cost curve, nationwide. There's some compelling evidence we can do so, if you'd like to chat.

The company just under a year and half old. We punch well above our weight-class with experienced founders, 50+ team members (~ one quarter is engineering), and paying customers.

If you're interested in some challenging work, you should let me know. We've got a ton of interesting problems to solve around distributed systems, data analytics and predictions, complex data modeling, ultra high-availability, security, privacy and more.

We're currently looking for experienced SW engineers up and down the stack, back end, infrastructure, data, dev ops, test, generalist, etc.

Our tech stack is a mix of Go and Java components with Angular on the front end. We use a custom service bus to tie our SOA together, microservices style. We love Docker, CoreOS, postgres, riak, automated testing, and continuos integration.

As a company, we're strong believers in transparency, trust and balance. As an engineering team, we believe good code is easy to read and should have a short "time to understanding". We expect all of our engineers to continually teach as well as learn. We also believe that everyone should write good code, yet balance that against the need to ship.

https://jobs.lever.co/collectivehealth

We're super proud of the company mission, engineering culture and tech stack we've put together and would love a chance to explain it all in detail!

-----

Collective Health, ( http://collectivehealth.com/ ), San Mateo, CA (Full time, on-site only)

We're tackling the employer-sponsored healthcare industry (our favorite analogy is how Tesla takes on several verticals at once, such car makers, dealers as well as the oil industry). We can lower both the first and second derivative of the rising health care cost curve, nationwide. There's some compelling evidence for it, if you'd like to chat.

The company just under a year and half old. We punch well above our weight-class with experienced founders, 50+ team members (~ one quarter is engineering), and paying customers.

We've got a ton of interesting problems to solve around distributed systems, data analytics and predictions, system reliability, security, privacy and more. We're looking for experienced SW engineers up and down the stack, front end, back end, infrastructure, data, dev ops, test, generalist, etc.

Our tech stack is a mix of Go and Java components with Angular on the front end. We use a custom service bus to tie our SOA together, microservices style. We love docker, postgres, riak, automated testing, and continuos integration.

As a company, we're strong believers in transparency, trust and balance. As an engineering team, we believe good code is easy to read and should have a short "time to understanding". We expect all of our engineers to continually teach as well as learn. We also believe that everyone should write good code, yet balance that against the need to ship.

https://jobs.lever.co/collectivehealth

We're super proud of the company mission, engineering culture and tech stack we've put together and would love a chance to explain it all in detail!

Collective Health, ( http://collectivehealth.com/ ), San Mateo, CA (Full time, on-site only)

We're tackling the employer-sponsored healthcare industry (our favorite analogy is how Tesla takes on several verticals at once, such car makers, dealers as well as the oil industry). We can lower both the first and second derivative of the rising health care cost curve, nationwide. There's some compelling evidence for it, if you'd like to chat.

Our tech stack is a mix of Go and Java components with Angular on the front end. We use a custom service bus to tie our SOA together, microservices style. We love docker, postgres, riak, automated testing, and continuos integration.

As a company, we're strong believers in transparency, trust and balance. As an engineering team, we believe good code is easy to read and should have a short "time to understanding". We expect all of our engineers to continually teach as well as learn. We also believe that everyone should write good code, yet balance that against the need to ship.

The company just a year and a bit old, so early enough for non-trivial equity. Despite that we punch above our weight-class with experienced founders, 40+ team members (~ one quarter is engineering), and paying customers.

We've got a ton of interesting problems to solve around distributed systems, data analytics and predictions, system reliability, security, privacy and more. We're looking for experienced SW engineers up and down the stack, front end, back end, infrastructure, data, dev ops, test, generalist, etc.

https://jobs.lever.co/collectivehealth

We're super proud of the company mission, engineering culture and tech stack we've put together and would love a chance to explain it all in detail!

Collective Health, ( http://collectivehealth.com/ ), San Mateo, CA (Full time, on-site only)

We're disrupting the employer-sponsored healthcare industry (our favorite analogy is how Tesla tackles several verticals at once, such car makers, dealers as well as the oil industry).

We can lower both the first and second derivative of the rising health care cost curve, nationwide. There's some compelling evidence for it, if you'd like to chat.

Our tech stack is a mix of Go and Java components with Angular on the front end. We use a custom service bus to tie our SOA together, microservices style. We love docker, postgres, riak, automated testing, and continuos integration.

As a company, we're strong believers in transparency, trust and balance. As an engineering team, we believe good code is easy to read and should have a short "time to understanding". We expect all of our engineers to continually teach as well as learn. We also believe that everyone should write good code, yet balance that against the need to ship.

The company just a year old, so early enough for non-trivial equity. Despite that we punch above our weight-class with experienced founders, 40+ team members (~ one quarter is engineering), and paying customers.

We've got a ton of interesting problems to solve around distributed systems, data analytics and predictions, system reliability, security, privacy and more. We're looking for experienced SW engineers up and down the stack, front end, back end, infrastructure, data, dev ops, test, generalist, etc.

https://jobs.lever.co/collectivehealth

We're super proud of the company mission, engineering culture and tech stack we've put together and would love a chance to explain it all in detail!

Collective Health, ( http://collectivehealth.com/#careers ), San Mateo, CA (Full time, on-site only)

We're a startup looking to replace health insurance with a system where incentives are aligned for the benefit of both employees as well as employers.

In the long term, we think we can bend the cost of health care across the country. Or in another way of saying it, we can lower both the first and second derivative of the rising health care cost curve, nationwide. We've got some compelling evidence for it as well if you'd like to chat.

Our tech stack is an SOA/microservices mix of Go and Java with an Angular front end. We're strong believers in transparency, trust and balance. We believe good code is easy to read and should have a short "time to understanding". We also believe that shipping is important and there are appropriate times to leverage technical debt.

Some of our company-wide values are transparency and a superior customer experience, from the way we design our products and over-indexing on customer support.

Our eng team is around 9 and we're well funded, but still just a year old, so early enough for non-trivial equity. We've got a ton of interesting problems to solve. We expect all of our engineers to teach as well as learn.

We're looking for experienced SW engineers up and down the stack, front end, back end, data, dev ops, test, generalist, etc. Full list of available positions: https://jobs.lever.co/collectivehealth

We're super proud of the company mission, engineering culture and tech stack we've put together and would love a chance to explain it all in detail!

Doesn't a discount align the incentives better? Is there active resistance to discounts in the investor community? Among angels at least, I personally haven't seen it...

What should one use? FMDB or similar?

The main idea is that there is a nice middle ground between pure SW, low touch SaaS apps and consulting services.

In particular this middle ground can actually help support a SaaS app until it reaches some level of critical mass. The early days of a PaSH app is about risk mitigation. A later stage company can use it to drive revenue up.

It's definitely not new, but it is a model I'm seeing more and more small team SaaS operators adopt.

Customers find it valuable because it ends up being a form of low cost, optimized outsourcing.

One of my favorite examples of this is Instapaper. The app on iOS registers itself as a handler for ihttp:// links so all you have to do is stuff an "i" in front of a URL in Safari and the link opens up in the Instapaper app. Super clever.

This statement is a bit ridiculous:

> "The team built a device dubbed Touchscope that can measure response times to a level of accuracy that is plus or minus 4 milliseconds. It then adds the cloud processing response time to calculate the actual delays experienced by users."

No way the cloud is processing anything having to do with touch handling.

Know your audience. I love that pg uses distributed algorithms as an analogy of how to treat VCs (failure is the default state).

Exercise is a positive return on the time investment.

A good workout (7-30 mins), a 15-30 min bike ride or a 10-20 min run will more than pay off with improved productivity and energy throughout the day.

I'm a huge fan of this one: https://itunes.apple.com/us/app/7-min-fit/id655808630?mt=8

Petitions aren't as effective as campaigns to elect the opponents of those mentioned in the petition.

Even if you fail to prevent reelection, you have a better chance of changing the behavior of the incumbents.

Nothing in go is silly. There are multiple reasons why it's required.

The answer usually given is faster compile times and the removal of semicolons from the language. I don't know the details, but someone new complains about it on the mailing list fairly frequently.

Also having a tool enforced brace style is just plain practical. Less silly arguments/bikeshedding.

I was also a brace on its own line kinda guy, but between javascript and go, I've gotten over it.

It is very, very common to wait until just before an IPO to sue. The strategy is that the defendant will be more willing to settle just to get the lawsuit off the books before the IPO. It usually works against smaller companies.

Google was the recipient of borderline frivolous legal action just before the IPO, but Google didn't bite. In the case of Facebook, I don't expect anything to be resolved pre-IPO, as Facebook has the momentum to deflect nearly anything at this point.

I hate slideshows masquerading as articles. I hate them so much.

- Raymond Chandler, author

- Harry Kroto, chemist

- Anton Bruckner, composer

- Mary Midgley, author, scientist

- Ray Kroc, founder of McDonald's

- Jean Dubuffet, painter

- Marco Olmo, runner

The NBA has a pension system for its players. It more or less does what you talk about. If you play for 13 years or so, I believe you get 50k a year if you retire or something to that effect. The longer you play, the higher the pension payout is.

The architecture reminds me of the PS3's Cell processor, but not as insane.

It's for backwards compatibility with regular old netstrings. It works very well in practice. Implementations are dead-simple and super fast in just about every language.

Maybe it's just me, but how can you embrace Flash but not Quicktime without looking like a hypocrite?

Thanks for the heads up. Sounds obvious when you point it out that way.

An excellent comment by nostrademons on how to be an expert programmer:

http://news.ycombinator.com/item?id=185153

You might consider flipping the question...

Pick a metric: (new user signups, weekly users, whatever) Which will help improve that metric? improved UX/I or more features/better code base.

Back it up with analytics/funnel analysis. If you spend time on your UX/I, and your signups increase, keep doing it. If your increase in signups start to flatten after X iterations, think about another way, such as SEO or coding more features that new customers are asking for.

The classic response is "nothing".

That being said, getting 4 out of 5 economists to agree on something doesn't mean it's right. Most economists will tell you that public policy works best when you have the capability/political will to iterate on solutions. Not unlike a startup really.