Linked by Thom Holwerda on Thu 11th Oct 2012 21:41 UTC
Thread beginning with comment 538508
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-07-14
Those two will kill you everytime.
Outsourcing projects is okay, if you understand that the final code you get will have to be heavily modified at the end of the day you are responsible for anything your company ships with your name on it. I've been involved in overseeing outsourced projects a couple of times. Its ranged from complete disaster with no usable code returned to a highly unpolished messy/buggy code base.
One of the things that people keep pointing out with Apple is that they aren't afraid of killing sales of existing successful projects by introducing new, better ones. The classic ipod was pretty much killed by the iphone. Ipad's may be eating into macbook sales. They aren't afraid of letting the better product they make be successful. Mameo, outsourced warts and all was a better future platform for Nokia. If they had moved more resources towards it and just let symbian go, they'd be doing much better right now. So maybe in a sense Elop came in the middle of a turf war between two warring factions and didn't choose sides by going in a completely different path. Perhaps looking to unite the company and avoid similar situations in the future.