I feel like to a large extent this is just techcrunch being techcrunch and writing link-bait articles.
My thoughts on this:
1) Just about everyone is "interested in making money" from their apps. I'm not sure how they're filtering the developers in the survey, but I'm willing to bet the amount of effort put in, and the actual methods used to "make money" differ wildly among those developers. Apples to oranges.
2) 5-10k per app per month for a single developer with a full-time job doing this in his spare time is pretty good. For a 300 employees company, not so much. Similarly, millions a month will sustain a large company and make an individual developer extremely wealthy. What are we comparing?
3) I'll go out on a limb here and say that games make more than any other category on the app store. They also tend to require a higher budget and production value: better graphics, sounds, a storyline, etc... Maybe the 100 flashlight / todolist apps competing for the same spots don't make much money but they also cost nothing besides a weekend of work and the $99 / year ADC membership. I also wouldn't be surprised if most of that "1.6%" were game developers. Lumping every app together and trying to get stats out of it doesn't tell us anything about how much the developers are spending to get those apps out.
4) Obligatory plug: Storm8, the company I work for, is recruiting. We're a mobile games developer (on the App Store we tend to be better known as TeamLava) and have been profitable and fully bootstrapped for over 5 years now through rapid growth. We're all very passionate about creating new games and refining our existing ones and have a lot of interesting projects to work on. We're looking for developers interested in learning more about the mobile games industry, no experience required. Email is in my profile if interested :)
I kind of skimmed the post, so maybe I'm missing something, but what exactly is the "architecture" described here? Dynamically-typed languages will allow the passing around of objects of different types as long as they implement the necessary methods. This is a nice property in some cases, but a lot of times I'd prefer to have static-typing and well defined protocols. It seems like that post ignored the more important parts of the discussion.
He doesn't negate your points because there were none to negate. Well, except for that clearly accurate "90-99%" figure you quoted. Your personal crusade is not a rebellion, and no one is trying to cut off "you're" head.
Sure, we all agree that deceptive advertising is deceptive. That's wrong, but not all advertising is bad. I think you'll be surprised to find out that 95% of people (yay, making up numbers is fun!) actually don't mind that google tracks their activity so they can show more relevant ads. I typically don't click on them, but hey, more relevant ads still makes my overall experience better and I really don't care if we get there because some of my search history was (relatively anonymously) logged on some of google's servers.
Also yes, word of mouth leads a lot of people to discover new products, and may be cheaper than traditional advertising in dollar amounts, but it's likely a much greater time investment that may not even pay off in the end. Likewise, patio11 could pay the hobbyist site, and google, and any other "legitimate" advertising platform directly but I think the time commitment to find those valuable platforms, enter into an agreement with them, and deal with all the associated details may not be worth it for him.
In the end, it's about finding a cost-effective way to get your products in front of its audience. That may be "word of mouth" (and I don't want to get into that debate, but product review sites tend to be more misleading, biased and corrupt than a lot of ads), or it may be ads. To each his own, but you don't need to condemn everyone who doesn't share your overly idealistic views.
IANAL, but I'd be surprised if the police was allowed to raid me, launch tear gas through my window and shoot me in the head. Even with a warrant. I'm not worried about this happening, because it doesn't. If it did, I'm sure it would blow up into a huge scandal.
I am worried about government agencies intercepting my traffic / communications because it does happen, it's really hard to find out unless you know what you're looking for, and they don't have a warrant on every American citizen that happens to get caught.
You'd be surprised by how many people won't do that. In my opinion, it's your job as a designer / developer to make sure your product works for as many people as reasonably possible, and not expect users to jump through hoops (no matter how small) to use it.
Non-combattants should be off-limits imo, yes. However war and terrorism are completely different. It's generally accepted that there may be civilian casualties in a war zone, and that is clearly not terrorism (intimidation, maybe).
Unprovoked, unilateral attacks seem to be the more traditional form of terrorism (basically using fear to try and influence behavior), in particular when performed by groups not (officially) affiliated with a specific government.
IANAL and I hate to sound like a fanboy, but can't Apple claim that the 2007 iPod touch is prior art, since it's basically a small black tablet with rounded corners and a single button at the bottom? It looks much more similar to an iPad than the 2008 crunchpad.
It seems that in the very rare cases where a commercial plane goes down spectacularly, the ones that make it alive were flown by formerly non-commercial pilots (military or otherwise), who've flown planes that give them much less assistance and in much more stressful situations and so "doing the right thing" has almost become second nature to them.
The problem with people is that even if you know what you should be doing in theory, when you're put in an extremely stressful situation you're unlikely to be able to come up with a creative solution... and few situations are more stressful than the moment you realize that something completely unexpected is happening, at night, in a thunderstorm, over the ocean, with 200+ lives depending 100% on your actions.
Surely there must be more to it. Clearly all of us who've played a flight simulator know that going up too fast will cause you to lose speed and eventually stall and fall until you regain enough speed to stabilize.
Sadly in this case it sounds like a mix of overconfidence (not avoiding the storm, trusting the plane more than the stall warnings, not waking up the captain until it was too late) and a lack of training for unexpected situations were the major factors in the crash.
I feel that work habits are a very personal thing.
I find that I'm more productive if I work on multiple projects throughout the day instead of dedicating to just one. I don't know if it's because I'm putting artificial deadlines for myself (i.e., I have 3 hours to get this done before I move on to task / project B) or because I stay more engaged and motivated if I'm working on very different things.
On the other hand I know people like Swizec who will feel overwhelmed if they know they have a number of tasks to get done in one day and will procrastinate on all of them.
Always interesting to read about other people's productivity tricks though.
Edit: Also completely disagree about the comparison with professional athletes. Burnout is very real and it will sneak up on you if you don't take some time off to relax here and there, but just working hard will not damage your brain like being a pro-athlete would damage your body.
I was just about to post the same thing. I agree with the underlying thesis that a good shipping product is better than perfect code that never ships, but the author seems to be confusing good code and over-engineering.
Good code does exactly what it needs to, but will be maintainable and won't have to be thrown away when that "fantastic" product ends up getting popular.
I also tend to believe that doing it right doesn't necessarily take much longer. The code I write now is much better than the code I wrote 10 years ago for a number of reasons, but I still get a lot more done, and a lot faster than I did back then.
Many shy people tend to avoid situations where they think they may get rejected. I think the point of the experiment is to show them that they could be happier / better off if they didn't take rejections so personally / weren't afraid of getting rejected.