I like this because it breaks binary, false dichotomies that developers usually put themselves in. We can understand why we do this - and its because things are

I like this because it breaks binary, false dichotomies that developers usually put themselves in. We can understand why we do this - and its because things are usually right or wrong, one or zero. We usually end up getting it right in the end and thus the "geekgo" (geek-ego). The tone of this article is great - yes the app store process probably isn't the greatest but it serves its purpose and what can we do to change it beyond opening it up completely to make 'everyone' happy? Maybe in the future a developer will have to prove themselves worthy of being above the slow, error prone approval process by demonstrating a history of thought through code drops and minimal bugs. Maybe the current process is suppose to give developers an incentive to get it as close to "right" as they can the first time.