I'm looking for a good Django tutorial that includes examples of developing with BDD and TDD. The way I learned Rails included RSpec and Cucumber, and that made a huge difference.

Try http://www.tdd-django-tutorial.com/

The TDD Django Tutorial is both a good example of Django TDD and a good introduction to using Selenium for integration/functional tests. It was my first introduction to both.

I agree that it's a niche market. I remember not getting an iPhone forever ago because I didn't want to switch to AT&T. Because I am on T-Mobile, this phone looks amazing.

Are you suggesting those articles / models contradict each other? They look pretty similar - one is just bumpier than the other.

They do contradict one another. In one Paul lays out a process, actually the process (which gels with my experience) which involves a lot of pain and flat to down time, followed, in the very long run, by the eventual ramp and growth phase.

Now he suggests you need to have 5% growth per week or your startup is doing it wrong.

I think that the first view is that of a founder, whereas the second view is that of a VC.

Reason why Google is no Microsoft monopoly: no copyright enforcement.

Microsoft depended on the government's ability to help enforce copyright protection, thus the government sponsored its monopoly. If Google went off suing all its users then I bet the government would care more.

Doesn't jailbreaking void your warranty?

Well, if the phone still works and you need something replaced under warranty, you can always factory reset it. If the phone DOESNT work, then there is no way for them to tell that it's jailbroken in the store...

Probably just friends with her because she's a girl.

Obviously, you didn't look at all the designs Apple claims are copies. Unless you believe Apple invented the mobile phone, I don't think you can just claim that this isn't preventing innovation.

So, who's next? Gestures seems pretty common on most mobile devices, and I'm guessing this opens the door for Apple to be able to sue them all, right?

Appeals are next.

They don't need to. This sent a big warning to all the Android OEMs not to copy the iPhone.

And that is what Apple wanted. Not money.

I think we can all agree that Apple's intention was to stifle competition, not to get money. The problem is that Android already have to go out of their way to "innovate around" obvious design decisions. This makes things even harder. There is a good chance things will go the other way too, and it will make it harder for Apple to keep up with Android as they introduce new features.

I can't see this being good for anyone except Apple shareholders, and in the long run I'm not sure it will even be good for them.

No. Apple's intention was to put as much of a gap between what the iPhone looks and feels like and what Android looks and feels like.

Whether that stifles competition is a separate issue.

You know Apple's intentions pretty well! Are you a C-level executive there? Or are you just speculating the exact same as he is?

I'm still confused how employers could ever justify doing this. Do they ever explain what they're looking for?