Larry Osterman - What's the secret to succeeding at one company for 20 years?

Charles Torre, one of the developers who works on Channel 9's code, sat down with Jason Zander, Product Unit Manager of the .NET Common Language Runtime team. Here's the first part of that interview.
"Our team is a cross between compiler geeks and kernel geeks," Zander says in response to "What is the magic of the CLR?"
"We do the rocket science so you don't have to."
There's a lot of backup material on my blog.
There is a link to the Headtrax report and more discussion there. There is also
conceptual information on Ngen here as well.
Two pieces of trivia:
1. The white cup on my desk says:
Cup<T>
a clever idea that Anthony Moore, BCL dev lead, came up with for our Generics release.
2. On the left speaker is the "Checkin Cartman". During V1 we didn't have great checkin automation (the system rocks now). After a long tree freeze, we'd bring the tree back up for checkins by serializing per dev lead. Only the dev lead with the Cartman
could check in.
JasonZ wrote:1. The white cup on my desk says:
Cup<T>
a clever idea that Anthony Moore, BCL dev lead, came up with for our Generics release.
Comment removed at user's request.
You are correct compliation is done only on first load, and then only for the methods you actually call. Even so, the time it takes is demonstrably longer than simply paging the existing code in from disk. Ideally, pages are also hot and sharable withother processes. We get our best startup perf through ngen with tuned scenarios (locality of methods). I have a lot of background material on JIT vs ngen and paging on my blog.dudenumber4 wrote:Jason spoke about slow startup times due to JIT compilation and how this is a big target for optimization.. I thought this compilation was done only the first time a new assembly was loaded...? It seems to me to be a negligible issue.