Hacker Newsnew | comments | show | ask | jobs | submit | mkopinsky's comments login

What happened here? Why was the title changed back to NPR's more clickbaity version?

To bait dem' clicks!

It's not about making a collective threat, it's letting management know that the new conditions are making you consider options "up to and including departure", and that you think the other devs may be in the same boat.

Just make sure you don't talk for other people (for example naming your peers). Otherwise i strongly agree.

They have a resilient, stable API. We use it for a number of clinical trials evaluating incentives for walking, and it works fairly well. Better than most of their competitors.

-----


Step counts are fairly accurate. From the Flex less so than their other devices, but still not too bad. Nike Fuelband is pretty bad. Pretty good figures at the link below.

Case MA, Burwick HA, Volpp KG, Patel MS. Accuracy of Smartphone Applications and Wearable Devices for Tracking Physical Activity Data. JAMA. 2015;313(6):625-626. doi:10.1001/jama.2014.17841. http://jama.jamanetwork.com/article.aspx?articleid=2108876

-----


There's a big difference between a court filing and lawyerly nastygram. By sending inappropriate nastygrams you're not wasting the court's time.

-----


I can see why the judge would see this as an important difference, but I don't see that it actually is one. Why do I care which option wastes the court's time?

-----


How about Ctrl-W to just close the Gmail tab?

-----


That's actually a great point.

-----


How do you keep track of the technical debt? Ticket system?

-----


    //TODO:

    //FIXME:
;)

-----


Wink all you like, but I get a lot of value from greppable, well written fixmes directly in the source they pertain to. If I’m working on a feature and I discover some odd misbehaviour, there is often a comment right there in the source, explaining precisely what I need to do next.

-----


Agreed. A # TODO: or # FIXME: lives in the code for all to see. I use ticketing & project management tools as well (Pivotal, Trello, others), but these tools are more useful for "X needs implemented and has measurable priority or Y needs fixed ASAP".

Things that we know need to be addressed, but the priority level is "when we have time" are better served living in the code. They tend to get lost in project management and ticketing systems, whereas they live until the code dies if they are in the code.

-----


If it is something expedient and thoroughly embarrassing I use

//kludge

-----


Shameless plug: https://github.com/bglusman/debt_ceiling

-----


No need to track it, just default on the debt when it's too much to bear.

-----


FYI your linkedin profile has very little for regular linkedin users - might want to open your permissions up a bit.

-----


Way to Health, University of Pennsylvania - Philadelphia, PA Chronic illness and the decisions people make and act upon – from their activity level to taking medications or smoking – drive the vast majority of the $3 Trillion in US healthcare costs. Our team has achieved breakthrough results in changing the behaviors that determine health outcomes, such as doubling adherence to medications that keep people healthy and out of the hospital, and establishing new insights into patient engagement. These results were enabled by the Way To Health platform, a unique technology asset now poised to move beyond research into broader clinical applications. The role we’re looking to fill is critical to expanding our impact. We need someone who can not only work with our team of internationally recognized thought leaders to identify and implement functionality and designs making interventions more effective, but also has the ability to evolve Way to Health into a scalable clinical platform that can be deployed efficiently in larger populations. The Way to Health developer role offers the opportunity to make a meaningful difference in patients’ lives and their health outcomes. This role also affords the right candidate a great deal of autonomy in both how you do your work and in crafting a vision for the technology. We’re looking for team members who love problem solving and finding better ways to get things done. Specific responsibilities include: * Collaborating with faculty to translate cutting edge research protocols into functionality for patient engagement and behavior change * Developing new features for individual interventions and for the platform * Working with the development team to iteratively determine the best way to meet project goals in a timely, robust and scalable manner * Crafting architectural approaches to drive down the cost of feature development and deployment * Designing new methods of information delivery and display for increased patient comprehension and response * Diagnosing reported issues, identifying the source of problems, determining the best path to resolution and implementing fixes * Evolving and supporting QA processes, writing automated unit and functional tests for new features, documenting work clearly, and finding ways to continuously improve quality * Participating in an agile development process (we use a modified version of Scrum) * Working with infrastructure providers to plan for future needs and ensure timely, efficient and reliable delivery Older tech stack is symfony/PHP/mysql, but we're migrating more and more to our node/mongo stack. More info and application at https://careers.peopleclick.com/careerscp/client_pennmedicin... Feel free to email me at myHNusername at waytohealth.org with questions. (No recruiting agencies, please.)

-----


Right. Because there's no US law that covers storage of personal data by health providers. And there's no legal penalties for things like this.

(Hint: http://www.ecfr.gov/cgi-bin/text-idx?SID=9e10f619aa05225aef1... Subpart C—Security Standards for the Protection of Electronic Protected Health Information)

-----

More

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: