Nope. Any PillPack developer can look up any customer in seconds. Other employees have more limited access, but generally quite a bit of access. Access is logged in production, but developers can also get a clone of the entire production database pretty easily.
That's not necessarily a problem or a HIPAA violation, depending on how it's used, although the opportunity for abuse exists. They cover their ass with annual HIPAA training.
Form Health | Boston | REMOTE/ONSITE | Senior Software Engineer
Form Health is medical weight loss. Delivered through your phone.
Obesity impacts 40% of the US adult population, but only about 1% of patients receive medical treatment for their disease. Form Health makes medical treatment available to everyone.
Losing weight is hard, the more so because Overweight and Obesity are conditions that change the basic functions of the human body. Our doctors help set it right.
Form Health helps people lose weight in a medically-supervised environment. Our physicians look at the whole patient and develop an individual, medical approach, including medications when appropriate. All of this: virtual MD visits, interactions with Registered Dietitians, group interactions, meal tracking, and more, is delivered with incredible discretion via an app on the patient's phone.
Form is small but growing. We’re a mission-driven, patient-focused, seed-funded team who believe in developing hypotheses, experimenting, shipping continuously, and learning and iterating quickly. You’ll report to our VP of Engineering, helping to build a world-class product, service, and team.
React Native, ReactJS, AWS, GraphQL, PostgreSQL
Things that are important to us:
- Creating a welcoming and safe place for patients
- Protecting patients’ privacy and the safety of their data
- Simplicity and quality
- Continuous learning and improvement
- Minimizing waste
- Growth and scalability
The question isn't whether problems should be solved using engineering strategies -- in general, I agree that they should. Rather, it's whether everything in life is an engineering problem.
Here's an example: When I was 18 I wanted to listen to some new music. This was when we got our music on CDs, and we didn't have algorithms like iTunes Genius to help us find something we might like. I bought something just because I liked the cover art. Fortunately I ended up liking the album. (It was this one: http://rateyourmusic.com/release/album/dink/dink/)
IF engineering strategies are not always inappropriate, does that necessarily imply that they are always appropriate?
I think the point of the post is that there's more to life than "frameworks". Not every problem is worth solving, and not every problem is an engineering problem.
You’ll collaborate closely with our clients and our world-class development team to craft gorgeous, intuitive experiences that people are thrilled to use.
You’ll teach. You’ll learn. You’ll create.
You’ll build and lead a world-class design team.
You should have experience in web and graphic design, typography, UX, and mobile. Ideally you’re an expert at HTML5, CSS3, Sass, and maybe even some JavaScript or CoffeeScript.
ABOUT TERRIBLE LABS
Terrible Labs is a Boston-based consultancy that builds web and mobile apps for some pretty awesome clients. We specialize in Ruby on Rails and HTML5. We just got started in 2011 but have already built a great brand and have big plans for the future!
We offer all employees a competitive salary, 100% paid health and dental insurance, a take-what-you-need PTO policy, a gym membership, RailsCasts Pro subscription, Intelligent.ly stipend, and we'll pay your smart phone bill (even though we don't expect you to be on call 24/7).
I've used Rails for almost 5 years. I've implemented Stripe, KISSmetrics, and Bootstrap each on at least two different projects.
Even with my experience, I'd estimate that using a pre-packaged app like this would save me at least 3 hours of (relatively mundane) work. It's worth every penny.
I could easily see this taking a day or two for someone with less experience.
I think truthiness and validity/completeness are different things. Overloading truthiness sounds to me like a recipe for confusion and less expressiveness.
That said, I'm all for experimentation and would love to see this idea tried.