Google Wave (pt2)

A closer slightly closer look at Google Wave shows that it doesn't do well in waves with lots of participants. I was in Lifehacker's public wave (or at least one of them) and made Firefox 3.5.3 almost unusable. That particular wave made the tab Chrome 3.0.x sluggish. Keep in mind, from a technical or even an organizational standpoint collaborating with 200+ people in a wave is not likely and not efficient between so much movement in the wave at any given time making it hard to read, hard to manage, and slow to load.

My other complaint is that there are so few people that I know in real life that it isn't really worthwhile (yet). I think it's only a matter of time before people I have stuff to collaborate with have access to it. But I do see a lot of potential once there are more adopters.

Google Wave

I managed to get a Google Wave preview account. I don't think any of my friends are on it and I don't have any invites (yet) unfortunately. So I'm kind of dead in the water on what I can do with it.

Reading list-online

From time to time, I'll share what I'm reading in print (magazines + books) and online.

This is my top 10 reading trends from Google Reader.

1. Techcrunch
2. Techmeme
3. Lifehacker
4. Forbes.com News
5. Boing Boing
6. Wired Top Stories
7. Ars Technica Front Page content
8. Wired Gadget Lab
9. Hack A day
10. The Economist

Why do I use Google Reader for RSS?
It integrates nicely with all my social media sites i.e. Feedburner syndication and it integrates with sites such as Digg and Facebook. Also the interface is pretty intuitive 

It's okay to fail

I admit it I'm a perfectionist and I over commit myself. This leads to all kinds of stress. So once in a while I end up dropping the ball. And while that can be frustrating and sometimes embarrassing but fear not, by removing the fear of failure we are free to do as well or as poorly as we would like.

I recently ran a half marathon during a rather busy week at work and in my personal life. I hadn't run in about a week and a half. So I was unsure how I would actually do. There is the chance that I would have run really really well and run a PR or run really poorly. Unfortunately I ran much worse than I would have liked. But hey, I finished without injuring myself.

But I got to thinking about why I didn't meet my own expectations and why that bothered me so much.

1. Not every effort can be your best. There is a prioritization of time and energy that needs to be applied and your end result will reflect that.
2. Preparation+preparation makes a big difference. In this case, I was going through bad dehydration and I went out (for the first 5 miles) at a pace that was about 20 to 30 seconds faster than I should have.
   
3. It really doesn't matter as long as you learn from any mistakes or have some sort of improvement opportunity. In fact, that makes it worth it.
   

New toys...err purchases

Fitness

• TravelTrac Century fluid trainer (link)


• Mission Skincare sampler
  
  Electronics
  
• iPod Touch Generation 2 with firmware 3.1.1
• Fujifilm Finepix s1500

Product Review: LG enV Touch

I got this phone several months ago because my old one (Motorola KRZR K1m) completely bit the dust. It wouldn't even boot up would I can import my contacts. I went to a the Verizon Store to check out my options. I didn't check out any of the phone review sites like I usually do when I'm going to buy a phone, but then again how often does your phone just die. I was debating between two phones- LG Dare, enV 3, and the enV Touch. After talking to the folks there, they said that the Dare's keyboard isn't good for someone that does a ton of texting. So that was off the list. I ended up chosing the enV Touch because it had the QWERTY keypad and the touch screen.

Book Review-iWoz

I, Woz: Computer Geek to Cult Icon: Getting to the Core of Apple's Inventor

This book is essentially an autobiography from Steve Wozniak. I received this book as a gift from a friend in college about a year ago and I'm just getting to reading it now. It was a pretty quick read. I think it took me about 3 days to finish it. On the whole, I found the book pretty entertaining and interesting probably because I'm a bit of a computer geek. I feel some of the stories went into a little too much detail such as when he would talk about some of his pranks and his childhood. I understand that he was into electronics and math as a kid but it seems like he went on too long. It's not a huge deal but it is something that I noticed. So this book could have easily been 20 pages shorter.

I feel this book was written for someone that really isn't into computers as much as for someone that is into computers. In some of the sections, he explains why some of these advancements in technology were critical in the personal computing revolution.


The sections that I found the most interesting were when he talked about when he created the Apple I and the final section that was written to encourage the entrepreneurial and the inventor's spirit. In this final section, he also talked about why he decided to write a book—to set the record straight about his involvement and his leaving (in a matter of speaking) Apple Computer.

Amazon link