(this is page 20 of 121)





Latest

Over the last 3.5 years I've logged almost 3,000 miles with my Nike+ system, a low-cost pedometer that uses the iPod/iTunes ecosystem to submit my runs to a site for online competitions and other interesting data-oriented tasks. I have come to rely on the Nike system so much that if I find myself without it, I won't run. By just collecting data and transparently uploading it to a place where I can go back and look at it, it has managed to alter my behavior.

This trend appears particularly powerful for health related issues. The Withings scale (WIFI and with the ability to broadcast your weight to various social networks) seems to be popular among the folks I follow on Twitter and the always "almost here" Fitbit promises to track all sorts of activity related stuff for subsequent analysis. As dorky as it sounds, it would appear that "what gets measured gets done" at least by a certain part of the population.

Today I ran into an ingenious mass market personal telemetry device that appears suited for children: simple, stylishly designed (but easy to to personalize), and best of all, cheap, the S2H Replay is essentially a low budget Fitbit/Nike+ system that fits inside of a color rubber wristband and tracks activity. What may make the Replay the Flip of personal telemetry devices though is that rather than relying on any sort of Wifi signal or a complex base station, it just emits a code that details the amount of work you've done to the site where you are then able to earn points.

Fans of the fully automatic will think of this as an ugly hack that disqualifies the Replay from the pantheon of early personal telemetry devices— after all, the user has to remember to go enter his code to claim credit for the exercise done. However, if my experience with the sometimes buggy Nike+iTunes combination is any indication, users will be very motivated to "get credit" for work done.

Which incidentally is where S2H performs its second great hack: getting users to compete for prizes in the forms of certificates to various different e-tailers. Think of it as a credit card reward program used for good.

I'll have more to say in a few weeks after I've used my own two guinea pigs for a test (boys, 7 & 4), but for now I sure am glad that there are so many creative approaches being taken towards kickstarting the personal telemetry revolution!

(And here is the Russell Davies's excellent review that tipped me off to the existence of this neat gizmo).

Comments Permalink

Pycon 2010 rocked

Pycon has always been a fantastic conference— especially given that it is run entirely on the backs of volunteers. Much better than most paid for-profit conferences for sure.

I've posted the notes and slides from my closing keynote this morning— a small contribution to this excellent conference. If you are interested in reading how it was supposed to go (and I think I got close), feel free to go read it.

And for those that prefer to listen to it, here is the video.

Looking forward to PyCon 2011.

Comments Permalink

I am doing the closing Pycon keynote this morning, so apologies to anyone who isn't there (feel free to skip this post, though I'll put up the notes and slides later today if you are interested).

To the other thousand of you, you are here because you're not listening. You've gone to The Google to figure out who this guy is and why he is so animated this early on a Sunday morning. Go back to listening and I promise by the end of the talk— agree or disagree— you'll know why.

Trust me, The Google will still bring you back here after the talk.

For those that just won't take no for an answer, who'd rather listen to frozen me talking to you from the bitstream of the Internet instead of live and in the flesh, I just have one more thing to say:

Python rocks because you do. As a community you do an amazing job of growing, maintaining, and evolving what I think is the greatest treasure that open source has delivered. Whether you agree or disagree with the argument in my talk, I hope at least you'll be entertained.

This talk is for you guys. Python works because you do.

Thank you.

Now go listen!

Comments Permalink

During my last job at HP, I got a chance to get up close and personal with a few big partnerships with other tech companies which had similar goals with respect to specific product roadmaps. In all of these cases, the point of the relationships was to work together on projects that would result in a bunch of software that would ultimately be better for both companies.

Now hold that thought for a moment.

Over the last few days I've been having a blast at Pycon, the main annual conference behind the Python programming language. It's fantastic to see how far it has come over the last two decades, almost entirely on the back of committed volunteers who burn nights and weekends maintaining and building a high quality software project which is so critical to many industries, and especially for the future of the open Web OS.

And yet, there are still a few warts on Python that could benefit from the focused effort of sponsored work. Of all of the big companies, Google has done the best job to date here— sponsoring projects like Unladden Swallow, a needed speed boost. There are other big companies that occasionally sponsor Python work, but not as many as you would think— especially not given how strategically important the language is to them.

There are two things that hit me this conference that might provide a solution. The first is that as serious as these warts might be, it would take relatively little manpower to remove them. Specifically, paying for something like 2 engineers for a sustained year of 100% work could go a long way towards solving speed, packaging, or concurrency issues in a really deep way. The second observation is that by the standards of big company budgets— and specifically as applied to the kinds of partnerships I mentioned above— this is an insignificant rounding error when it comes to dollars spent— even for really senior folks.

Instead of spending the money on needlessly flying executives back and forth to regurgitate the same 20 slides over the "partnership possibilities," I wonder whether there isn't the possibility or reallocating these Steaks&Strippers budgets to fund open source wart removal as a kind of joint venture where each side dedicates a couple of engineers to something that would benefit both companies and allow meaningful longterm partnerships to develop.

It would take more thinking to see exactly how this could be fit into something like removing the Python GIL (a impedance to really good concurrency and multicore support), but I'm sure it could be done. Each big company usually has its cash cow business model: Google and web advertising, Intel and chips, HP and ink, etc. And each of these cash cows often generates a whole host of "ecosystem partnerships" that companies go into to ensure the long-term continued growth of X, where X is whatever makes the cash register continue to sing.

In effect, newer projects like Android may provide the perfect test for these types of partnerships. Except of course that a mobile OS is pretty strategic to most big tech companies which is usually code for more Steaks&Strippers and less meaningful partnering.

Something to think about.

Comments Permalink

It's been 4 years since I left Emacs for Textmate for many of the same reasons that I left desktop Linux for OSX— I was just tired of configuring everything instead of having it just work.

That said, Textmate's slow development cycle has been bugging me as of late. It is a terrific text editor— fantastic even in some cases— but the fact that almost a half decade into its existence, you still can't split a window to see multiple files side-by-side is just ridiculous. In fact it makes it too hard to review code changes or take notes on a document that you are editing, or any of a number of other important tasks that text editors have been able to do.

I get the whole "opinionated software" thing, I really do. But being at a geek conference (Pycon) and seeing all of those Ubuntu desktops configured just so (some with Emacs and some with Vim), something just snapped. So I'm going back to Emacs. Eddie recommended Aquamacs which is supposed to be a nice Cocoa port, so we'll see if that works as a nice "tweener," If not, it's back to XWindows for me.

As a side note, I'm still blow away to see the developers at this Python conference running Eclipse to work in Python (and mostly on webapps). While it may be acceptable for the Java/C/C++ world, seeing Eclipse at Pycon is sort of like watching the soccer mom getting out of the mongo SUV at the local Starbucks— way too much of a tank for something that should just be lighter.

Finally, if you like this kind of geek rumination, I highly recommend the blog The Setup.

Comments Permalink