What he means, is don't hire mobile engineers that have worked at big telco provider (samsung,motorola, or carriers). It is well known that these companies just don't have good talent.
I'd rather work with a good generalist, than a crappy mobile developer. But, a good mobile developer will run circles around a generalist.
"b. Don’t hire “mobile” Product Managers (PMs)"
Again, same thing. He equals 'mobile pm' to somebody that has worked in crappy telco related companies.
That's not true. There have been plenty of mobile companies that are not telco related. Even before iPhone came to change the landscape, there were plenty of companies that were both mobile and consumer focused.
..
"For example, on the early Google mobile team we had a PhD student from Yale with no industry experience, an expert on enterprise Java from BEA, and a research scientist at Google. These people helped form a formidable core for mobile engineering at Google."
Ah, this explains why the Android api seems like something that came from the desktop. It has everything thrown into it, even the kitchen sink. Comparing to the iPhone sdk, it is clumsy. Also, this probably explains a lot of the usability problems Android has in general.
The sad fact is that developing for the android is twice as expensive, and produces less good looking application than the iPhone.
Perhaps this guy should have hired mobile engineers?
What he means, is don't hire mobile engineers that have worked at big telco provider (samsung,motorola, or carriers). It is well known that these companies just don't have good talent.
If your main reason for not hiring someone is "They worked for Nokia," then I'm not quite sure what to say, besides that it doesn't seem to be a very good reason not to hire someone.
Of course, I've never worked for any of the aforementioned companies. That being said, I know some very smart people who have (and continue to do so). People who I'd be happy to work with, if the chance ever came up at the right time.
1. Dalvik VM manages a lot of stuff that have do by hand on iphone resulting in iphone always costing 1.5 times as much as android.
2. I can point out the crappy iphone apis if you like such as that notification api that freezes iphone devices more than once even for the average user on a daily basis.
Comments
I think it is ok advice:
What he means, is don't hire mobile engineers that have worked at big telco provider (samsung,motorola, or carriers). It is well known that these companies just don't have good talent. I'd rather work with a good generalist, than a crappy mobile developer. But, a good mobile developer will run circles around a generalist.
"b. Don’t hire “mobile” Product Managers (PMs)" Again, same thing. He equals 'mobile pm' to somebody that has worked in crappy telco related companies.
That's not true. There have been plenty of mobile companies that are not telco related. Even before iPhone came to change the landscape, there were plenty of companies that were both mobile and consumer focused.
..
"For example, on the early Google mobile team we had a PhD student from Yale with no industry experience, an expert on enterprise Java from BEA, and a research scientist at Google. These people helped form a formidable core for mobile engineering at Google."
Ah, this explains why the Android api seems like something that came from the desktop. It has everything thrown into it, even the kitchen sink. Comparing to the iPhone sdk, it is clumsy. Also, this probably explains a lot of the usability problems Android has in general.
The sad fact is that developing for the android is twice as expensive, and produces less good looking application than the iPhone.
Perhaps this guy should have hired mobile engineers?
What he means, is don't hire mobile engineers that have worked at big telco provider (samsung,motorola, or carriers). It is well known that these companies just don't have good talent.
If your main reason for not hiring someone is "They worked for Nokia," then I'm not quite sure what to say, besides that it doesn't seem to be a very good reason not to hire someone.
Of course, I've never worked for any of the aforementioned companies. That being said, I know some very smart people who have (and continue to do so). People who I'd be happy to work with, if the chance ever came up at the right time.
ahem,
I have developed both on iphoen and android:
1. Dalvik VM manages a lot of stuff that have do by hand on iphone resulting in iphone always costing 1.5 times as much as android.
2. I can point out the crappy iphone apis if you like such as that notification api that freezes iphone devices more than once even for the average user on a daily basis.