Why I Switched from iPhone to Android, then back to iPhone

Back in August 2010 I’d fucking had it with AT&T in San Francisco.  My iPhone 3G didn’t work at my house located in the middle of the city, I always lost calls on 101, download speeds were dirt slow almost all the time, the list goes on.  I felt as though I had an iPod touch most of the time, yet I was paying close to $100 a month for this supposed “service.”  Enough was enough, so despite hearing Verizon iPhone rumors I switched to the phone that most resembled an iPhone available on Verizon, the Droid Incredible.  After almost a year on Android I’ve switched to an iPhone 4.  I’ll try to explain my reasoning in this post.

Why Verizon

I chose Verizon because I had used a friend’s Verizon smart phone in the city.  My experience trumped any other experience with any other carrier.  Sprint and T-Mobile are supposedly pretty good in SF, but I wanted the best.  And I got the best.  Verizon is absolutely amazing.  It’s wicked, wicked fast, available almost everywhere, and I have yet to find a single spot that consistently drops calls.  Since the switch I’ve never once found myself limited by not being able to use 3G while on the phone.  And I’m utterly happy to be paying $100 a month for stellar mobile performance.  Though like all carriers Verizon’s service isn’t all that great, and they hit with you with a bunch of hidden fees wherever they can.

iPhone vs. Android

I know exactly what you’re thinking.  You’re thinking I can’t compare the iPhone to Android because each handset is different and the software each handset provider and carrier puts on these devices is different.  Google deliberately lets carriers and handset providers change and add software, which gives the consumer–me in this case–the right to compare Android to iPhone.  So for better or worse, I’ll comparing iOS to the Sense Android interface running on Froyo (2.1).

Hardware

The Droid Incredible’s downfall is it’s battery life.  A charge won’t last a day, not even close.  Sometimes I’d be at 25% battery at 10am after a full overnight charge.  Other than the batter, though, the hardware and specs are pretty comparable.  The real difference is in software.

Software

Android vs. iOS really comes down to polish and detail.  Android can be very clunky and often only slightly inconvenient.  Android gets a lot of small things wrong, and unfortunately the small things often frustrated me.  I don’t want to bore you with detailed examples of what I’m talking about, but for argument’s sake I’ll include one example. Take adding a new phone number received via a SMS to a contact already in my contact list.  When I’d hold-click the new number to add a it, I’d start typing the name of the person that already existed in my contact list.  I’d see several seemingly duplicate entries for the same person.  I’d click one arbitrarily, and be prompted with another list of several seemingly duplicate contacts.  I eventually gave up trying to add phone numbers from SMS, instead adding phone numbers by hand.

Android does beat iOS in a few ways.  First, the Gmail app is totally awesome, way better than Apple’s Gmail integration.  And I do really like the gadgets that can be placed on the home screen.  But frankly I can’t think of anything else I like more about Android.

Conclusions

The iPhone is a far better product, and a far better experience.  I’m significantly less frustrated using my iPhone, and now that it’s on Verizon the service is exquisite.  I gladly signed a 2-year contract with Verizon, and I’ll likely buy a second iPhone before two years comes up.  Having first struggled with bad service, followed by frustrating software, I’m totally stoked to have found the best of both worlds: excellent service and a phenomenal user experience.  Go Apple, and go Verizon.  They may both be closed/evil in their own ways, but I choose the better products.

Filling the Gap

Over the last few years I’ve been able to learn a good breadth of skills ranging from product management to large scale data processing and analysis.  But a gap in my toolset still remains: beautiful design.  I can’t for the life of me make something beautiful.  I know Javascript and HTML pretty well, but my CSS sucks.  So, designer/front-end friends, can you please recommend some resources I can start exploring that’ll enable me to make beautiful websites and mobile apps?  This is my current plan:

Design: Defensive Design for the Web, Don’t Make Me Think

CSS: CSS Mastery

Leave me a comment or shoot me an email if you have thoughts.  Thanks!

Decisiveness

For better or worse I tend to care a lot about the happiness of the people around me.  For example, I tend to think I’m a hospitable host when I have guests over for dinner.  I feel guilty when I may have made someone unhappy, self-conscious, or otherwise upset.  And I’m eager to hear coworkers’ opinions when I’m proposing a big plan or debating a difficult topic.

In a lot of ways caring so much for those around me is a good thing for all the reasons it’s good to be a nice person.  But in the workplace I’m starting to believe that more importantly than caring about others’ well being is caring about solving the problem at hand, about being decisive and moving forward.  And second to being decisive and productive, one should be nice.  Now depending on your job, others’ well being may be top priority, for example if you’re a leader at a company, a manager, or anyone else directly influencing others’ happiness.  But among peers and anyone above you in a company hierchy, decisiveness matters most.

I’ve always considered my coworkers my friends, but now I’m starting to understand that relationships are different at the workplace.  Business matters in this context more than friendship.  Or at least friendship can be put aside temporarily while business is conducted, while decisions are made and projects and teams are moved forward.  I’m learning to be decisive, to express my opinion instead of a statement I’ve constructed that might make someone else feel better, that someone else is more likely to enjoy.

DMD Ride Report: 207 miles, 20,656 feet of Climbing

Yesterday I cycled 207 miles, starting at 5am and ending at 11:30pm, climbing 20,656 vertical feet, over six substantial mountains and passes.  This is my story.

The Months Leading to the Ride

In late January, Vitaly emailed the Mission Cycling list about a ride called the Devil Mountain Double (or DMD for short), a ride with over 200 miles and 20,000 feet of climbing.  My original reply to the email was literally, “F that.”  Not even an hour later my good friend and coworker, Jay, pulled my leg and got me to commit to the ride.  Another friend, Keith, joined us, making for four riders in total representing Mission Cycling.

I more or less gave up my social life to train for this ride, trying to ride over 100 miles every Saturday leading up, with Sunday recovery rides and at least two days of riding during the week.  I also totally flaked on my good friend, Eric, and a community he’s built around his website, OneUpMe.

The Ride

Yesterday started with a 4am wakeup and a 5am departure from the San Ramon Marriott.  A little over 200 people did the ride, most leaving at 5am, and some leaving at 6am.  We rode in the dark for 10 miles, bringing us to the base of Mt. Diablo.  From there we climbed 11.2 miles for a total of 3,283 vertical feet to summit Diablo in the nearly freezing temperatures and brutal wind.  Jay and I descended quickly without regrouping with Vitaly and Keith at the summit rest stop, to avoid the brutal temperatures at the top.  I didn’t even bother noticing the amazing view of San Francisco.  As we were descending my hands and legs became completely numb.  I was shivering uncontrollably.  And I was worried I’d crash given my hands weren’t working well, I was shivering violently, and I was descending a technical, steep grade.  The thought crossed my mind to throw in the towel and go home.  However, eventually we made our way into the sun, warmed up, and kept going.

Jay and Vitaly are much stronger climbers than me, so on the Morgan Territory climb we separated and regrouped at the next rest stop.  And Keith was somewhere behind us.  I took off my bike lights and put them in a bag that the ride volunteers would take to a rest stop towards the end of the ride, when I’d need them in the dark of the evening.  By that time Jay had already had a flat tire and realized he needed a new tire.  Fortunately the rest stop had a new tire, so after a few minutes of changing we were off again heading east.  We saw Keith as we were leaving.  On our descent from Morgan Territory into the Central Valley, we saw fire trucks and ambulances tending to a fellow rider who had gone down because of a strong cross wind.  He seemed OK, but seeing him amidst the flashing lights was humbling and kept me cautious on the descent.

The Central Valley, along highway 580, was windy and occasionally miserable.  Sometimes we had tail winds, sometimes cross winds, and sometimes head winds.  I stayed with Vitaly and Jay and struggled to keep up.  I was worried I was putting too much effort in to stay with them, but I kept with it until Patterson Pass.  Most people on the ride were worried that Patterson Pass–surrounded by wind turbines–would be awfully windy, but fortunately it wasn’t.

Jay and Vitaly were waiting for me at the next rest stop, so I ate quickly and we kept going.  We started ascending Mines Road at mile 90ish, and this was the last time I would see Jay and Vitaly.  For the next 30 or so miles I rode by myself, eventually getting to lunch, where I ate quickly and reapplied chamois cream.  And at about this time my right knee started bothering me, I expect because I wasn’t wearing leg warmers and my knees were cold.  After lunch I got back on the horse with two guys I met along the way, Jules and Doug.  My front tire flatted shortly after lunch, but after a quick tube change I was off and back on the bike.

After some up and down Doug had ridden ahead and Jules and I started climbing Mt. Hamilton, a bear of a climb, with a gain of  1900 vertical feet over 4.4 miles.  The climb was beautiful but also challenging.  We started the climb at mile 130ish, and by this time I was tired, but I was also fired up.  I knew that after we finished Hamilton all we’d need to do is ride north and we’d be home free.  Physically I was pretty battered, but mentally I was fired up.  With only a few more minutes in the climb my front tire flatted again.  I discovered that I had missed a small splinter when I changed the tire after lunch.  So after removing the splinter, borrowing a tube and pump from Jules, and changing the tube, I was off again.

As we started the descent my rear tire blew out–or, flatted very abruptly–after I rode over a big bump in the road.  The tire had a small hole in the sidewall, which worried me but didn’t stop me.  I forget exactly why, but I ended up needing to wait for the sag wagon–one of the vehicles driving around helping cyclists in need.  I’m not sure if I needed a new tube or what, but after some waiting, a dollar bill in the hole, a new tube, and some air in the tube, I was back on the bike, descending Hamilton, overlooking the entire South Bay.  The view was gorgeous.  As I was descending I felt a small bump in my rear tire, which I was worried was due to the hole in the sidewall.

Eventually Jules and I made it to the rest stop at the bottom of Hamilton.  After a quick stop I looked at my rear tire and noticed that the dollar bill wasn’t doing its job, and I’d need a new rear tire.  Fortunately the rest stop had a spare tire, and the insanely helpful volunteers changed my rear tire for me.  The first tube they used popped when they put the tire on, so they had to take the tire off completely, change the tube, and refill the tire.  So what started as a quick stop become a long stop, with two tube changes and one tire change.  Just as I was ready to depart by myself I saw Keith rolling into the stop.  I waited a few minutes for Keith to rest and eat, and the two of us left together and would eventually finish together.

The research I had done on this ride beforehand lead me to believe that the next climb that awaited us, Sierra Road, was going to be the hardest.  The climb started at mile 155, elevating 1759 vertical feet over a short 3.5 miles.  This climb was brutally steep, and it never ended.  I could barely turn my pedals over, however I resisted from zig-zagging across the road.  I think Sierra Road was the hardest climb of the day, but at least at the rest stop at the top Keith and I could overlook the sun setting on the South Bay.  The sight was beautiful, and after our accomplishment Keith and I felt as if we were on the home stretch, with only 40 miles to go (ugh).

The rest stop at the top of Sierra Road is called Pet-a-goat, because there’s a goat at the top that you’re supposed to pet.  I pet the goat, ate and drank, and put my lights back on.  The sun had set, and it was getting dark and cold.  Just as we were leaving a woman, presumably with her husband, rolled in and had a mental breakdown.  She started hitting herself in the face, screaming and cursing about having so much left at a late, dark, and cold 8pm.  She was not happy, and her reaction troubled me.  It made me realize that Keith and I were physically and mentally exhausted, facing 40 miles to go, with two more climbs in the cold and dark.  We started on our way, and Keith would eventually see the woman and her presumed husband at the finish at 12:30am.

The rest of the ride was a mental battle against myself.  We were almost entirely on small, single-lane, backcountry roads, with no civilization in sight.  All we could see were silhouetted mountains that I was worried we’d need to climb and the lit road in front of us.  Keith and I hardly talked with one and other, but we road two abreast, our lights leading the way through the night.  Between the pet-a-goat stop and the finish, we’d do two more climbs, ride a little over 40 miles, and stop once for hot chocolate and more food.

Sierra road was definitely the hardest climb in my book, but this last 40-mile stretch was overall the hardest.  Physically I was toasted, but by this point I could continue to turn the pedals so long as I continued to eat and drink.  What was hardest was the mental acceptance of what was to come.  Every climb, every turn, I wished the hotel would be around the corner.  I wished I would at least see a human or a house or a restaurant, to remind myself of the reality that this is just a bike ride.  I wanted a shower, a warm meal, a break.  The last 10 miles were especially awful, because we weren’t sure exactly when we’d see the hotel, so every corner we’d turn we’d get our hopes up only to see another hill, or another corner.  A few times Keith or I would spout a curse in frustration, but we kept each other going and sane.

By the time we knew we were within a mile of the hotel, we were doing well over 20mph, giving the last stretch everything we had left, which wasn’t much.  My Garmin bike computer and headlight were almost out of batteries.  I screamed in joy when we saw the hotel, relishing my accomplishment.  I did it.  I completed California’s hardest double century, one of the hardest organized rides in all of California, exactly 12 months after doing my first century (100-mile ride).  I was physically and mentally toast, ready for a shower, ready for bed, ready to be off my bike.  I had started at 5am in the dark and finished at 11:30pm in the dark.  But I was ecstatic.  I had prepared for this ride for months, and I had finished it.  YES!

Eating and Drinking

For amusement’s sake, I thought I’d list an estimation of what I ate all of Saturday:

Breakfast

  • Oatmeal
  • Water
  • Multi-vitamin
  • 2 salt tablets
Rest stops in total
  • ~5 salted and herbed potatoes
  • ~6 peanut butter and jelly sandwiches
  • ~6 bananas
  • Some trail mix
  • Some potato chips
  • ~14 salt tablets
  • ~10 ibuprofen
  • Chicken teriyaki sandwich
While riding
  • 6 Clif bars
  • ~12 gels
  • ~3 scoops of Accelerade
  • 1 granola bar
  • ~10 bottles of water (24oz each)
  • 1 root beer
Dinner
  • Vegetable lasagne

Summary

The Devil Mountain Double was my hardest day on the bike by far.  I’m glad I did it, and I’m super proud of my accomplishment.  But as I’m writing this I’m in pain, sore, and mentally and physically exhausted.  And I don’t think I’ll ever do something like this again.  Yesterday I was awake for 23 hours, physically sitting on the bike for 15 hours, and resting/changing tires/eating for 3.5 hours during the ride.  Right now the accomplishment doesn’t justify the mental and physical torment I put up with for 18.5 hours.  But then again, we’ll see how my attitude changes as I recover, and with better luck and fewer than four flat tires I could probably finish in much better time.  For now, I’m super stoked, super proud to have ridden with Jay, Vitaly, and Keith, and super ready to sleep and eat more.

Thank You

All of my friends and family have been insanely supportive throughout.  You’ve been understanding when I didn’t stay out late or when I flaked on a commitment.  You’ve been there to talk me through my worries and fears.  And you’ve been so congratulatory.  I thought of you endlessly on the ride, trying to find encouragement to turn the pedals.  Thank you so much for everything.  I couldn’t have done this ride without you.

The volunteers and organizers of the Devil Mountain Double did a fantastic job.  I’ve never been a part of such a well organized, well supported ride.  I can’t thank the volunteers enough for their kindness and willingness to help, no matter what.  So to the DMD volunteers and organizers, thank you.  You guys made the day as good as it could be.  Seriously, volunteers would fill my bottles for me, change my tires, take my bike to the bike rack.  You guys are so awesome.

Jay and Vitaly were waiting for me and Keith at the hotel, probably bored out of their minds being in the little conference room for several hours waiting.  You guys are awesome for waiting for me, even though you totally didn’t need to.  It was great riding with you both, even though it didn’t last very long.  Hopefully one day I’ll be able to catch you guys :).  But for now, thanks, and see you out there Tuesday, assuming I can sit on my bike by then.

Keith was my sanity for the last 40 miles.  I think without Keith I would have struggled to keep going, to stay sane in the wilderness, with no signs of civilization around me.  I know you didn’t need to say or do anything to keep me going, but your presence, relaxed manner, and company were stabilizing.  I’m glad we found each other at that rest stop.  Good luck with the rest of the California Triple Crown!

Update: read Vitaly’s report here.

Real-time Marketing: Twitter and Competitor Failure

The whole tech world is talking about the extended EC2 failure today, and all the chat is happening on Twitter, ‘EC2′ and ‘AWS’ are both trending.  The marketing team at Storm took this opportunity to run a promoted tweet on the ‘EC2′ Twitter search, promoting their competing cloud offering.  Take a look:

Storm’s strategy here is totally brilliant.  Everyone is talking about how EC2 is totally failing right now, a moment when customer emotions are perhaps the highest they’ll ever be.  And Storm is the first brand being put in front of these angry customers’ eyes, clearly distinguishing themselves as a competitor in the elastic hosting market.

If you have a competitor that goes down and Twitter is talking about it a lot, buy a promoted tweet for that search.  I’ll bet this is one of the best ways to capitalize on competitor failure, especially when you’re in a market where uptime is a key competitive distinction.

Update: now SoftLayer has joined the mix with a funny promoted tweet about SkyNet:

The Personal and Social Challenge of Endurance Cycling

For those of you that don’t know me that well, I love to cycle.  My interest started shortly after I moved to San Francisco in the fall of 2008.  In 2010 I completed my first century (100 miles), my first double metric (200 km), and finished the season with Death Ride, a grueling 128 mile ride over five mountain passes, totaling 15,000 vertical feet of climbing.

I decided to up the challenge this year by signing up for a 200-mile ride with 20,000 vertical feet of climbing.  The Devil Mountain Double (DMD) is scheduled to take place on April 30th, and I’ve been training like a madman getting prepared.  This blog post is about the training leading up to the big ride, both how it’s impacted my life and how I’ve gone about preparing.

When I signed up for the DMD I assumed the toughest part would be preparing my body for the physical challenge of biking 200 miles in a single day, over long, steep, mountain climbs.  However, to my surprise, I’ve found the toughest part of the training to be the impact it makes on my social and personal life.

For the last two months, with the exception of only two weekends, I’ve spent every Saturday biking more than 80 miles, usually departing my house before 7am.  I’ve spent as many Sundays as possible biking between 40 and 60 miles, usually leaving my house before 10am.  And I’ve been very consistent riding Tuesday and Thursday mornings for 20ish miles, with several Monday and Wednesday bonus rides as well, leaving my house before 6:15am, often climbing up and down the same hill to get the most out of my morning.

Needless to say I’ve been quite a morning person the last several months, which isn’t too much different than my normal schedule.  However, I’ve made a huge effort to get plenty of sleep to aid my leg recovery and prevent me from being a total tired wreck at work.  I’ve had to say “no” to too many fun nights with friends or coworkers.  I’ve had to leave movies before they’ve ended.  I’ve had to say goodbye to a group of awesome friends staying out for an extra beer or two.  I’ve turned down several snowboard/snowmobile trips to keep my weekends open for cycling.  The list goes on.  I feel awful bailing on my friends, but I’m doing what I need to do to survive this ride.

So to all my friends, thanks for your patience while I devote myself to this challenge.  Every time I say goodbye early, or turn down an awesome opportunity to snowboard, drink, eat, run, or do anything else with you, I want you to know that I badly want to throw away my training and enjoy a weekend or night with you.  But I’m devoted to this ride, I’ve trained too hard to lose diligence.  You’ve all been amazingly supportive and understanding.  So, seriously, thanks.  My guilt often reminds me how great of friends you are, and that energy will be what motivates me to turn my pedals over and finish this bear of a ride.

Update: my Ironman friend, Andrew, wrote about this last October, six weeks before his race.  So it’s not just me :).

Young People, I Urge You To Consider Software

I work in a crazy industry called software.  Companies with zero revenue get wild valuations, engineers complain that their employer doesn’t provide free food (#firstworldproblems), and starting salaries are almost at the 6-figure mark.  Yet what’s more crazy is the undeniable need for talented young professionals.  I’ll claim that no other industry is anywhere near as creative and lucrative as the software industry.  Sure, you can go get your law degree or work for an investment bank, and after a few years you’ll be making lots and lots of money.  But the chances are good that you’ll be unhappy with your job.  When I hear about my friends in law and banking I feel sorry for them — so many of them devote hours and hours to mindless, awful work, living lavishly on the weekends, slowly making their way to more creative roles as they mature and gain experience.

Forget giving away your 20s to working your way up the ladder, justifying a shitty job as a means to an end.  The software industry has insanely high starting salaries, startups give out equity that can convert to large sums of money if the startup does well (and many of them do), and most importantly, you’ll be doing wildly creative, awesome, challenging work.  Seriously.  Data is being created faster and faster, and the need for smart, math-oriented analysts and engineers is only growing.  Mobile is blowing up, and the need for mobile engineers and awesome designers/UX people is following in the wake.  New websites are always being started, opening up all sorts of opportunities in scalable web infrastructure engineering, agile software development, design, and product management.  There is so much happening in this industry, and so much opportunity.

I wish I could find a study that goes into the happiness of people in different industries.  Hardly any of my software friends are unhappy: they love their work; they have excellent salaries; they are treated well by their employees; they have insane opportunities to grow and better themselves; and they’re passionate about what they do, the problems they solve, and the people they work with.  In the software industry age and experience don’t matter.  What matters most is your passion and motivation, followed closely by your intelligence and cleverness.  So if you’re on the fence about what to study, give software a shot.  Take a class in college, read a book or two, and see if you’re interested.  The software industry is absolutely amazing, and there’s a huge need for good people.  If you’re interested, be one of those good people, and be happy.  You’ll love it here.

How Math Can Help You Make Friends

At OneUpMe Eric and I have created several formulas that correlate one user to another based on the votes each player has made.  We’ve used this “friend score” to bring people closer together, both as they play the game and also as they communicate with other players.  Similarly, we’ve created formulas that rank players’ popularity and taste scores, ultimately showing how good or bad a player is at playing the game.  And with these formulas we’ve been able to create a significantly richer OneUpMe experience, connecting similar players together to forge new and deep friendships.  In this post I’ll talk specifically about the friend score, and how math has helped OneUpMe players make friends.

The Math Behind The Friend
Let’s talk about our “friend score” formula first.  On OneUpMe players compete by supplying creative responses to seed topics.  Every day sees a new topic, and players vote on other players’ responses, the best voted response winning for the day.  A player’s response is initially anonymous to all players, until a post is voted on, at which point the voter is able to see the post’s author.  So, if Eric posts a response, I won’t know it’s his until I vote on it.  The formula we chose to determine friend score is listed below.  For sake of example let’s say this formula is calculating the friend score from person A to person B.

N * T / P

In this formula N represents the number of times person A voted for B, T represents the total number of posts made by person B, and P represents the total number of posts made by person B since I’ve joined the game.  Basically, what we’re doing is we’re multiplying the number of votes person A has made for person B by the ratio of posts person A has had the opportunity to vote on.  So friend score will be maximized if person A has voted for each of person B’s posts, assuming person A joined the site earlier than person B.  The math is simple, but in this case simplicity is all we need to represent meaningful relationships.

After we’ve calculated the friend score between each player we normalize the scores, effectively assigning percentiles to friendships.

Applying the friend score
With the normalized friend score–meaning we can say that person A and person B have a friendship strength in the Nth percentile–we’re able to do a lot of things in the game to really drive engagement between friends.  For example, the “hottest” list of posts utilizes the normalized friend score to increase the likeliness of me voting on a post made by someone I’ve previously voted for.  Take a look, in the below example I voted for Eric’s and Carla’s posts, both players I often vote for:

Similarly, we’ve built a news feed feature which takes relevant forum and wall discussions and displays them on my news feed.  The news feed scores discussions based on the friend score between me and the people in discussion, only displaying posts of people I’ve voted for previously, or, people I’m interested in chatting with.

Ultimately we’ve changed the dynamic of the game to be more social, to be played more between friends, friends that develop and change as you play the game.  Our users have said they’re less overwhelmed with the thousands of posts the site sees per day, because the “hottest” post list and the news feed let them connect with the people they already know.  And the OneUpMe champion players, known on the site as “Elders,” have made powerful friendships, and are visiting one and other all across the world.  Seriously, last week a pair met up in London!  Math makes friends!

Next steps
We base friendship on a player’s voting pattern, and we use friendships to encourage discussion and further playing among friends.  Currently a friend score is purely based on gameplay–people you vote for become your friends.  However, such a measurement isn’t quite complete.  We need to start using forum commenting, wall posting, and liking to measure friend strength as well.  So instead of just using game play, we also need to use discussion.

Selfless Corporate Culture: Weekends for Fun and Profit

To continue my little series  on what I’ve called a selfless corporate culture, today I’m writing about a crazy idea around alternate weekends for productivity and adventures.

Late last week Tahoe was hit with quite a lot of snow.  There was so much snow, in fact, that highway 80, the main artery entering and leaving North Lake Tahoe, closed for most of Friday.  Still on my high from heli-boarding I decided at 7pm Friday night to drive to Squaw and shred my share of fresh snow.  I left shortly before 8pm that night and arrived in Tahoe at 2:30am.  After sleeping four hours I got ready and jumped in the car en route to Squaw, only to wait in traffic for another 45 minutes.  My crazy thought hit me at this moment: some of my most productive times are the weekends, yet often I spend them in traffic or fighting crowds at airports.

Employees should be given an option to take their “weekends” during the week.  So instead of having Saturday and Sunday off, everyone has the option to take Tuesday and Wednesday off instead.  I have two reasons for this: first, working Saturday and Sunday would be email and meeting free, almost unarguably making non-managers more productive; second, taking your “weekend” during the week would let weekend warriors avoid crowds at the mountains, airports, or anywhere else.  My first reason assumes that most employees would most of the time decide to have normal weekends, which seems like a plausible scenario considering how few people make regular weekend trips.  And a final caveat is that sufficient notice would need to be given to take Tuesday and Wednesday off.

The largest argument against my proposal is about communication.  How will team members be able to communicate if they’re not all in the office at the same time?  First, everyone will always be in the office Monday, Thursday, and Friday, which in most cases should be ample time to work with others on joint projects.  Furthermore, I argue that in most cases face-to-face realtime communication isn’t as critical as most leaders expect.  (Wow, I feel weird writing that given how extroverted I am.)  But again, three days a week should be plenty of time for all-staff meetings, team meetings, team building events, or any other gathering.  Lastly, if employees are properly multiplied, they’ll be self-sufficient decision makers capable of and passionate to do what it takes to succeed.  And they’ll be happier because they’ll be able to beat the weekend crowds if they so desire.

Not too crazy of an idea, right?

Serendipity

Shortly after I posted about joy in community I was hit by a huge, serendipitous realization: creating a community is exactly in line with the Dalai Lama’s teachings.  I’ve written endlessly about the Dalai Lama, and I’ve always reiterated his teaching that inner peace and happiness come by being compassionate for others.  I’ve always agreed with the Dalai Lama’s teaching.  However, I don’t think I’ve understood how it played a part in my technology-driven life until now.

Creating a software product that enables an individual to be a part of something bigger, connecting them to others centered around the same product, is being compassionate.  Seeing the joy you bring your established community will relentless bring you closer to an undisputed inner happiness.  This is my purpose, the merging of technology and happiness, the enabling of an individual to connect with others in a product-centered community, to find happiness and excitement in that community and surrounding product.