First Impressions Review: Acer Aspire Easystore AH340

My 4 year old Infrant ReadyNAS NV+ only had a couple of hundred gigabytes of storage left on it, so I now had to make a decision: do I upgrade all the drives at once, or should I switch servers entirely? The epiphany I had came when I experienced a power supply failure in 2009. While the ReadyNAS was offline and had to be shipped back to the manufacturer for a replacement, I had no access to data. Note that while RAID protects you from a failure in any given disk, you still have single-points of vulnerability in your RAID machine's motherboard, power supply, and network card. Netgear's customer service so bad that they replaced my 1GB machine with a 256MB machine, so I knew that I would not stay with Netgear if I could at all help it.

Other raid vendors such as Drobo FS were just as expensive, and did not solve the ultimate problem I find in all RAID systems, which is that every RAID implementation is different. If your vendor went under, or you simply found a better deal elsewhere, you couldn't switch vendors and expect to just move your disks and have everything go well. In fact, if your RAID vendor went under and your hardware went bad, your disks will now be just a bunch of platters with no use whatsoever and you'd better have reasonable off-site backup.

The answer, then, is to run a commodity OS that's more or less configurable. In fact, if possible, doing away with RAID and running a standard file system that you can operate from any commodity hardware would be ideal. I considered doing what Michael Herf did and setting up a ZFS Nas, but instead found a refurbished Acer Aspire Easystore over at Cheetah Deals. At $270 shipped, I didn't think I could build a machine for less. (Herf paid $1500 for his ZFS wonderbox)

The Easystore runs Windows Home Server (WHS), which is not software RAID or in fact, RAID of any kind. All the disks you stick into the machine gets turned into NTFS disks, which means that if you have a hardware failure (not a disk failure), you take the disks out, stick them into a Hard Drive Dock attached to any Windows PC, and your data comes right back up. This is huge. It means you can abandon WHS with no real lockin, or move things to a newer bigger machine in the future. To defend against hard drive failures, WHS lets you designate certain folders to be duplicated, which means that their contents will be replicated across multiple drives, so if one drive fails you won't lose all the files. This is a nice feature, since for most media (like music, watch-once videos, etc) you don't have to waste space replicating them, but for your most important files, you'll get protection against drive failure.

The implications of this setup are interesting. First of all, if you fill all 4 disk slots on your EasyStore and you run out of disk space, you can't just pull out an existing disk and drop in a larger capacity one! That's because you have to attach a new disk, tell WHS to remove the old disk (it will then copy all the data off that old disk), and then stick in a new one with more capacity. Fortunately, you can use the USB ports or the eSATA ports to add new disks. One particularly intriguing approach would be to use a multi-bay eSATA enclosure in order to expand your WHS indefinitely. The other implication is that if you have a drive failure and that drive contained some non-replicated folders, you will almost certainly lose data. It's also impossible to upgrade the system drive, without doing a full restore from backup. Finally, if you do lose the system drive, you'll have to restore from a CD off another machine.

What's even more interesting is that you might not even use that feature all that often! One of the big features of WHS is that it can wake up all your machines at home from sleep or hibernate mode and back up them at night while you sleep! This is a full image backup, so you can now leave your data on your machine and not copy them over to your NAS unless you really need to share them. One big caveat is that the version of WHS that came with my EasyStore was 32-bit, so the recovery disk is 32-bit. If you need to restore a 64-bit Windows machine, what you'll have to do is to augment the drivers with 32-bit drivers via a USB disk. This is not for the faint of heart, but I performed a full backup and recovery of my 64-bit Thinkpad X201 with some hunting down of the various drivers on Lenovo's website, so I'm confident that the process will work. Obviously, if you don't run an all Microsoft Windows network, this feature will be less useful for you, though apparently you can use Time Machine with WHS. I've never met an Apple user who would condescend to buying a WHS though, so I can't imagine that this is well-tested.

One interesting thing is that in order to gain access to the NAS, your Windows boxes have to install a client. This turns out not to be a big deal: just download the client from the NAS (which exports a http server), type in the password, and away you go. Mac users can access the same folders via Samba.

But that's not all! WHS automatically exports videos, photos, and music over your local area network, which meant that for the first time, my PS 3 can now play videos directly off the NAS, something the NV+ could not do before. It also exports music via Firefly, so those of you who have Roku music players or SONOS will have no problems with exported music. The big feature for me, surprisingly, is photos. Photos now can be viewed on the big screen in the living room, letting you run digital slideshows off the NAS. I always knew this feature existed before, but what with having to copy data round on a thumbdrive, I never actually used the feature. I can only imagine that those with a XBox 360 would have just as much access to these features.

What's interesting to realize is that the WHS box is running Windows, which you can access using Remote Desktop. This lets you install CrashPlan, for instance, and get automatic off-site backups. If you're too lazy to transcode everything for the PS3, you can also install PS3 Media Player, so transcoding automatically gets done for you by the WHS. I also installed PlayOn, so the PS3 now has access to YouTube and Hulu. Now I can turn off/hibernate my big power hungry desktop whenever I'm not using it.

With all this going on, you might think that the puny Atom 230 on the NAS would be overwhelmed. Well, I recently did 3-4 things on it at once. I started a multi-hour copy job, started a 3 hour restore job, had Crash Plan running in the background, and played a video off the easystore from the PS3. The Easystore didn't even crack a sweat: CPU utilization was at 50%, and the network utilization was close to 20-30%. The video played smooth as butter. Performance on the copy operation, by the way, was a little better than what I could get out of the NV+. The NV+ topped out at 5-6MB/s on my network, while I could get the Easystore to give me 10-12MB/s on writes. I have no idea why the NV+ is so slow because it's apparently been benchmarked elsewhere with significantly faster write performance.

Then to top all this off, WHS had one more feature up its sleeve that pleased the heck out of me. It turns out that you can register a domain at homeserver.com, and set up account access to your WHS through the internet so you can have access to those files in your home directory anywhere you go. It's like having a massively unlimited Dropbox folder, though perhaps with a UI that's not as sweet once you're off-site. The NV+ advertised that feature but I was never able to get it to work, and it's very nice to see Microsoft doing it right. This by the way, also solves the problem of: "Hey, I've got this huge file I need to send to you, how do I get it over to you?" Just create an account for your friend, give yourself read-access to that folder, and have him login to your domain. The flip side of all this functionality, of course, is that you can no longer turn off your NAS when you go on vacation, but that's not that big a deal --- the Easystore also has a wake-on-LAN feature, which I'll test as soon as my huge copy jobs (for migrating off the NV+) are done.

All in all, my initial impressions of WHS and the Easystore are very favorable. If I'd known about all these features I probably would have jumped ships the last time my ReadyNAS died (yes, it died twice, once from corrupting its own boot sector and once from hardware failure). Obviously, it'll take months/years to see how reliable the hardware is, but the reality is, even if I have to build my own WHS box, I don't see why I would consider any other approach for my next NAS. Highly Recommended. Does anyone want a used ReadyNAS NV+ that still has about a half a year of warranty left on it?

Review: Philips Sonicare Healthy White Toothbrush

I had one of the old Essence Sonicare toothbrushes, but the battery was getting old, so when my brother gave me one of the new Healthy White toothbrushes I started using it on this year's Tour of the Alps. To save weight, Phil and I each brought one toothbrush head and just carried the toothbrush handle. I used to run the Extreme 3000 for trips because it used AA batteries, but with the new Garmin units, I had no other reason to bring AA batteries and the new Sonicare, together with the charger weighed less than the e3000 with AA batteries and USB AA charger.

The battery life on the new Sonicare is amazing. Phil and I toured for about 12 days, with each of us using the tooth brush twice a day, and the battery never gave out, well exceeding the 2 week specification. (We'd shipped the charger back to our hotel after the St. Moritz trip) The toothbrush cleans exceedingly well: after my latest dental examination, my dentist decided to put me back onto a 6-month cleaning schedule, as opposed to my previous 4 month cleaning schedule.

The other major change is that the toothbrush head is now a bayonet mount instead of a screw mount. This makes swapping heads faster, and there are no longer any grooves for gunk to build up. Unfortunately, there's also a little space between the bayonet mount and the top of the toothbrush, so water and gunk does get into that space and build up, so I'm not sure this is any better. I do appreciate the newer lighter weight design, as well as the smaller heads (which unfortunately, are also more expensive than the older heads).

All in all, recommended.

Review: Playstation Move Bundle

Slickdeals found me a Playstation Move Bundle for $50, so I jumped on it and bought one just to see if it was any different from the Wii. I like the Wii just fine, but on a 1080p display, old-style video game resolution has started wearing on my eyes.

In the box, you get a Move Controller (you're advised to buy a second one), a Playstation Eye USB camera, and the Sports Champions game. Sony boasts that the Move is a more precise mechanism than the Wii, mostly because the video camera is used to precisely place motion. The move controller's got its own lithium ion battery, rather than taking AA batteries. It charges via a mini-USB port.

There are a few funky things about the setup. One is that you'll have to calibrate the controller every time you start a new game. Basically, you hold your controller in 3 different places to the camera knows what the parallax is and how far you are from the camera in default position. Secondly, the angle of view of the camera isn't wide enough if your living room is so small you have to stand within 2m of the screen. This is a relatively minor annoyance as the game will inform you if it can't find your controller optically, but those of you with small living rooms should not buy this.

Now onto the games. The biggest draw for me was the ping-pong game. The game has amazing fidelity. My mother-in-law, for instance, has never so much as played a video game in her life, but she easily picked up the controller and kicked my ass in this game, once she got past the calibration hurdle. That's pretty amazing. Spins, smashes, and drops clearly reflect how you hold the controller and how you move. This is a lot of fun and well worth the price of the bundle by itself. The archery game was fine, but the use of two controllers is a bit of a gimmick. I think my accuracy was actually worse with two controllers than with one. The gladiator game was fun, but I don't think it shows off the controllers very well: either that or I'm playing it wrong. Volleyball is the one game where having two controllers felt like it helped. The game's interesting, but there's something missing from the gameplay. Frisbee golf is interesting, and I found myself playing through a few courses only to discover that there weren't enough courses to keep me playing (there's a lot of repetition) Finally, there's Bocci, a tossing game that's clearly very similar to bowling. The increased precision is extremely demanding.

All in all, I'm very pleased with the purchase. I was surprised to find that I used the move often enough during rainy days that the controller needed recharging a couple of times. Recommended. I'm not sure you'd need to buy any more games to get your money's worth out of the controllers --- the bundled game is that good. I'm pretty sure if you wait until black Friday, the Move will be widely discounted this year.

Review: The September Issue

The September Issue is a documentary about Anna Wintour, and the process of publishing Vogue's September issue, which is apparently a big fat telephone book of a magazine devoured eagerly by fashion aficionados. I have no fashion credentials, and no real interest in the genre, so why did I watch this movie?

The short answer was that I was stuck with nothing but my Nexus One when my Kindle broke on this year's Tour of the Alps, and I had stuck this into my N1 thinking that it was about magazine publishing. I'm also a photographer, and thought it would be interesting to see how a magazine worked.

The movie opens with Anna Wintour defending the interest of fashion. It definitely came across to me very much as a "Thou dost protest too much." Then we're treated to meeting after meeting of Wintour's staff discussing what needs to go into the issue. The secondary star of the show is Grace Coddington, a senior editor who puts together the photo-shoots and proposes layouts for Wintour to dispose. She's clearly very passionate about her work, and is extremely unhappy when Wintour takes out photos that she put a lot of work into or that she particularly likes.

Mid-way through the movie, we see an interaction between Wintour and her daughter. The daughter declaims to the camera after a discussion with her mom about some upcoming layouts: "There's no way I'm going to go into fashion. I can't imagine a life much more shallow than spending all your time thinking about clothing." I thought that was a great counter-point to the film's opening.

Did I learn something about magazines? Yes. It's amazing how much every page of the magazine has been photo-shopped. One scene after another, you see editorial staff bringing up photoshop and tweaking the photos. And they're not doing things like cropping, they're compositing backgrounds, removing skin blemishes, that sort of stuff. It's pretty impressive how quickly these professionals work, but at the same time, it hammers home to me how every image in media is suspect, except for perhaps a few magazines like National Geographic that have made a point of emphasizing image integrity.

In the end, the movie was interesting enough for me to keep watching to the end, but I'm glad I didn't pay full price for it in the theaters. Recommended only if you've nothing else to watch on your N1 while cycling through Europe with a broken Kindle.

Review: The Long Run

After reading The AI War, I felt compelled to go back and read The Long Run, which I last read probably 15 years ago or so.

Daniel Keys Moran paints an rich tapestry of future, and given that this book was first published in 1989, features several new features such as the use of "web" for internet. The book reads a lot like a summer blockbuster movie. Many plot sections are improbable, and Trent, the protagonist, is cocky, sure-footed, but also has a big enough ego that he constantly makes mistakes that jeopardizes his goals. There's good use of foreshadowing all through the book, and Moran makes use of his long range plot for the series to provide quotes. Looking at The AI War, I'm disappointed that we never see Denice and Trent together again, and that loose end was never tied up.

Nevertheless, a quick, interesting read, and fun airplane novel. Recommended.

Political Considerations

Startup Engineering Management deliberately excluded politics from its discussion of management. Since I'm a lousy politician by nature, I felt unqualified to write about it. A couple of my friends are good politicians, but I can't persuade either of them to write a book (or even a blog post) about engineering politics at large corporations, which I think is a pity.

Recently, however, I was made aware of a couple of political situations at a well-known large corporation that merits discussion in a blog post.

Exec A: Having worked himself up into a senior executive position on the major product at Corporation X, he was told upon a reorganization that he was now going to run a different area of the company. While important, this was not as critical and he recognized it as a demotion. He immediately tendered his resignation, and was only persuaded to stay long enough to make a transition smoother by the CEO.

Exec B: Was at corporation Y since the early days as an early employee, and was instrumental in many of the design decisions behind the property. After a political stumble, she was asked to leave her current role as the major design driver behind the the product and take on a newer "emerging" product. This was widely recognized as a demotion, but the executive stayed on anyway, while the emerging product team started working around and ignoring her because she clearly no longer had the ability to effect change.

One could say that this is a possible difference in style between the way men and women approach status changes, but I'd argue that in this case, staying is the wrong decision. When you've lost political clout, staying on signals that you will accept further demotions in the future, which is debilitating for your future career. By contrast, leaving immediately signals that you will not accept further degradation, and if you've got a proven track record, also sends a message to your future employer. These political considerations are not fun to think about and demand self-awareness and total honestly about your current position. The penalties of not assessing your current position honesty could easily end up with you being ineffectual at your job, which is not very satisfying. Don Neufeld at Obvious a few weeks ago said this to me, "Most people have a loss aversion about losing their jobs. Startup people have a loss aversion about wasting their time." To me, sitting in a position, no matter how lucrative, when you're ineffectual is a complete waste of time and should be avoided.

Scalability

I've been helping various startups, and one of the things that's impressing me is how frequently these startups are launched on new infrastructure pieces like Ruby on Rails, written mostly by people who're not really trained formally in computer science or software engineering. This is a triumph of modern programming tools: I certainly didn't think that we'd get to a point where essentially product managers can actually write code, and asking these teams to execute in C++ or even Java would have set them back months. Even better, these startups don't even run or own their machines, choosing instead to use Amazon Web Services to launch and scale.

That is, until they suddenly hit a scaling inflection point and then someone like me gets called in to help out with the architecture and scalability problem. This is a good thing, by the way. Too many software engineers fresh out of school get hung up on the latest performance or scalability techniques and use them too aggressively when there's no need. It's far more important to launch a product quickly and get it to the point where you have product acceptance before you worry about performance. Even then, some of the latest techniques get you nowhere. One of my favorite examples came when I was at Mirapoint. A team of folks were working on the mail transfer agent. This is a relatively straight forward piece of code but when designing for high performance, they had decided on an architecture that made use of multiple threads and that made debugging hell. Brad Taylor came in, took a look at it, and rewrote the entire thing using a single-threaded select loop. Not only was that single-threaded select loop easier to debug, it actually ran faster, because the processor wasn't doing all those crazy context-switches just to get simple things done. In general, when scaling a product, your best bet is to first design for easy debugging and easy replication (so you can get horizontal scaling) by spinning up new processes rather than throwing the universe into an address space and launching multiple threads. The first person to articulate that philosophy to me was Michael Wolf at a dinner conversation with me and Steve Grimm.

Back to the startup. The problem with launching a startup on AWS and on Ruby on Rails is that when you hit the scalability inflection point, the easy solutions are not available. For instance, one company I helped were hammering their MySQL database with too many requests. While the number of queries were potentially large (and there was a fair bit of writing, so read-caching wasn't helping), their actual database was small. If they were hosting their own infrastructure instead of running on AWS, a simple straightforward solution that would have required no programming, would have been to just install a SSD (or if you have money burning a hole in your pocket, one of those crazy Fusion IO PIC boards, which bypass the SATA limitations and use the full bandwidth of the PCI bus for IO). SSDs are expensive, but even $400 or $8000 a pop is cheaper than the time it would take to rework the database to a NoSQL solution. Unfortunately, none of the existing cloud solutions will let you specify SSD-type performance for the machines you request.

Since they were essentially using MySQL as a blob store, they thought about exploring one of the NoSQL solutions. But the amount of data they had was so small it would have fit into main memory (of a relatively large server), so they could have potentially could use a simple shadow hashtable approach with a background thread to write the shadowed hashtable to disk for persistence. Unfortunately, that requires real threads and some simple locking, and the default implementation of Ruby doesn't support kernel threads (though JRuby does). Furthermore, by using Ruby On Rails, they'd written themselves into a corner where it would be difficult to extract the data layer out of their code so they could write to a NoSQL database anyway. What's interesting to me is that these were the people smart enough to know that they'd run into scalability limits with their software and infrastructure. There were probably many others who did not and chose to muddle along.

When I finally read about how Twitter was a big user of Ruby, all their scalability problems finally made sense. At some point, you do have to throw away your prototype and rewrite everything if you want to scale.

Review: Blood of Elves

If you wanted to prove that dead-tree publishers are brain dead and will not be missed during the e-book revolution, exhibit #1 would be their handling of the Witcher saga, of which the third book is Blood of Elves. Whereas the first novel, The Last Wish was entertaining and a lot of fun, Orbit chose to release the third book in the series next, skipping over a lot of the back story for Blood of Elves.

The story revolves around Geralt's child surprise, whom he apparently recovered in the earlier book and finds himself having to care for. The novel moves forwards in spurts, with lots of time between many sections. One of the worst things, however, is that you never get a good overview of what's going on. A lot of hinting, and lots of wheels grinding in the background and a little clumsy exposition of various factions plotting.

We do see a few characters that showed up in The Witcher, but the reality is, the book ends before giving us any satisfaction.

Not recommended.

REI Series of Talks is Over!

From BayArea

At a WorldCon seminar, Sandra Tayler told me that people get hung up on the bookstore signings, and that's why they try their darnedest to be published by a traditional publisher rather than being an independent publisher. Well, even if you're an indie person, there's no need to give up on doing the bookstore signings, you just have to arrange it yourself. An Engineer's Guide to Silicon Valley Startups and Startup Engineering Management don't lend themselves naturally to public venues (though I've certainly given plenty of talks covering those topics in private venues), but Independent Cycle Touring was a completely different beast. I started off by giving a talk at the local Sports Basement, but after chatting with REI, was put in touch with Polly Bolling back in March about the possibility of doing a series of talks at various REI. Strung together over a period of about six weeks, this is about as close to a traditional bookstore tour as I'm likely to get. Polly had great insights as to what worked for an REI talk and what doesn't. She suggested that I focus the talks on Europe, and that destination-oriented talks really got people in the door, so I refocused the talk around Europe. You can see the slides as posted earlier.

Getting into REI is a long lead time process. It wasn't until late May that I was confirmed as booked, and it wasn't until June that I was given the OK to publicize the series of talks. I had no idea there were so many REIs: I could have done even more REIs, but at some point decided that I really didn't need to go to all of them.

The turnout at various REIs was widely disparate. I had as few as four people, and spoken to as many as 70 people in a fully packed room. The venues ranged from a professional looking classroom/community room to a warehouse where REI employees would make room in the space just an hour or so before the talk. With pleasure, I can say that the projectors and screens were always more than acceptable, and equal to what I found in industrial settings. The employees (including Polly herself) were always happy and enthusiastic and willing to do whatever it took to make the talk work. It was a good thing that I was given a few smaller venues to work with first before I started hitting the large ones (Berkeley/San Francisco/Mountain View/Saratoga). This gave me a chance to refine my talk, and let me get a good view of what played well with the audience and what didn't. I knew I had hit my stride when members from the Berkeley audience came to me after the talk and said, "Best REI talk I've ever been to, and I attend nearly every one." That was very gratifying. One reason I'd gotten good at talks, by the way, was that giving talks at Google was even more demanding --- if you did not proceed at a pace fast enough and fun enough to keep an audience's attention, Google employees would flip open their laptops and check e-mail instead. Authors/speakers who were used to a less demanding audience probably did not have a good time at Google.

Polly told me to keep my expectations for selling books low, saying that selling one or two books would be about right. Well, I kept my expectations low, but my conversion rate was about 12-15%: in other words, about 1 in 10 people who saw the talk would buy the book. That's far better than say, Adwords or classified ads, so I'd say that the talks were definitely worth the time. It was also interesting to see how every REI was different: some clearly catered to more cyclists than others, and it was clear that the North Bay had a wildly different demographic than the South Bay.

All in all, I probably won't try to do another book tour type event for the foreseeable future. I can see why some authors find them exhilarating: there's nothing like speaking to a fully packed room with an engaged audience, and the people flooding you with questions, asking to buy a book and asking you to sign one is extremely flattering. It's a lot like the high you get from getting to the top of a climb and facing a glorious descent afterwards. Ultimately, though, you still have to get back to writing interesting work for an audience that is willing to pay for it, and the talks and signings are a bit of a distraction from it, though I'm grateful for the sales and hope it sparks future sales!

(If you want to watch a short excerpt from the MTV talk, I've got one up on YouTube)

Review: The AI War

Daniel Keys Moran's Continuing Time series has been one of my favorites. He's a good writer with compelling characters that keep you reading, no matter how absurd the plots are. I once made the mistake of lending The Long Run to a friend on a bike tour, and during the night she retired to her tent and stayed up all night reading instead of sleeping and getting ready for the next day's ride. If you're unfamiliar with the series, read The Long Run and The Last Dancer before reading The AI War. The web-site for buying the book's incredibly unintuitive, expecting you to return to the product page after purchase in order to make the download, so you might want to visit Amazon instead.

The AI War is a Trent novel. Trent is one of Moran's great characters, and here he's involved in thwarting the Unification's big project. The plot-holes are pretty large: why build one giant ship instead lots of little ones. But the details are a lot of fun. Moran is a programmer by trade, and it's good to see his model of how a 10X programmer works. Trent infiltrates the project as the chief engineer, and soon puts the project on schedule. Along the way, we get a biography of a few side characters and some future sub-plots are set up.

If I'm annoyed by a few things, it's that the book's far too short (it says "part one"), and there's no AI war (yet) that as far as I can tell. I also wanted to see the unresolved plotlines from The Last Dancer filled in. Unlike other novels in other multi-part series, however, at least this is not a book where nothing happens, and it's a compelling read start to finish (I bought the book last night and it grabbed me by the eyeballs and made me stop reading the other book I was reading). You could read this book without reading any of the other books in the series, but I think you'd find the book a little less fulfilling without the rest of the back-story. Also, The Long Run is still a better read. Go buy it already.

Execution Strategy and Business Strategy

Rebecca Frankel shared on her Google Reader Feed this image:

I think it's a great example of execution strategy. A frequently used execution strategy is to standardize on one platform and optimize on delivery that way. The nice thing about this strategy is that if you're the startup and the incumbent has built in legacy systems and costs that keep them from executing on the same strategy, you'll have a built-in advantage that will continue for a good long time. For instance, it's hard for an airline to switch the hubs it's using after it's been locked into a long term contract. And obviously, it's hard for incumbent airlines to sell all their fleets and standardize on the 737. The strategy that RyanAir uses, by the way, was first pioneered by SouthWest Airlines. A good execution strategy like this can be easily explained to all your employees to the point where everyone knows what the strategy is, leading to broader alignment.

At Google circa 2003, the execution strategy was straight-forward: build clusters of commodity machines driven by a common software infrastructure so scaling was straightforward. Once MapReduce was adopted, for instance, your mapreduce jobs were datacenter independent and could be run on any number of datacenters. Similarly, all projects could share a single set of site reliability engineers, release engineers, etc., and your resource constraints could be relieved by effectively hiring in all these areas.

The problem comes when you have a new product that doesn't fit your existing execution strategy. Orkut, for instance, was initially written using Microsoft's .NET framework. That didn't fit in with what the rest of Google was doing. It rapidly became a popular product, and the system started falling over from the huge number of requests. The team was staff-constrained, and few engineers inside Google wanted to work on a product that was clearly way out on the left field with respect to Google's execution strategy. To be honest, nobody knew how big social networks were going to be. The result was that it took a while to rewrite Orkut to conform with Google's execution strategy, and by the time it was done enough time had passed and enough users had migrated to another social network that the rest was history. In retrospect, the right thing to do should have been to spin Orkut off, have it raise its own funding round (with Google kicking money), and race quickly to deal with its scaling problems independent of the rest of Google's infrastructure. Facebook might still have won, but at least Orkut wouldn't have been paying Google's strategy tax. Microsoft has its own strategy tax here in that everything has to be tied to windows, but I think even Microsoft's starting to move away from that with its phone and tablet entries.

Business strategy is a whole different animal. In some ways, it's like playing a strategic board game with your business. I'll give you an example. Microsoft invested $240M in Facebook in 2007 at the then stunning valuation of $15B. At that time, Facebook was not profitable (and would become profitable based on Microsoft's guaranteed revenue), and it looked like Microsoft was desperate, throwing money at Facebook. Well, 4 years later, it looks like a brilliant move. Not only does it look like Microsoft's investment will pay off (at least 4X, maybe more), Facebook's been a tremendous thorn on Google's side, probably accounting for no small amount of management distraction, time spent launching (and re-launching) competitive products, and I'm sure no small drain on Google's engineering team. Time will tell as to whether Microsoft's acquisition of Nortel's patent portfolio, essentially forcing Google to buy Motorola will be similarly smart, but spending $4.5B (and that's split between Apple/RIM/Sony/EMC, etc) so that your competition has to spend $12.5B (and ends up having to run a hardware business that's not particularly profitable --- Motorola's the weakest of the Android manufacturers) looks pretty smart right now.

Another company which is good at this is Amazon. The Kindle, for instance, unusually attacked the market from a completely different angle. It's early adopters were not the usual hip 20-somethings, but were the older generation: people who still read and whose deteriorating eye-sight and arthritis made the Kindle an almost must-have. This was so much ignored by other vendors (Apple included) that by the time other ebook stores launched, nobody else has made a dent in electronic book distribution. By ensuring that the Kindle App is available for nearly every platform, Amazon has gotten a choke-hold on electronic book distribution that's only starting to be realized at this point.

Someone told me a little bit back that Amazon's S3 services were priced at below cost at launch. Basically, they bet that they could drive costs down a bit, and that customers would see the move to their cloud services as a no-brainer at those prices and thereby gain them further economies of scale. At this point, I've run into lots of companies that have based their businesses on S3, but comparatively few who've done so on Google's AppEngine infrastructure AppEngine is a bit of a red-headed stepchild at Google because it can't be priced to produce high margins, while Amazon's very much used to low margins.

Obviously, business strategy is of no use if you screw up your execution strategy (or if your product sucks --- nothing ever saves you then), but ideally you want everything in place. Amazon's been the stealth surprise in the past few years in places that looked completely unrelated to e-commerce because of this. At the same time, Microsoft's not being doing so well at execution but its business strategy successes are being ignored by the press, and I think that counting them out would be a mistake.

Review: The Dragon Never Sleeps

The Dragon Never Sleeps (DRM-free kindle-compatible edition) was a difficult book for me to read. The first time I tried to read it, I couldn't become interested in the characters, and abandoned it. However, at this year's WorldCon, Cook mentioned that it was one of his proudest novels, so I went back and read it again.

The universe Cook weaves is a compelling one. You've got organic military vessels that are nevertheless non-sentient. Starships travel through space on strands of the Web, which turn out to harbor a deeper secret. The war against methane breathers comes with deeper intrigues. Planet-side, the feudal structure of the milieu provides us with a key source of human intrigue. Just as interesting, cloning is an option and is frequently used, and used imaginatively by the author. Yet all this is done without long expositions. It all just happens inside the text. Cook is the master of the brief sketches and dialog that brings out character, and he uses that in this novel in spades. As you might expect, there are no plot-holes here. Everything makes sense if you've been paying attention, yet the surprises are genuine. It's also interesting that the science fictional world portrayed is one where technology is more or less static, and has been for thousands of years, so one military force (guardships) could be designed for immortality without the risk of obsolescence.

There are flaws in this book. The big one is that there are too many characters for you to properly care about, and the important characters aren't fully high-lighted, so if you're going along rapidly you might have to go back and re-read a passage when one reveal or another happens. Cook also flips between nick-names, titles, and real names all the time, which could be confusing, especially since the character cast so so large. All this combined together to make an unusually long (by Cook's standards) book means that the reading gets too dry at times and I had to take breaks. It took a long time to finish this book.

Nevertheless, if you're a fan of Cook's characters, matter of fact exposition, and want to see what he does with science fiction, this is definitely recommended (unlike Passage At Arms. Just don't expect it to be a quick airplane read.

Location Still Matters

This year's been interesting as I got invited to several startups either to talk or to give advice. Usually, I try to mix it with another visit if it's in the city, so I don't make the trip to San Francisco just for one thing.

One of the fascinating things is that San Francisco has a pretty active startup scene, but many of them are hurting for engineers. After talking to several startups with ambitions of growth but who can't seem to hire decent engineers no matter what, I'm coming to the conclusion that the more technically challenging your startup, the more important it is that you be in Silicon Valley, rather than being able to locate elsewhere.

Why is that? For technically challenging problems, you want people with a decent amount of experience doing the engineering. I'll take an example: Facebook managed to get Jeff Rothschild to lead its engineering team fairly early on. Jeff, by the way, doesn't get nearly enough credit for making Facebook as successful as it has been. It is doubtful that Facebook would have been able to recruit and retain Jeff if it was in San Francisco rather than Palo Alto. The same probably would have gone for Google's Jeff Dean and Sanjay Ghemewat. For whatever reason (people tell me it has a lot to do with schools), parents prefer living in the South Bay. I've lost count of the number of people I know who moved to the city when they were single and childless, and then moved back down south once they had a kid.

The result: if you want to grow past your first 50 engineers or so, you'll either have to settle for a less technically competent population, or you'd have to move south. What's surprising to me is how things I wouldn't have expected to be technically challenging turn out to be such. For instance, I would have guessed that Twitter wouldn't need Google-quality engineers, but that turns out not to be true.

This doesn't mean that San Francisco startups can't be successful and make lots of money. For instance, AirBnB and Zynga will be incredibly successful. Zynga has a famously low technical bar, and one of my friends came back from an interview saying that being the smartest person there wasn't enough even if it did make her rich. Obviously, being in Silicon Valley is also no guarantee that you'd be able to attract technically competent employees (Friendster was in Mountain View, for instance). But by and large, I've been amused to watch Cloudera move steadily south (from Burlingame to San Mateo and now Palo Alto). By the way, I don't think Zynga's wrong to have a low technical bar: there's no need to pay for top-end talent if your problems don't need top-end talent to solve it.

Many designers have argued to me that design talent is easier to get in San Francisco. I'm not a designer, so I don't really know, but let's say I give you that point. The problem is, to realize your design, you probably need only 1 designer for every 10-20 engineers. And of course, Apple is right in Silicon Valley, and whatever you might say about Apple, you can't argue that their design is inferior.

Ultimately, if you're a startup, think carefully about what your business is. If you never need more than about 50 engineers, I think San Francisco is fine. If you believe you're really in the media business, San Francisco's probably better (be very careful, though --- Yahoo! thought it was in the media business --- that turned out to be false!). But if your startup idea needs a sizable number of Google-quality engineers to succeed in the long term, you really should be in the valley.

Now the real puzzle to me is that there should be far more startups in the Berkeley area than they are. They've got Cal, which has a strong computer science department, so recruiting for engineers should be no problem. My guess is that the city of Berkeley does not view startups in a friendly fashion, and it would be very difficult to find cheap space in the area. Inktomi (founded by Cal professor Eric Brewer), for instance, famously moved out of Berkeley (to Foster City) as soon as it had to scale.

Span of Controls

Coincident with the launch of Startup Engineering Management, I'd been asked to help out at a few startups, two of which were Obvious and PlayMesh. A common question that came up at both places was: What's the appropriately wide span of control in management.

I believe the answer to that question is: "It depends." If you look at industry wide span of controls, they're somewhere around 6 to 1. That is, every 6 engineers will have a manager. If you examine that carefully, however, what you'll notice is that this arises typically in larger corporations. In those corporations, what's happening is that aggressive go-getters who don't get promoted will quickly leave, and the only way to retain such people is to give them management positions long before they're ready. (An alternative is to set up a separate engineering ladder, which was advocated as far back as The Mythical Man Month. That doesn't work as well as its advocates will have you believe) Effectively, at large corporations sporting a 6:1 engineer/manager ratio, what you are doing is training engineering managers on the job, where the manager is essentially still expected to perform individual contributor duties in addition to doing management.

At well-run startups where most engineers who are brought in do not need a lot of coaching, the appropriate span of control is closer to 20 engineers. At that level, the manager can't do a lot of coaching, but more importantly, he can't possibly do any micro-management, which is irritating if you've hired high performance engineers. Essentially, the manager has to lead by setting direction, not provide management or mentoring at the task level. That doesn't mean he can be non-technical, because you need to be capable of understanding detailed software/hardware architecture in as much as it affects your product. To give an extreme example, Wayne Rosing in his early days at Google had all 100 engineers directly reporting to him. Having participated in those structures before (as described in An Engineer's Guide to Silicon Valley Startups), it was extremely exhilarating, and yet Wayne (and Bill Coughran) always knew what the problems were and how they could help every time I came to one of them with one (very often, the way they helped was to send a one word e-mail: "Approved.").

If you're promoting engineers into management positions who have not managed before, you will need to be closer to the industry 6:1 ratio. However, if you're hiring a manager from outside, your bar needs to be a lot higher: they need to be able to handle a span of control of 20:1. Many startups do not hold incoming managers to that standard, and therefore end up with poor management. I'll give you a concrete example: Facebook does not hire managers from outside, because they've discovered that the practice does not work. However, they do hire directors from outside with some degree of success (though less so than with directors who were promoted from inside), and one reason for that success is that most directors hired from outside have already proven themselves capable at the 20:1 ratio.

At the tech lead level, however, you probably will still need the 6:1 ratio. But tech leads are by their nature not going to provide the full range of management functions.

Is there a way to short cut this process? Yes. One of the best tips in Startup Engineering Management is actually one that came from Yishan Wong: when hiring engineers, try to look for engineers who've managed before and are willing to come back as an individual contributor. This lets you promote from within once you need managers, and also gives you managers that don't consider management an more important job than engineering.

One interesting note is that these numbers are extremely similar to what the U.S. military uses in the army: a squad leader commands a group of 8, and a platoon commander commands three squads for a group of 24. The squad leader is very much like a tech lead, and the platoon commander is the lowest level officer in the army. While you might argue that military jobs aren't as cognitively challenging or creative, I'd counter that you should be also much more demanding in your recruiting process than the military, hence the similarity.

Startup Engineering Management gets .mobipocket and .epub

One of the workflow changes I made when publishing Startup Engineering Management was to use Adobe InDesign instead of Microsoft Word or Open Office. It's more cumbersome, given that it's an entirely text book, and it makes proofing hell, but the new version of InDesign actually makes it somewhat straightforward to produce EPUB and Mobipocket files (via Calibre).

The result: you now get the book in all 3 formats (PDF, EPUB, and Mobipocket) when you buy it. If you've bought the book and want it in other formats, please let me know and I'll rectify the situation.

Independent Cycle Touring in Europe: The Presentation

Independent Cycle Touring in Europe

View more presentations from Piaw Na.

If you've been following this blog, you know that I've been giving a series of presentations at REI about Independent Cycle Touring. I hadn't put up the slides before because they were under revision all the time (especially between presentations things would change), but now I think I've gotten it stable, so those who're interested can view it.

If you're in the Bay Area, the last two presentations are September 19th at Saratoga, and September 29th in Mountain View. Registration is free, so show up and see the slides in full resolution! In addition, I'll always provide pre-flight entertainment for those who show up early. The reception to these presentations, no matter the size of the crowd, has always been very positive, and you can't beat the price.

Now Shipping: Startup Engineering Management

My latest book, Startup Engineering Management is now shipping.

Until now, all my books have been relatively independent of each other: there's no reason to believe that one person would buy An Engineer's Guide to Silicon Valley Startups and Independent Cycle Touring at the same time. The topics are very different, and you're unlikely to be in the mood to read one book or the other.

However, folks are likely to want to read Startup Engineering Management right after (or before) An Engineer's Guide to Silicon Valley Startups, so for the first time, I've provide one single page shopping cart where you can buy any (or all) of the books on one page. As a bonus, if you buy $50 worth of books (any 2 books), I'll provide free shipping. Obviously, this only applies to paper books, as electronic copies always have free shipping.

Incidentally, I recently met with both Obvious and PlayMesh to discuss engineering management, and the feedback on the material that we discussed (which all went into the book) has been very positive. There are other reasons to read this book even if you're not going to be a manager, and I'll get into that in the future. Watch this space.

Review: The Lost Fleet: Beyond the Frontier: Dreadnaught

I've been buying all the previous Lost Fleet novels on Kindle mostly because they were priced right, and written pretty much as airplane fodder. You don't have to think very hard, and it's a lot like eating candy: you won't get overfull, and you can eat a lot of it at a go. The books are relatively thin, and you can easily zip through a couple of them at a shot.

Campbell's publisher has decided that Campbell's (aka John G Hemry) popularity means that they can price his books as a hard cover, so Dreadnaught, which begins a new series now spots the cover price of $15.82 (and a Kindle price at $12.99), which puts it easily out of the impulse buy range.

Unfortunately, in length, plot, characters, and interest, this is pretty much the same as any of the previous novels. We have John Geary confronting impossible situations in his fleet, making quick decisions that allow him to escape nicely as background problems escalate. There's a cliffhanger at the end, but most of the book can easily be zipped through like the airplane fodder that Campbell's so good at delivering. Nevertheless, the series is getting a bit old, and the reveals are starting to feel like they're deliberately drawn out to milk the series for all its worth.

Not recommended. Wait for the entire series to come out, or check it out from the library if you must.

Charts and Tables from Independent Cycle Touring

One of the things I wanted to do but kept forgetting to was to extract all the charts and tables from Independent Cycle Touring and put it in one document so readers could easily print out copies and use them for packing or planning trips. I finally got around to doing so and you can now download all checklists and tables.

Review: Girl Genius Omnibus 1

Girl Genius has won the Hugo for best comic several years running. While they have everything on the web, it's much faster to read comic books on paper, so when my local library had the book I picked it up.

Humor is tricky. For instance, some people find fart jokes funny, others not so much. Some find zany characters like Rumiko Takahashi's Ranma 1/2 to be great, I personally characterize it as: "her idea of character development is to add more characters."

Unfortunately for me, Girl Genius falls into the latter category. The philosophy is to just keep adding more characters in the hopes that you'll find something funny somewhere. You could approach Girl Genius as a serious story, but that doesn't work very well either. The plots are unbelievable, and while there's a long running plot, most of the time you get just one gag after another, without a lot of plot exposition. There're also plenty of digressions that seemingly add nothing to the story. I say seemingly, because of course something might turn out to be relevant a few books later, but I haven't got the patience (nor do I necessarily want to spend the money) to run out and buy the books or click through the web pages just in case there's a pay off in the future.

All in all, if you like Ranma 1/2 or love lots of gags, this is the comic for you. For everyone else, I'd suggest paging through the first few pages to see if it grabs you.

Review: Big Bang Theory Season 3

I saw episodes at random times, mostly on the N1. This is the season that made Jim Parsons a major star (or rather, the critics finally agreed that he wasn't a fluke), and it shows. Nearly every episode is hilariously funny, and the writers take pains to get all the details of geekdom correct.

The season even ends with a cliff-hanger! All I can say is, I don't usually watch TV, but this series will have me watching every episode I can get my hands on. The Stan Lee episode definitely had me laughing out loud while sitting on a train. Highly recommended.

Review: Jack of Fables Vol 2-4

While Fables keeps going from strength to strength, Jack of Fables was for me, a bit of a dud. I read the first 6 issues but it didn't compel me to spend money, so I checked Vols 2, 3, and 4 from the library to see if got any better.

The story has to overcome several problems. First of all, Jack himself is an incredibly unsympathetic character. Secondly, the problems encountered in Jack of Fables aren't all that interesting. You get impatient with the character's inability to see the obvious, and one would think that with immortality, even the most insipid personifications would eventually realize that his capers are repetitious and his continuing attempts to get rich never end well.

The art is good, but not so good that you can forgive the relatively lame stories. The introduction of the literals also draw a yawn, which is one of the many things that made Fables 13 boring and silly.

The mystery of why Fables was so much better was solved when I met Willingham, who said he handed over Jack of Fables to Matthew Sturges, because he felt that Matthew deserved a break. Well, Sturges' talent isn't in the same caliber as Willingham's, and it shows.

This series is only worth checking out from your local library.

Review: How To Train Your Dragon

At WorldCon, there was a panel entitled "The Real Revenge of the Nerds", where the theme was the recent spate of movies where the hero is a nerd and indeed gets the girl. How To Train Your Dragon would be exhibit #2 in that discussion. Exhibit #1 properly belongs to The Social Network, not only because it single-handedly raised CS enrollment nation-wide, but also because the antagonists, the Winklevosses, are classic good looking athletes.

The story revolves around Hiccup, who's the lone weakling in his village whose only hope of achieving social acceptance is to kill a dragon. When he finally gets a chance, he finds that he's too much of a wuss to do so... and to say more would be to spoil the story.

The animation is so-so, though the animators have cleverly avoided the uncanny valley. What's great is that our hero doesn't succeed through brawn: he succeeds through a combination of clever engineering, intelligent observation of critters, and ultimately, with kindness. To say that there is a total lack of such examples in typical children's movies (especially with male protagonists) would be under-stating it. In fact, it's the heroine of the story who supplies the brawn.

What's more, the protagonist sacrifices something real at the end of the movie in order to achieve his results. While everything does end well, the sacrifice makes it feel real in a way that recent Pixar movies (for instance) do not.

Highly recommended if you're a nerd.

Review: Why We Get Fat

I've pretty much ignored all the Paleo/Atkins/Low Carb diet craze the last few years, and Cynthia recommended Why We Get Fat as a way to see what it's all about.

Taubes has a good writing style and a lucid, clear argument as to why conventional diet and exercise doesn't work:

• The poorest people in the world don't eat a lot of meat but get fat anyway.
  
• The hunter-gatherers that exist today eat as much fatty meat as they can get their hands on.
  
• Carnivores are lean while Hebivores are fat.
  
• Insulin has been shown to be the agent converting sugars to fat. Having a constantly elevated level of sugars basically floods your body with insulin and therefore eliminates your ability to burn fat.
  
• The Atkins-type diets have been shown in some studies to reduce weight faster than other comparative diets.
  

Boy, vegetarians and vegans must hate this book. The prescription eliminates many items traditionally thought to be healthy and good for you such as fruits! (There's an assertion in the book that if you ate mostly meat, you probably don't need as much vitamin C)

Yet a few questions have answers that aren't very satisfying. For instance, why are the Japanese skinny? They eat plenty of rice (as do most Asian countries), and when you visit Japan, you're not going to see a lot of fat people around. Taubes says that these countries don't drink a lot of soft drinks, which is true, but a trip to your local Japanese supermarket sees plenty of sweet drinks. I'm not sure that this book holds the complete story: there's a lot about nutrition that we don't know.

Then of course, there's the assertion that exercise doesn't work. That one's weird, since I certainly know plenty of people who's lost weight from exercise. In any case, I found the book interesting as far as being an introduction to what all this high-protein/high-fat/low carb craze is about. Recommended.

An Engineer's Guide to Silicon Valley Startups now on the NOOK

Note that as with the Kindle version, this is the first edition. I have no expectation of significant revenue, but the BN store front was easy to use, so it didn't cost very much time.

I'm not expecting a Mac version. The iBookstore requires owning a Mac, which I haven't done since 2009 (and even that Mac ran Windows since I found myself repeatedly booting into it in order to run Quicken, etc).

Long Term Review: Garmin Edge 800

(Please also see First Impressions)

I've now lived with the Edge 800 for over 1700 miles, including quite a bit of hiking. The unit has survived a tour of the Alps with rain and plenty of sweat. A few notes:

• The unit's pairing with the cadence/wheel sensor is great. The only time I've seen problems with speeds being inaccurate is if the magnet is misaligned and hits the wheel sensor instead of zipping past it. When that happens expect to see speeds of 100mph or more. The cadence magnet slips easily, but is easily solved if you tape the magnet to the crank instead of relying on the zip-tie.
  
• Battery life is good. At 15 hours, you can expect 2 full days of touring on a complete charge if you forget to charge it one day. The battery drains at the rate of 5% per hour if the unit is not routing, which in practice means 20 hours. With routing, the drain is around 7% per hour.
  
• Routing is the same was other Garmin units, though sometimes address searches can get wonky.
  
• The unit really does work with full fingered gloves. This is due to the display technology, which also means that button pushes on screen are sometimes clunky. That's not a bad thing.
  
• In tunnels the wheel sensor pairing works well. In particular, Phil, who had the same unit, had his unit confused in tunnels and locked up, so I'm not sure how optional the wheel sensor is. A reboot solved the problem.
  
• Unit uploads are fast!
  

All in all, I'd say that this unit performed as expected and is reliable. Most people would probably buy an Edge 500 since most people don't tour, but for the touring cyclist, it's clear that this is the unit to get. Recommended

Review: Air Berlin

This year was the first time we flew Air Berlin. If you're a cyclist, there are only three viable airlines to Europe if you wish to bring your bike. Air Berlin, Air Canada, and British Airways. On British Airways, bikes fly free, but you have to fly through London Heathrow Airport, which many people hate (I've never had an issue with London Heathrow, but nightmare stories abound). On Air Canada, there's a $50 each way, which is reasonable, but they're not always the lowest cost carrier.

Air Berlin is almost always the lowest cost carrier, and they have a bike policy that's extremely friendly to cyclists: sign up for the topbonus Service Card, and you can carry your bike (at up to 32kg!) on any number of flights you take with them. The annual fee is 79 EUR, but in addition to unlimited bike carriage, you also get free early checkin for flights the night before, and an increased baggage allowance. You also get to make seat reservations (which is apparently a paid sevice). That makes it a good deal.

Good deals are useless if the airline loses your bike the way US Airways does. I'm happy to report that Air Berlin has excellent customer service. The staff is always courteous, and usually goes beyond the call of duty to get things done for you. Air Berlin schedules flights the way Germans schedule trains. That means connections are very closed together and you will find yourself in customs wondering "How the heck am I going to clear customs and make my next flight within 50 minutes?" Wonder of wonders, the German customs at Dusseldorf (Air Berlin's hub) are incredibly efficient and provided you don't dilly dally you will make your flight. We lost no baggage, and things were mostly on time. I can therefore recommend Air Berlin to cyclists wishing to bring their bikes to Europe and back.

Review: Olympus EPL-1

When my brother ran off to Europe for 6 weeks last year, he bought an Olympus EPL-1 for not much more than the Canon S95. What convinced me to recommend that camera was the DPReviews with the comparison shots that clearly showed the EPL-1 as being superior to many other more expensive cameras. Well, my brother shot tons of photos but didn't post any of them, so I had no idea what the photo quality was like.

Since XiaoQin was driving this year, weight was a non issue for her and she could carry the Olympus EPL-1, which we borrowed from him. There are a few annoying things about the Olympus EPL-1:

1. It stamps all photos with the caption OLYMPUS DIGITAL CAMERA. Yes, this is a camera that shouts at you and demands that you remove all those captions.
   
2. It has no orientation sensor, so you have to manually fix the orientation of all the photos that are shot vertically.
   
3. It does not have a rear control dial, so exposure control requires cumbersome button presses.
   
4. The auto-focus is piss poor.
   

I hoped that the extra quality of the EPL-1 would offset those faults, but the last one really did me in. One out of every three shots were poorly focused, and the screen wasn't sufficient to show it. Whatever auto-focus mechanism Olympus uses, it's not as smart as the one on the Canon S95/S90 series, since the S95/S90 screens aren't any better than the Olympus'. The flip side of it is that the camera is fast! Shot-to-shot wait times are nearly non-existent. Unfortunately, coupled with the problem auto-focus, that just means you just take more crappy photos. The camera does not have decent battery life, so it's a good thing my brother gave us 2 spare batteries. As with all other micro-four thirds cameras, it does not fit in a jersey pocket, and so would not substitute for the S90 that I was carrying. But the reality is, even on a hiking trip, the S90 shot better pictures, provided better control, and while slower, wasn't so slow that it didn't out-perform the Olympus EPL-1. I see that Olympus has lowered the price on this camera to be the same as the S95's. Nevertheless, it is a bad deal. There is no reason you wouldn't carry a S95 instead of the Olympus EPL-1. I found no circumstances under which the EPL-1 took better pictures than the S95. Given that the S95 fits in a jersey pocket, that's pretty damning. Not Recommended

Conclusion and Thoughts

If the Tour of the German Speaking Alps last year was an example of everything going wrong, this year nearly everything went right.

• We started a week later, and thus only had a couple of days of poor weather at the start.
  
• We booked a hotel nearly next to the airport avoiding the possibility of losing luggage right from the beginning.
  
• We scheduled the hiking at the start of the self-supported touring part of the trip, enabling us to ship our hiking stuff back to our airport, which enabled us to travel lighter and faster once we started riding.
  

Other notes:

• I'm getting older. We only had a couple of days exceeding 100km and 2000m of climb. As I get older and slower my days of doing those 100km/2000m days back to back seem to be gone. Part of it is that Sleep Apnea forces me to carry more weight up and down the hills, but the other part of is that my recovery isn't what it used to be. Last year I could pretend that it was the tandem's fault. Not this year.
  
• We actually did more cycling once we lost use of the car. The car enabled us to skip to "the good parts." The reality is, though, that cycle touring is about all the parts, not just the good parts.
  
• This is my first year where I could do both the French side and the Italian side back-to-back. The result: no contest, the Italian/Swiss/Austrian Alps are way prettier than the French alps. People who only ride in France because that's where the Tour de France is don't know what they're missing.
  
• If you're going to have rain for a week on the trip, having it at the end is much better than at the beginning. At the beginning you just lose shape and motivation. At the end, you're ready for a rest!
  
• When coordinating with a car, make sure that you pick good locations to meet up. In particular, meeting in the center of strange towns is going to make your driver very antsy, as towns are harder to navigate than country side. It's far easier to arrange to meet at an intersection or a very small town.
  
• Having a car was very nice: Phil said, "The car was totally worth the money!" We definitely had to thank XiaoQin for driving. A lot of the days would have been unmanageable or we would have had to take a less than optimal route when cycling. That said, I loved the unsupported part of the trip every bit as much, so I wouldn't go out of the way to get a car in Europe if everyone was up for riding every day (as was the case in the past).
  
• Remove the plastic dust caps from valve stems before mounting bikes on cars!
  
• We did our hiking in the St. Moritz Area instead of the Bernese Oberland this time. Compared to the Bernese Oberland, St. Moritz is less pretty, and not as interesting. It was worth doing once, but I don't think I'll revisit. Having now stayed at Wengen, Grindelwald,Lauterbrunnen, Rosenlaui, and Murren, I would recommend Murren for first time visitors and Rosenlaui for people who would like to get away from the Rick Steves/Lonely Planet crowd. Wengen is nice, but not as nice as Murren, and definitely not as nice as Rosenlaui.
  

Previous

Day 31, 32: Epilogue

We woke up in the morning to gloomy skies, despite attempting to sleep in. We were due at noon at a restaurant downtown to meet Stefan, so we had a bit of a leisurely breakfast before heading to town on our 24 hour ticket.

From Tour of the Alps 2011

The restaurant featured Swiss German food, with an entry way granting us great reasons to not smoke in the area. Stefan told us stories about his trip to the Himalayas. The trip proper sounded really fun, but the stay in Kathmandu and the aftermath of the consequences of the stay were ugly and off-putting. Stefan does a far better job than I did of explaining it, so I won't attempt to paraphrase him. Stefan as an outdoor enthusiast is second to few others, and his preparation was thorough and complete, so if bad things happened to him and his girlfriend, I'm not sure I want to risk something similar.

From Tour of the Alps 2011

Stefan took us on a river side stroll back to the train station, and it was lucky that he stayed with us because the train back to Kloten had a problem. We ended up hopping onto the train to the airport and then taking the airport shuttle back to Hotel Flyaway.

At 6pm, we went to the airport with our bikes and checked baggage, and made use of the early checkin to get our boarding passes and to get rid of the bikes. With the TopBonus service card, we did not have to pay to use this feature, and our cards let us bypass the line to pay to checkin! We then spent the rest of our swiss francs on dinner and on some extremely expensive Truffles du Jour at the Sprungli store, as recommended by Stefan.

The rest of the stay was uneventful, as was the flight proper. I'm happy to report that one and a half N1 batteries was all that was necessary to get me through the flight. (I did spend 2 hours on the X201 sorting pictures in lightroom --- when you run heavy duty photo-processing on the Thinkpad, the battery just doesn't last as long as when you're just typing away on Emacs) Phil performed the super human task of packing all the chocolate in his carry on baggage (he did not want to risk losing any of that precious cargo!), and not eating any of it on the flight. I did not trust myself, and checked all but one bar of chocolate, and that bar did not survive the flight. All our chocolate arrived safely, and now a month later, a lot of it is already gone!

Previous
Next

Price Drop on Independent Cycle Touring

While at WorldCon, I had a discussion with Sandra Taylor of Schlock Mercenary, who told me that I could get full color books printed in China at about $5 each, instead of paying the $15/copy that I'm paying right now. The problem? I'd have to print 5,000 copies at a time. Well, that's ok if I sell enough copies, so I'm going to start pricing the books as if I was going to get them from China and see how things go.

As of right now, Independent Cycle Touring is $29.95 for the paperback, and $14.95 for the digital edition. If you want both, it's $34.95. If this experiment works, the price change will be permanent. If not, prices will have to go back up. There's no way I'm ordering 5,000 copies of anything if it doesn't sell. Storage at my house is not infinite, and it'll be squeezed if I have too much inventory.

Day 30: Neuhausen to Kloten

We woke up in the morning to overcast skies and wet roads. Looking at the weather forecast, it looked like rain was in the cards for the next morning as well, so I called Hotel Flyaway and informed them that we would arrive a day early. We ate an anemic breakfast and got on our bikes and headed again for the Rheinfall, since our route would initially be along Swiss bike route #2.

From Tour of the Alps 2011

What a difference 12 hours made! Instead of the beautiful water, now all we saw was gray. Riding past the falls, we quickly found ourselves back in Germany!

From Tour of the Alps 2011

The gray skies continued all the way until we came back into Switzerland, but at last the rain stopped. At Flach we ignored the bike path sign to Eglisau and headed instead towards Embrach and Kloten. Since our GPS units already had Hotel Flyaway set as a way point, we had the units set, but ignored the GPS most of the time since the bike path signs were more reliable.

From Tour of the Alps 2011

Upon leaving the Rhein, the route led relentlessly uphill for an hour or so, but at a gentle grade and without much rain. Even the roads were starting to dry. Once in Embrach, bike path signs for Kloten showed up and we followed that over a hill and found ourselves descending at speed into Kloten, where GPS units and Phil's memory led us easily back to the hotel. We checked in, got our bike cases out, and started taking apart the bikes for stowing. The skies were blue when we checked in but as we started wrenching on our bikes rain came down from the sky in sheets of water and thunder shook the skies around us. We had clearly ended the tour right at the nick of time.

From Tour of the Alps 2011

It took us about 45 minutes to pack the bikes, after which we cleaned up, feeling happy about not having to do laundry for a change. Our freshly laundered clothing had arrived safely from St. Moritz, as had our Amazon.de order for maps. We ate a late supermarket lunch, then started shopping for chocolate. Phil had never really spent much time in downtown Zurich, and Cynthia had wanted us to bring back some Lindt Summer Edition chocolate, so we caught a train downtown with a day pass. We took a quick break at the Sprungli cafe downtown for some chocolate cake.

From Tour of the Alps 2011

I was starting to despair at finding summer edition chocolate when I finally found it in the basement of the City Coop near the Sprungli store. Phil and I each bought about $100 worth of chocolate. We then had dinner near the train station and headed back to Hotel Flyaway just in time to see the Double Rainbow.

From Tour of the Alps 2011

We had one more day in Zurich, but our tour was over.
Previous
Next

Day 29: Radolfzell to Neuhausen

We woke up to pretty clear skies and beautiful weather, and so cooked our Weisswurst and ate them before heading over to the train station to see Alan. To our surprise the forecast was pretty grim, so we opted to take the train over to Schaffhausen. Alan had told me the night before that Scahffhausen was the only Swiss town that got bombed by the allies during World War 2 because the allies thought it was German!

From Tour of the Alps 2011

We got on the train and had a fairly long train ride, and watched gloomily as the weather got more and more overcast as we approached the Bodensee. Finally, I suffered from a fit of impatience and we got off the train at Radolfzell to start riding towards Schaffhausen rather than take the train all the way there. It was drizzling as we got off the train but I figured that it wouldn't be too bad.

From Tour of the Alps 2011

Indeed as we wound around the final parts of the Bodensee the rain never got so bad as to restrict our visibility. The bike path provided ample reminders that Germany was a cycling country, with a bike repair station mounted right past the town of Moos. (Yes, we'd visited two towns named Moos and Wangen on this trip)

From Tour of the Alps 2011

At the town of Horn, we saw a fruit stand and stopped to buy and eat some fruit. The vendor turned out to be from New York. He spend every summer in this part of the country helping out his friend, and said that the weather was unusually wet this year. It was unusually wet last year as well, so I was starting to think this was pretty normal. He told us to stay on this side of the river and that Stein am Rhein was a pretty town and worth visiting.

From Tour of the Alps 2011

Indeed when we got to Stein Am Rhein, we found a cute town with a walkable central district with what were obviously some nice old houses with painted facades. It was a little too early to stop, though, so we pressed on, as Schaffhausen was literally right down the river.

From Tour of the Alps 2011

At Schaffhausen, it took us some time to find the tourist information center, but we then discovered first that the falls were at Neuhausen and not Schaffhausen, and as a bonus, the cheap lodging was at Neuhausen. With help from the lady at the information center, we booked the cheapest hotel at Neuhausen, and then proceeded to ride along the #2 bike route, the Rhine route towards Neuhausen where we found a non-descript hotel that nonetheless featured internet access at the ground floor.

From Tour of the Alps 2011

The hotel had a transparent shower, but fortunately, in addition to having the shower in the room, there were also showers on the same floor, so we took showers simultaneously so as not to have to deal with taking showers with other people in the same room potentially staring at us.

From Tour of the Alps 2011

Of course, as soon as we showered the sun came out, which meant that we should visit the falls. It was a mere 15 minutes walk from our hotel to the Falls, and on the way we went to the supermarket to pick up snacks and drinks.

From Tour of the Alps 2011

The falls were billed as the largest waterfall in Europe. It's not very big compared to say, the Niagara or Victoria falls, but it was charming in a very European style, with no less than 3 castle-like buildings lending atmosphere to the natural wonder. We spent time exploring the falls from several different angles and shooting pictures before our hunger compelled us to seek out dinner and we returned to our hotel.

From Tour of the Alps 2011

Once at the hotel, I pulled out our map and said, "Hey wait a minute, we're only 35km from Zurich, if that!" We looked at our options and decided that we would see what the weather forecast looked like the next day: if it was good, we could keep riding and explore more of the area but if it sucked we would just ride to our hotel in Zurich and spend an extra day in Zurich.
Previous
Next

Startup Engineering Management Pre-Orders

I am now in the final stages of proofing the Startup Engineering Management and pre-orders can now begin. For a limited time (basically while I'm getting the final proof copy), I am providing pre-order copies at $22 each. This period will last until I get the final proof from CreateSpace and order the initial print run. (The reason I can offer this discount is that the more copies I order, the cheaper each copy will be)

Furthermore, so you aren't stuck waiting in case shipping is slow, this pre-order comes with an electronic copy as well, so you can start reading right away!

So if you want a copy, visit the above link and buy away!

Day 28: Rest Day in Munich

We woke up in the morning to a light drizzle that would wax and wane all day, leaving us glad that we had taken the day off. I ran downstairs to buy some senf (sweet mustard) as well as bread for the Weiss Wurst, made some, and then Phil and I went downtown to first get an umbrella and then chat with Alan about dinner arrangements. He seemed happy to meet with Googlers, so we set a time for 6:00pm and went back downtown to use the ATM, browse maps in the bookstore (Phil found an Austrian map to his liking, indicating that perhaps he might return to Austria some day for some more exploration), and then visited Google for lunch.

From Tour of the Alps 2011

After lunch, we bought more Weiss wurst and then headed back to the apartment where Phil slept and read while I watched movies on my Nexus One, which had become my only source of entertainment after my Kindle had died.

Dinner with Alan, Frank, and Daniel was great. Alan explained to us all the construction that was happening in front of the Google office in Munich near Marienplatz. The train line through downtown was the busiest in all of Europe, with a train passing through every 2 minutes, bottle-necking the entire system. The construction was intended to alleviate that by not just building multiple lines, but also enabling Munich's East train station to further allow more traffic. The result should be complete in about 5 years or so. Discussion also revolved around the politics of the train station. The big news, however, was that the French TGV system, which was famously unfriendly to bike carriage, would finally run a line from Lyons to Frankfurt. However, as a condition of being allowed to run on German tracks, the German train system had negotiated with the TGV to have a bike car! As a result, this will be the only TGV/long distance train run by the French system to allow bike carriage. This train will start running in 6 months, and you heard it here first.

From Tour of the Alps 2011

Dinner passed very quickly, and at the end when Alan heard about where we were planning to go, he suggested that we went to Schaffhausen, both for less riding in the rain, as well as to visit the biggest falls in Europe. He told us to show up at 9:00am the next day at the Deutsche Bahn counter where he'd look up the weather for us and provide us with suggested routes.

We went back to the apartment, did laundry using the laundry machine and dryer (what a luxury), cleaned up the place, and went to sleep hoping for better weather the next day.

Previous
Next