15 June 2011
"The best way to predict the future is to implement it" - Alan Kay
A year ago, several colleagues and friends including Kendra Little (b / t), Crys Manson (b / t), John Halunen (t), Mike Decuir (b / t), and Argenis Fernandez (b / t), went on SQL Cruise. They came back with fire in their eyes, new skills, and a lot of new contacts. This time, I decided to go as well.
Why Should I Go?
At first, my reason for going to SQL Cruise was "This will be fun!" I knew the organizers by reputation, and knew I would learn. A lot. I had never been on a cruise before and was curious what it would be like.
Later, I found I had different reasons for going:
What Did I Do?
I dislike the unknown. I learn what I can to avoid risk. Here's what I did to learn about SQL Cruise, and cruising.
And so it begins...
Boarding was very easy. I had read that earlier is better, so I arrived at 11am and was on board in 15 minutes. Our cabins weren't ready yet, so I went up to the outdoor dining area to chat with the other arrivals.
The first four hours of the cruise were spent in the sunshine, eating soft-serve ice cream and getting to know the other cruisers.
Some of my fellow cruisers, like Neil Hambly (b / t), were social and easygoing. Others, like Klaus Aschenbrenner (b / t), are more reserved, but have a wealth of experience. The others, like Ryan Malcom (t), are brilliant up-and-comers. It was clearly a great group of people to be with.
The Team-Building Exercise
Confio had sponsored a search-the-ship team building exercise. We split up into teams of 4 or 5, some of us merrily inebriated, and were told to find 25 different things on the ship. The winning team would win fabulous prizes.
45 minutes (and 500 calories) later, we finished. Sadly my team did not win. Still, it was an amazing experience, and worked brilliantly to break the ice to all of us.
Exhausted, content, and ready for the next day, I went to bed. The training was about to begin...