Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
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.
"25 November 2006, we've got the letter from Michael Jones, the Chief Technologist of Google Earth, Google Maps, and Google Local search, requesting us to cease reverse engineering and improper usage of licensed data that Google Earth use. We understand and respect Google's position on the case, so we've removed all downloads from this page and we ask everybody who have ever downloaded gaia 0.1.0 and prior versions to delete all files concerned with the project, which include source code, binary files and image cache (~/.gaia)." Is Google starting to "do evil"?"
From the article:
There's everything from MP3 player project kits to Linux based GSM phones.There are hundreds of gift guides this holiday season filled with junk you can buy — but a lot of the time you actually don't own it, you can't improve upon it, you can't share it or make it better, you certainly can't post the plans, schematics and source code either. We want to change that, we've put together our picks of interesting open source hardware projects, open source software, services and things that have the Maker-spirit of open source.
It begs the question: what are you getting your favorite alpha geek this year?"