1,116 karma · joined October 16, 2011
Would love your feedback on it!
https://query.wikidata.org/#SELECT%20%3FpresLabel%20%3Fcompa...
We're currently looking for several mid/senior engineering positions (android, iOS, frontend, backend, infra/platform, sre) across our engineering team. More descriptions can be found on our jobs page (below). If you're in the area I'd love to just grab coffee regardless of whether or not you're actively looking to move -- I love talking to other passionate, driven people about what they do.
Our stack is native Android (Java) and iOS (Objective-C), our API is served in a Ruby on Rails monolith and Scala services, on top of MySQL, Cassandra, ElasticSearch and Spark. Our frontend is mostly Backbone + React, although some more complex state we are moving to Redux.
Jobs: https://www.wellframe.com/jobs Also feel free to reach out to me at nam@wellframe.com!
What do people think of the format? I have off and on been thinking about a format where the video is the main highlight, but is supported, like this one, with links and other media to make it a more engaging experience. Are there other use cases that you think this would be conducive for?
Much of our container building includes fetching dependencies from various package managers which rarely changes across builds, yet takes up the majority of the build time. Most of the time thats good enough, but for cases where we want to immediately deploy a fix, it can be quite frustrating to having to spend all this time seemingly unncessarily.
Edit: Docker 1.13 has the new --cache-from option so it seems relatively straight-forward to do I guess?
At Wellframe, we are building an intelligent care-management platform that allows health plans and care-delivery organizations to better manage large populations of complex patients. Because the most clinically complicated cases in a patient population tend to drive a majority of the costs, even seemingly small improvements in these patients’ well-being have dramatic benefits for the care provider. Wellframe focuses on improving patient health by providing personalized and adaptive care programs for people trying to recover from or manage serious health problems. We use the health data we collect in order to intelligently allot care resources to the specific needs of patients, paying special attention to the most-critical patients. Through clinical studies and working with large healthcare payers, we have seen that our platform improves patient outcomes, increases the capacity of care management teams and reduces costs of the care provider. We have a relatively small engineering team at about 10 engineers. What makes us unique is that we have a full time clinical team of doctors that work with us to break down clinical science so that we can build it back up into personalized and adaptive care programs.
We're currently looking for several mid/senior engineering positions (android, iOS, frontend, backend, infra/platform, sre) across our engineering team. More descriptions can be found on our jobs page (below). If you're in the area I'd love to just grab coffee regardless of whether or not you're actively looking to move -- I love talking to other passionate, driven people about what they do.
Our stack is native Android (Java) and iOS (Objective-C), our API is served in a Ruby on Rails monolith and Scala services, on top of MySQL, Cassandra, ElasticSearch and Spark. Our frontend is mostly Backbone + React, although some more complex state we are moving to Redux.
Jobs: https://www.wellframe.com/jobs Also feel free to reach out to me at nam@wellframe.com!
At Wellframe, we are building an intelligent care-management platform that allows health plans and care-delivery organizations to better manage large populations of complex patients. Because the most clinically complicated cases in a patient population tend to drive a majority of the costs, even seemingly small improvements in these patients’ well-being have dramatic benefits for the care provider. Wellframe focuses on improving patient health by providing personalized and adaptive care programs for people trying to recover from or manage serious health problems. We use the health data we collect in order to intelligently allot care resources to the specific needs of patients, paying special attention to the most-critical patients. Through clinical studies and working with large healthcare payers, we have seen that our platform improves patient outcomes, increases the capacity of care management teams and reduces costs of the care provider. We have a relatively small engineering team at about 10 engineers. What makes us unique is that we have a full time clinical team of doctors that work with us to break down clinical science so that we can build it back up into personalized and adaptive care programs.
We're currently looking for several mid/senior engineering positions (android, iOS, frontend, infra/platform, sre) across our engineering team. More descriptions can be found on our jobs page (below). If you're in the area I'd love to just grab coffee regardless of whether or not you're actively looking to move -- I love talking to other passionate, driven people about what they do.
Our stack is native Android (Java) and iOS (Objective-C), our API is served in a Ruby on Rails monolith and Scala services, on top of MySQL, Cassandra, ElasticSearch and Spark. We are especially focusing on expanding our frontend team as we see significant growth on that side of the product. We are mostly Backbone + React, although some more complex state we are moving to Redux. It's a very exciting time for the frontend, as we are planning to grow both in scale in terms of patient populations, as well as product use cases that require diverse interactions. It is super rewarding to see our product affect real people's lives and the opportunity to reinvent this massive industry is enormous.
Jobs: https://www.wellframe.com/jobs Also feel free to reach out to me at nam@wellframe.com!
At Wellframe, we are building an intelligent care-management platform that allows health plans and care-delivery organizations to better manage large populations of complex patients. Because the most clinically complicated cases in a patient population tend to drive a majority of the costs, even seemingly small improvements in these patients’ well-being have dramatic benefits for the care provider. Wellframe focuses on improving patient health by providing personalized and adaptive care programs for people trying to recover from or manage serious health problems. We use the health data we collect in order to intelligently allot care resources to the specific needs of patients, paying special attention to the most-critical patients. Through clinical studies and working with large healthcare payers, we have seen that our platform improves patient outcomes, increases the capacity of care management teams and reduces costs of the care provider. We have a relatively small engineering team at about 10 engineers. What makes us unique is that we have a full time clinical team of doctors that work with us to break down clinical science so that we can build it back up into personalized and adaptive care programs.
We're currently looking for several mid/senior engineering positions (android, iOS, frontend, infra/platform, sre) across our engineering team. More descriptions can be found on our jobs page (below). If you're in the area I'd love to just grab coffee regardless of whether or not you're actively looking to move -- I love talking to other passionate, driven people about what they do.
Our stack is native Android (Java) and iOS (Objective-C), our API is served in a Ruby on Rails monolith and Scala services, on top of MySQL, Cassandra, ElasticSearch and Spark. We are especially focusing on expanding our frontend team as we see significant growth on that side of the product. We are mostly Backbone + React, although some more complex state we are moving to Redux. It's a very exciting time for the frontend, as we are planning to grow both in scale in terms of patient populations, as well as product use cases that require diverse interactions. It is super rewarding to see our product affect real people's lives and the opportunity to reinvent this massive industry is enormous.
Jobs: https://www.wellframe.com/jobs Also feel free to reach out to me at nam@wellframe.com!
1. What is a reasonably sized project? I.e. often times two hours is not enough to produce something of substance/complexity, yet asking the applicant to do more becomes prohibitive. 2. I see a bunch of people asking candidates to do greenfield applications, while virtually all work most future workers will do is refactor and maintain. The latter however requires additional time investment to get to know an existing system/codebase.
How are you guys handling those issues, and trade-off time complexity against insight value?
http://nambrot.com/posts/24-semi-nomadism-a-way-of-life/
Tl;DR: Post-college I negotiated a remote deal and spent the last months slow travelling, while still producing good work. I think logistically, everything works out very well, it really isn't a financial question at all (if you are a half-decent developer) unless you spent most of your travels in expensive Western cities. I prefer this over full-time travel.
However, the worst thing ended up being the transient nature of travel, no matter how slow you do it. If you are a person that does well by him/herself, then that's fine, but having a stable and sustainable social life has become a greater priority for me.
We are working towards a solution that takes in data to improve health outcomes: https://www.wellframe.com
It's a super exciting space and time to be in, but it's also super challenging, so we are hiring! Let me know if you have any questions!
http://pragdave.me/blog/2007/12/30/pipelines-using-fibers-in...
What is everyones experience with just using Backbone Models as your data source. We currently just pass the backbone models as props, but include a mixin that forces re-renders by listening to the model's change event.
I can see how at very large scales you'd want to move away from that, but for us it works great so far as we don't have to think that much about events, components are still just simply representations of the model in a functional way.
I'm afraid of a world in which Lyft is forced to quite (as you only so long sustain on VC money), and Uber then abusing it's monopoly power.
The difference to the existing cab market is the extraordinary scale and growth Uber posses. They can simply afford to undercut everyone's prices for the short term with their billion of dollars in VC money.
I do think that something like OP would be too formal, as it doesn't give you the flexibility to deviate, which is why I think a more liquid network of at the start just several locations would work.
Btw, I liked your approach above very much, if you have a majority of the group do that (allowing individuals to divert), this could totally work
I think having a group or network of similar minded people would greatly help.
I have actually thought about this a lot, what if there is a network of airbnbs/hostels around the world which a group of remote workers agree upon to be more concentrated? I think co-working spaces do much of it right now, but it can always be improved upon.
I love Ruby and the Parallel gem (https://github.com/grosser/parallel) makes certain stuff easier, but I feel like every month or so I spend hours just trying to figure out the proper way on how to parallelize