I don't have the energy to come up with a decent title for this post, so search engines be damned...
I've been catching up with some podcasts this week. This morning I finally took a listen to Michael Arrington's (from TechCrunch) TalkCrunch. I heard their first installment about calendaring. Really cool stuff. The podcast does so much to put humanity behind these sweet, new products that are being developed. It's important to keep that in mind. I got such a better sense of what zvents and 30boxes are doing and trying to do. I came away with a deep respect for these guys. Michael and Nic as well. Above all the web is about people. Most Web 2.0 applications are designed to provide people with a voice, or control, or a place to feel involved, or comfortable. Getting to know the people behind these products in a comfortable and casual way is something that Michael is doing with his podcast.
Since calendars are very near and dear to my heart, I was happy to hear some good discussion on the subject. zvents has a great grasp on monetization which I'm so happy to hear, and 30boxes understand its audience and is well positioned to take off in the next 6 months. This also makes me happy :)
I also enjoyed the discussion on how all of these guys realize that they can't get caught up in the hype. They recognize the importance of the core early adopters and influencers, but they understand that there is a huge audience of folks that need simple applications and are very new to the social web. Again, happy to hear that, with these guys. We can not design for ourselves. We have to solve real problems. So check out TalkCrunch if any of this junk interests you. Michael is a tremendous filter; pay attention.
I've been encouraged lately to start to learn to program. Leonard and Andy from Upcoming.org suggested that I jump into Ruby on Rails. I've considered this before, but I'm now convinced that it's something I need to do to better express myself. A working demo or prototype is the only way to get people's attention these days. No one reads documentation or can understand wireframes or even rendered designs unless they have something to play with. I'll keep you posted on this new chapter.