I know where the employees who work for me live. I know what car they drive. I know where they like to go to lunch. I have their social security number and a copy of their driver's license.

I also know a guy named Tony. Tony likes to break things. And ever since some pencil-neck computer nerd posted pictures of Tony's girlfriend on-line, Tony really likes to break computer nerds.

With Google, these things are much less transparent.

Any time you hear a project manager say "God Willing" about a deliverable or date you know they are flat out lying.

This is exactly why Apple doesn't want third-party UI systems on the iPad. They make their own business decision to improve their UI (something Google has needed for some time and something Google needs in order to survive against the likes of Bing) and now they are getting bad press because some lazy programmer can't figure out how to scrape their search results.

Intermediation is not a right. Businesses should have the right to engage with their customers without third-parties trying to intervene.

Actually, when he uses "proprietary" he means what he says: controlled by a private entity.

Jobs makes the point that Apple has plenty of proprietary technologies as well. However, HTML5, CSS and JavaScript are not proprietary. Even Adobe themselves are a part of the HTML5 spec process. You can join in that process today by either getting involved in the standards process or by writing code (as Apple has done) to support those standards. In fact, not only has Apple been a part of supporting those standards, they've also made their code open source and it is now being used by a wide range of their competitors in their competitors devices.

Go back and watch the iAd demo. Those ads were all created in HTML5, JavaScript, CSS and h.264 video. Compare those ads to most apps in the app store and then ask yourself why so many of those app developers didn't go the HTML5-route in writing their code considering that their Apps would then be cross-platform enabled (since Android uses WebKit as well).

The only reason to build a device-specific App is to take advantage of device-specific features. If you're building something akin to what is being delivered in the iAd demos, why are you bothering?

The iPhone supported sending pictures taken on the phone using the built-in email client from the very beginning. The best part: this feature was basically free (you'd already paid for the data service regardless).

By contrast, MMS messages require an additional charge (either an additional data plan or a per-message fee).

The only reason Apple ever decided to support MMS was because US-based customers wanted this feature to send pics to non-email capable phone users.

The iPhone also has no serial port sticking off of it. That's how it goes with old, outdated technology.

Does the company have an existing dress code? Do the IT guys follow that dress code well?

Let's be honest: IT guys have a reputation for being a bit sloppy. If that's the case here, perhaps the right approach would be for the team to do a better job of looking professional.

But if the team is already meeting the same expectations as the other employees, this just sounds like a giant waste of time. Money, energy and resources wasted on this would probably be better spent on something worthwhile that would actually have an impact on the team's ability to provide quality service.

Yes. Kinda like IBM does.

Oh no you diint!

What's even crazy is the FISH.

Get this: the fish breathe the water, they poop AND pee in the water, they drink the water and they eat other things that also live in the water.

I mean, they basically live their entire lives in the water they crap in.

Yeast are like that, too.

Anyhow, I'm gonna go grab me a tall, frosty mug of yeast shit infested water.... I mean beer...

Ahhh... the birth of a meme...

You're probably a bot.