Life is cyclical. Recognizing that allows you to optimize your personal and professional activities, maximize fun, and make the biggest possible dent in the universe.
People sometimes ask me how I approach work-life balance, so I thought this would be a good opportunity to share.
I find ninety minute bursts of productivity with renewals in between works very well for me.
My ideal work day: I walk my child to school (a little hit of sunshine and light exercise first thing), followed by checking email and then a quick team video call. After dealing with any pressing issues raised on our team standup, I try to take a short break where I get up and out of my home office for a few minutes. After another period of ninety minutes or so of work, I break for lunch. A third work period, then an afternoon workout (usually a run). A fourth period of work on days when family commitments don’t preclude it, and then I try to get to bed at a decent time to repeat tomorrow.
On “rest days” when I’m not running I will try to spend my mid-afternoon renewal time either reading or napping. Either way, I stay out of my office and away from my laptop to avoid diving immediately back into work and problem solving mode.
Getting to bed at a decent time is where I most often fail. Lots of temptation to get back into work mode after getting the kids to bed, when I should be settling in for the night.
What works for you?
The latest slides are available on Slideshare:
Changes to the slide deck include:
- Updated Health Graph platform stats for growth in users, partners, and data
- Added links to set-based APIs (after removing links to now-deprecated corresponding discrete measurements)
- Asked all developers to please read through and follow the Health Graph Best Practices as they develop and prepare to deploy their integrated apps, services, and devices
Please take a few minutes to review the slides and let us know if you have any questions. Thanks and happy hacking!
Cross-posted from the Health Graph blog.
I don’t believe in immediately jumping on the political bandwagon as soon as something bad happens. I’ve been biting my tongue, but given the continued shortsightedness and frankly extremely irresponsible rhetoric from many this week, I feel the need to point out some cold hard facts.
There are multiple fundamental disconnects from reality in much of the media coverage and popular dialog every time something like the tragedy at Sandy Hook is carried out by a criminal.
Ask any policeman or policewoman (we have several family and friends who serve) and they will confirm:
- Bad guys will get weapons, period.
- Bad guys don’t care whether the law says the weapons they want are legal or not.
- Bad guys will target “gun free zones” for the same reasons wolves prey on weaker animals.
- Police are not here to protect us, there aren’t anywhere near enough of them in any sort of democratic society we’d want to live in; rather, the police are here to draw chalk outlines and catch the bad guys after the bad guys have already broken the law.
- Responsible citizens must have the ability, and that includes weapons, to defend themselves when attacked.
If you consider that this was a “gun free zone”, as was Columbine, as are the vast majority of such crimes, and you really think about it, it is obvious that “gun free” does not work.
I believe in the right to defend my family and others. Without that right, all the other things in our lives are subject to removal. In that sense, the Second Amendment truly does acknowledge our “first freedom”. The inalienable right to self defense enables all other rights, freedom, and liberty.
If you don’t believe that a little sign or a law will make bad guys leave their weapons at home, then the only rationale response is to allow responsible, legally vetted adults to carry and defend themselves and those who cannot.
We already trust our childrens’ lives to school officials including administrators and teachers. Why not allow them the one tool that will help ensure bad guys are stopped from harming our kids? And by allowing them to carry, and telling the bad guys that schools are not soft targets, why not end the vast majority of school massacres before they ever start?
It’s the only sane thing to do in this whole insane mess.
While this post is targeted at attendees of the September 2012 Quantified Self conference in Palo Alto, even if you’re not attending you still might find some useful Health Graph information and development tips.
Welcome Quantified Self attendees and hackers! You’re in for a great weekend of learning and networking. And hopefully plenty of fun!
Here are the sessions where I’ll be representing RunKeeper:
- “Hacking APIs” breakout session, Saturday 10:30AM – Beau Gunderson (@beaugunderson) of Singly and I will be discussing APIs for self quantification and hackery. We hope to have a lively discussion with you and each other, examining APIs for QS from every angle.
- RunKeeper & Health Graph office hour, Saturday 1:30PM – I’ll be available to discuss Health Graph development and answer any questions you may have.
I will also be attending as many of our partners’ sessions as I can, while hopefully having lots of time to share ideas and make new connections. Please shoot me a tweet (@billday) if you’d like to get together at the conference.
To prepare for the conference, or begin using the Health Graph directly on your own, you should start by watching this high level overview of the Health Graph platform:
For a quick primer on developing with the Health Graph API, click through the more technical presentation below:
All Health Graph partners are required to follow the Health Graph API Policies.
You can access more technical details on the RESTful Health Graph API by clicking here. Experiment and prototype with the API using the Health Graph Developer’s Console (click here to load the console).
When you’re ready to start your app in earnest, visit the RunKeeper Partner page and click “Connect To Our API“. From there you can fill out the form to register your new Health Graph integrated app, service, or device.
Click here to learn about authorization removal callbacks before providing your callback URL on the form. If you will be reading data out of the Health Graph for accounts other than your own app registering account, you should also request Read permission on the form, being sure you give a detailed explanation of what you will do with that data once you’ve accessed it. Likewise, if you would like to ask users for permission to retain their Health Graph data across deauthorizations and/or edit health information for authorizing users, please request permission(s) on the form.
Need some inspiration to get your developer juices flowing? Check out some of the applications built and deployed using the Health Graph API, available from the RunKeeper Apps page (click here). You can also access an archive of third party libraries, wrappers, and bindings which might make your Health Graph API-based development easier by clicking here. And there’s more information on how app and library partners are taking advantage of the Health Graph via our Health Graph partner profiles series on the blog.
One more tip: Click here to learn how to export your own user data from the Health Graph; useful for programmable self hacks as well as backups and parsing your data to re-upload into a test account via the Health Graph API.
Now that you know how to use the Health Graph, go build something great!
Cross-posted from the Health Graph blog.