Where 2.0 day two Steve Morris gave an interesting presentation describing the "disappearing data problem." He explained how public data, geo-spacial data in particular, is rotting away in decomposing physical formats, or incompatible/proprietary file formats. There's a lot of it, but whether it will be usable is a major
Where 2.0 day two Steve Morris gave an interesting presentation describing the "disappearing data problem." He explained how public data, geo-spacial data in particular, is rotting away in decomposing physical formats, or incompatible/proprietary file formats. There's a lot of it, but whether it will be usable is a major
Where 2.0 day two Steve Morris gave an interesting presentation describing the "disappearing data problem." He explained how public data, geo-spacial data in particular, is rotting away in decomposing physical formats, or incompatible/proprietary file formats. There's a lot of it, but whether it will be usable is a major
Great hotel experience! As I was checking out of the San Jose Fairmont hotel this morning, the Registrar asked me if I'd had taken some cashews and M&Ms from the mini-bar; I was shocked! Usually the front desk is clueless about mini-bar purchases. I had the cashews the day
Great hotel experience! As I was checking out of the San Jose Fairmont hotel this morning, the Registrar asked me if I'd had taken some cashews and M&Ms from the mini-bar; I was shocked! Usually the front desk is clueless about mini-bar purchases. I had the cashews the day
Great hotel experience! As I was checking out of the San Jose Fairmont hotel this morning, the Registrar asked me if I'd had taken some cashews and M&Ms from the mini-bar; I was shocked! Usually the front desk is clueless about mini-bar purchases. I had the cashews the day
Where 2.0 day one Here's my summary of day one, of two, at the Where 2.0 conference in San Jose, CA, USA. It's the data! If there's a recurring theme at the Where 2.0 conference this year, it is data. From geo-spacial format and feed standardization
Where 2.0 day one Here's my summary of day one, of two, at the Where 2.0 conference in San Jose, CA, USA. It's the data! If there's a recurring theme at the Where 2.0 conference this year, it is data. From geo-spacial format and feed standardization
Where 2.0 day one Here's my summary of day one, of two, at the Where 2.0 conference in San Jose, CA, USA. It's the data! If there's a recurring theme at the Where 2.0 conference this year, it is data. From geo-spacial format and feed standardization
Another Apple moment. A few years ago my need for personal video conferencing became serious. I have family scattered around the world, and I wanted them to see my newborn son. It was around this same time that Apple announced iSight/iChat (their video conferencing solution for personal computers). Further coincidence around that
Another Apple moment. A few years ago my need for personal video conferencing became serious. I have family scattered around the world, and I wanted them to see my newborn son. It was around this same time that Apple announced iSight/iChat (their video conferencing solution for personal computers). Further coincidence around that
Another Apple moment. A few years ago my need for personal video conferencing became serious. I have family scattered around the world, and I wanted them to see my newborn son. It was around this same time that Apple announced iSight/iChat (their video conferencing solution for personal computers). Further coincidence around that
text input Distilling meaning from text that users enter into arbitrary text input fields is going through some good iterations these days. I see three general buckets of "smart entry fields"; you could build six permutations of them if you consider client-side and and back-end-side versions of each, but, for
text input Distilling meaning from text that users enter into arbitrary text input fields is going through some good iterations these days. I see three general buckets of "smart entry fields"; you could build six permutations of them if you consider client-side and and back-end-side versions of each, but, for
text input Distilling meaning from text that users enter into arbitrary text input fields is going through some good iterations these days. I see three general buckets of "smart entry fields"; you could build six permutations of them if you consider client-side and and back-end-side versions of each, but, for
Consensus I came across this great cartoon, apparently from 37signals, where two people agree that they want to build a house. Working for a big company, I see this happen all to often. I think it's a mechanism to reach "agreement" on something rather than nothing at
Consensus I came across this great cartoon, apparently from 37signals, where two people agree that they want to build a house. Working for a big company, I see this happen all to often. I think it's a mechanism to reach "agreement" on something rather than nothing at
Consensus I came across this great cartoon, apparently from 37signals, where two people agree that they want to build a house. Working for a big company, I see this happen all to often. I think it's a mechanism to reach "agreement" on something rather than nothing at
Video & Conversion (not that kind of conversion!) Do you remember your first kiss? I do; 5th grade, Gina Stabile, recess, outside the gym doors. We pecked, then ran away from eachother as fast as we could. Do you remember when you converted to Apple? I do. It was a couple of years ago. Two things moved me
Video & Conversion (not that kind of conversion!) Do you remember your first kiss? I do; 5th grade, Gina Stabile, recess, outside the gym doors. We pecked, then ran away from eachother as fast as we could. Do you remember when you converted to Apple? I do. It was a couple of years ago. Two things moved me
Video & Conversion (not that kind of conversion!) Do you remember your first kiss? I do; 5th grade, Gina Stabile, recess, outside the gym doors. We pecked, then ran away from eachother as fast as we could. Do you remember when you converted to Apple? I do. It was a couple of years ago. Two things moved me
Vonage vs. Skype call quality Awhile ago I tried Vonage for two weeks, and wound up returning it. Although its feature set is rich, call quality was rather poor. Very high latency made the call as bad as a cell phone call, with participants talking on top of eachother. I recently tried Skype again (it
Vonage vs. Skype call quality Awhile ago I tried Vonage for two weeks, and wound up returning it. Although its feature set is rich, call quality was rather poor. Very high latency made the call as bad as a cell phone call, with participants talking on top of eachother. I recently tried Skype again (it
Vonage vs. Skype call quality Awhile ago I tried Vonage for two weeks, and wound up returning it. Although its feature set is rich, call quality was rather poor. Very high latency made the call as bad as a cell phone call, with participants talking on top of eachother. I recently tried Skype again (it
To acronym or not to acronym? It's been fun watching all the hype fly around AJAXapplication programming over the past year or so. Especially funconsidering that XMLHttpRequest has been in existence since June 2000. [http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/extensions/xmlextras/base/src/nsXMLHttpRequest.h&rev=HEAD&mark=1.