Tomek_Kopczuk

Thanks for the s3cmd suggestion, we'll be sure to check it out before next weeks post.

I predict it will be adopted even quicker than the 4.x branch, due to new notifications. Much sought after feature. Few months and 4.x market share will probably be close to 3G market share.

It is a very good question indeed. And the answer is - yes, I do think so (actually I did 1 year ago, because now the 3.x market share is close to nil). Many 3G owners do wonders to downgrade back to 3.x for performance reasons. And they do spend money.

Consider European markets where costs to upgrade iPhone 3G to 3GS/4G are much more than $200.

According to Bump's statistics from Jan 2011, 90% of all iOS devices run iOS 4.x. We decided to target 3.1.3, because while using 4.0 features would make development a bit quicker, we calculated that additional 10% (it was a bit more back then in favor of 3.1.3) is still worth it.

http://www.quora.com/What-proportion-of-all-iPhone-owners-us...

Party, mate!

We had our app pirated a few weeks ago, it didn't have any impact on the sales. People who pirate your app wouldn't buy it anyway I imagine. Unless it was really well-known and great - but then there's no chance of it not being pirated.

You can verify if the device is jailbroken, but as @wccrawford said couple of comments below - they might have paid for it. And I know many people using jailbroken devices and not pirating one thing.

Party! Your app was deemed worth pirating.

I really recommend just reading the Django docs: https://docs.djangoproject.com/en/1.3/

They are truly magnificent.

Great post.

But I still don't think Vagrant is that big of a help. I agree that compiling stuff like PIL on OSX can be a bit of a bother, but on production machines it's no bother at all.

And developers usually have to do it once, as, at least in our company, they do not change the projects they work on that often, but rather do them from start to the finish (we find it more productive this way). PIP requirements file with proper package versions is a must of course (Fabric deployment). As is staging server, but speaking from the experience - it's just a precaution, it works well.

Cheers for a part about Django Admin. I think it's the single most annoying, hack-needing piece of Django (as Django is great itself, we should expect perfection).

We are starting our own series of Django tips, mainly related to deployment, performance and scaling - at least one tip weekly. But thanks to you I decided that first we'll write about things we use to make Django admin work with you not against you - http://www.askthepony.com/blog/.

Did anyone really expect them NOT to sell this data for ad purposes?

Services like Google, Myspace and facebook are free. Don't kid yourself, they are doing this for money. If you pay - demand privacy. If it's free - come on, you did put all the personal data voluntarily, didn't you?

All they use is statistical data. Be fair - no one really cares about your individual private data, unless you're rich and/or famous. But then you will be much more cautious about sharing personal data on the web. You will, won't you?

Don't underestimate the biggest advantage of going to college - people you will meet.

Other than that - I agree. If you seek knowledge - just pull your finger out. College won't do it for you.

While it seems logical, it's not completely true.

If your great game gets lost down the charts before it's seen, then your success relies on people finding it using App Store search and your keywords. From my experience nobody does this, except for Utilities.

Having a really good app helps it stay on the top, but not necessarily get to the top at all. We've seen pretty poor games get to the top (and usually falling down quickly) and great apps never making the top (due to ie. poor shots or description).

It's not that simple.