Firefox bookmarks sync is much better than Chrome bookmarks sync. Firefox stored your bookmarks locally and updated them periodically from the cloud. Chrome appears to have to download everything when I start the browser. I get a blank bookmarks bar for a few seconds when the internet is slow and I open Chrome. This is one place where Firefox got the design right and Chrome has it wrong.

Push to production as soon as the (many) automated tests that you have pass. This means you should have comprehensive unit tests and tests that run in the browser, probably written in Selenium. You'll also want to script your release so that you can do it with the push of a button. Once the tests pass, and the mechanics of a release are trivial, there is little reason to hold up a release.

I worked for a top 500 website (East coast) for 7 years that did weekly releases. Since I left, they decided that wasn't fast enough and now release multiple times per week. I'm now self-employed on my own website and release within an hour of finishing development of a feature.

I started my development career writing firmware for laser printers. When you are shipping code on a physical product, the cost of bugs can be quite high. Especially when it leads to returns or recalls because customers are not satisfied. Our release cycles there were 6 months+. Quite appropriately, IMO.

On the web, the cost of bugs is much lower. In most cases it is the only cost of another release. Sometimes it could cost more because of downtime, but good automated test coverage mitigates that risk pretty well (especially if there is load testing involved). The worst case would be data-corruption, but I've never actually seen that in practice from a release, that has only been related to hardware failure or accidents in my experience.

Facebook has a real name policy as well. It hasn't hindered their growth. The problem is that Google+ has a real name policy, but doesn't require mutual friendship. This leads to a duplicate one way friendship problem.

Here is the use case: you want to add a friend who isn't on the network but you have their email address.
Facebook: You add the user by email. It goes to "friendship requested" status.
Google: You add the user by email. That email address is added to your circles
Then later, the user signs up for the social network, but not using the email address you supplied then friends you.
Facebook: You are friends!
Google: You are friends, plus you have a zombie email address friend in your circles. FAIL!

That and Google+ is full of bugs. For example you open a Google+ account at your own email address. Then you sign up for gmail. This changes the email address of your Google account to your new gmail address with NO WAY TO CHANGE IT BACK. The people in your circles are associated with your old email address. Google has DELETED all the friends from your circles. You then have to re-add all of them.

The IT department here used on of those "perpetual motion" drinking birds to test the video conference system. A week before the big meeting, they set up the link between our Boston office and our London office, put a drinking bird in front of the camera, and made sure that the connection remained stable enough that it wasn't going to drop during the three hours that we really needed it.

I always get jealous of IT folks when I see that they get to work with racks of equipment. It seems to me like it is building with Lego blocks for a living.

In addition to software installation and security, our IT folks plan out the hardware with the power and cooling requirements. I would have been fascinated by this stuff as a kid (and I still am).