Ditto with Google off-line maps. 2 months is all you get, then your maps disappear from your phone. Really sucks when you're in the boonies for a couple of months and your map disappears.

Do you *really* think that's air you're breathing?

Code reviews are worth it, you just need to figure out how to do them so they aren't a pain and are useful. Keep in mind that pair programming is continuous code review, and is a good thing if at least one of the pair is a senior developer. The formal, get in a room, and review all the code since X is a waste of time. My team is fairly small, I have two scrum teams of 5 developers each. For code review, we have version control set up to mail all commit summaries to everyone on the team. One of the duties of the scrum master is to review all commit summaries from both teams, and bring up any problems with the team member. This is generally just a forward of the commit summary to the appropriate developer with comments in the email, and cc to the team. I found this works extremely well and does not interrupt the work flow at all.

I happen to have access to an Omniture account, so I checked their numbers. Omniture says that 100% of the people going to my company's website have Flash installed, and Omniture also says that the internet average is 87.4%. While Adobe's sample size may be large enough to be statistically valid, I think Omniture's sample size is much larger, and therefore, much more accurate.