Re: Apple's Development Process?

Let me help you with that:

http://sellsbrothers.com/posts?format=atom10

: )


On Jan 29, 2012, at 9:18 PM, "Mike Frith" <[email protected]<mailto:[email protected]>> wrote:


True. We just didn’t get the email that you were leaving MS. :)

From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Sells
Sent: Sunday, January 29, 2012 9:02 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [OT] Apple's Development Process?


It's not like I'm not still here. : )
________________________________
From: Mike Frith
Sent: 1/29/2012 8:38 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [OT] Apple's Development Process?

Telerik. From Sellsbrothers.com<http://Sellsbrothers.com>

“You've reached the internet home of Chris Sells, Developer Tools at Telerik.”

From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Ying Jin
Sent: Sunday, January 29, 2012 5:15 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [OT] Apple's Development Process?


Seriously, Chris left MS? Where is he working now?

________________________________
From: Mike <[email protected]<mailto:[email protected]>>
To: [email protected]<mailto:[email protected]>
Sent: Sunday, January 29, 2012 6:42 PM
Subject: [OT] Apple's Development Process?


Hi,

Does anyone know any specifics about Apple's development process?  How agile they are, what CM do they use, what are their documentation practices, etc.  I recently read a great little book, "Inside Apple: How America's Most Admired--and Secretive--Company Really Works", but it left me with more questions than answers.  Googling did not yield anything worthile.

I'd also be interesting in a non-BS answer as to why so many important Microsoft employees have left in the past few months, even the originator of this list, Chris Sells!  It seems as though a dark cloud has settled over Redmond, but I can't put my finger on what it is.

Thanks,
Mike