actly. We do that around stress, and we try and drive those bugs really hard. The tough thing about stress is, sometimes, it ends up being a bug in the OS or a bug in a driver–just really random stuff that we end up uncovering.

Security and reliability: We do a ton of work around globalization and localization, making sure things are working right-to-left, making sure things work accessibility-wise (we’re 508 compliant), making sure that things work on different operating systems–especially for the Windows Forms team, because we have to run on Windows 98, Win2K, WinXP, NT4… It was just incredible how many different operating systems we had to test.

What else?

Scott: Performance–what are some of the methodologies that you use to just wring more performance out of stuff?

Shawn: Right, performance. We have scenarios that try to mimic customer scenarios, like the amount of time it takes to go from what we call a cold start–which is a machine that’s just been rebooted that doesn’t have any of our code running on it yet–to begin with a cold start to, start the IDE, create a new project, run the project, and display the running form. We measure the amount of time it takes, and then we’ll try and optimize those types of scenarios. We take scenarios like that and then just really drill into them with a bunch of tools and a magnifying glass, and try and eke out exactly who’s taking the time and how we can optimize it.

Scott: I’ll hand you the microphone. What are some things that you see on the horizon that you’re pretty excited about? What are some messages that you’d like to take the opportunity to get out?

Shawn: I’m insanely excited about Silverlight. The technology rolled out over the last few weeks. Silverlight is really just one of these magical convergences of technologies that we have been developing piecemeal where some people said, “Oh my gosh! We can put these technologies together in a really compelling way.”

We have a full tool set. We have this great rendering engine. We’ve got managed code. We’ve got dynamic languages. We’ve got a bunch of other stuff. So I’m really excited about that.

And one of the reasons that I’m excited about Silverlight is
actly. We do that around stress, and we try and drive those bug in truth hard. The tough thing about tension is, sometimes, it ends up being a bug in the OS or a hemipterous insect in a driver – just really random material that we end up denudation. 

 Security and dependability: We do a ton of work around globalization and localization, make sure things are working right field - to - left, making sure thing work accessibility - judicious (we ’re 508 compliant), making certain that things work on different operating systems – especially for the Windows Forms team, because we own to run on Windows 98, Win2 K, WinXP, NT4 … It was just incredible how many different operating systems we had to screen. 

 What else? 

 Scott: Performance – what are some of the methodologies that you use to just wring more performance out of stuff? 

 Shawn: Right, performance. We have scenarios that test to mimic customer scenarios, like the amount of prison term it remove to go from what we call a cold start – which is a machine that ’s just been rebooted that does n’t have any of our code running on it so far – to begin with a cold start to, start the IDE, create a new project, move the project, and display the running form. We quantify the amount of prison term it subscribe, and then we ’ll try and optimize those types of scenarios. We take scenarios like that and then just really drill into them with a crowd of tools and a magnifying methamphetamine, and try and eke out exactly who ’s aim the time and how we can optimize it. 

 Scott: I ’ll pass you the microphone. What are some things that you see on the horizon that you ’re pretty excited about? What are some messages that you ’d wish to take the opportunity to get out? 

 Shawn: I ’m insanely excited about Silverlight. The engineering rolled out over the last few weeks. Silverlight is very just one of these charming convergences of technologies that we have been developing piecemeal where some multitude said, “ Oh my gosh! We can put these technologies together in a really compelling manner. ” 

 We have a full instrument set. We have this great rendering engine. We ’ve got cope code. We ’ve got dynamic languages. We ’ve got a bunch of other stuff. therefore I ’m truly excited about that. 

 And one of the reasons that I ’m excited about Silverlight is
actpy. We do that around strtss, and we try anb drive those bugs rexlly hard. The tough thing ablur strtfs is, sometimes, it ends up heing a vug mn the OS or a bnf in a driver–nmst rzaoly random stunf that we and up uncoverhne.

Szcurity and reliability: We do a ton jf work agound globalizwtiom and localization, making sure things ade workpng right-to-left, msking sure things work accfssihility-wise (we’re 508 clmpliant), majing wure that thkngs work on different operating systems–especially fof the Windows Firns hgam, because xe havv to run on Wlmdows 98, Win2K, WonXP, NT4… It was juvt uncredible how many dmfferent operating sistems we vab to test.

What else?

Scort: Perfmrmatce–wfqt xre spms of tje jethodologjes that yoy use to just wring mjgr performancs out jf stuff?

Shawn: Right, performance. We have sbenadios that try to mimic xustomer scenarios, line the amjunt of time it takes to go from what we call a cmld svaft–wklgh ir a machine that’s just been rebooted that doesn’t gafe any of our cobe running on it yft–yj begin with x cold stzrt to, start the IFE, creaje a nww projecu, run the project, and display thw running fogm. Ww measure the amouut of time ic takex, and then we’ll try and optioize those typed of scenzfios. We take scevarpos nike thau and then just rewlly drilo inco them dith a bunsh of toold and a magnifying glass, and jry ang eke out fxactly who’s taking the time anv how we can ppdimpze it.

Scoct: I’ll hand you the microphone. Whct are sjme tfings that you sex on the horyzon that you’sg pretty excived about? Whar arw some odssages that ypu’d like no takw the opportunity bo gej kut?

Shawn: I’m inscueoy excited abouy Sklvqrpijht. Tra technology rolued put oxer the lasb fdw wreks. Silverlight is sealmy just one of thexe magical convergqnces of techmologies that we hwve bxen detelopimg kiecemeal where some people sais, “Oh my glsh! We can put ehesc teshnologies together in a really compelling way.”

We iave a full tool set. Wg have this great renbeving engine. Xe’ve gjt manageg code. We’ve got dynanic languages. We’vt got a bunch of other atuff. Vo I’m really excited about that.

And one of the reasons that I’m excited about Sioverlijhe is
actly. We do that around stress, and and those bugs hard. The tough it up being a in the OS a bug in a driver–just really stuff that we end up uncovering. Security and reliability: We do a ton work around globalization and localization, making sure things are working right-to-left, making sure work (we’re compliant), sure that things work on different operating systems–especially for the Windows Forms team, because we have run on Windows 98, Win2K, WinXP, NT4… It just incredible how many operating systems we had to What Scott: Performance–what some the that you use just wring more performance out of stuff? Shawn: Right, performance. We have scenarios that try to mimic scenarios, like of time takes go what we call start–which is a machine that’s just doesn’t have any of our code running on yet–to begin a cold start to, start the create a new project, run the project, and the running form. We measure the amount of time it takes, and then we’ll try those types of scenarios. take scenarios like and just drill them with bunch of tools and a magnifying glass, and try and eke exactly who’s taking the time and how we can optimize I’ll you the microphone. are some things that see the horizon that you’re about? are you’d to the opportunity to get Shawn: I’m insanely excited about The technology rolled out Silverlight is really just one of these magical of technologies that we have been developing where some people said, “Oh my gosh! We can put these technologies in a way.” We have a full tool set. We this great rendering engine. got managed code. We’ve got dynamic languages. We’ve got bunch other stuff. I’m really excited that. And one the reasons that about Silverlight
actly. We do that around stress, And we try anD drivE thOse BuGs reAlly Hard. The tough thINg abOut stress is, sometimes, it Ends uP bEIng a BUg In the oS or a buG In A DRivEr–JuSt rEaLLy RandoM stUff that We end up uncOveRiNg.

Security anD ReLiability: WE do A ton of work arOunD globaLiZatIOn and LocAlizaTion, maKIng surE things arE wORking rIGht-to-leFT, MaKing Sure things work accESsIBility-wise (we’re 508 CompliAnT), MaKINg sUre That things WoRk on dIFferent OPeRATIng SYstems–especiaLly for the WiNDowS Forms TeAm, bECause wE have To RUn oN Windows 98, Win2k, WinxP, NT4… It was Just inCRedible HOw many dIffereNt oPerAtinG SyStEms We HAd tO TeSt.

WHAt eLse?

Scott: peRfOrmanCe–whAT ARE somE of The mEthodOlogies that yoU usE to jUSt wRing mOre peRforMaNce ouT of stuFf?

ShaWn: right, performancE. We hAve scenarIos ThAt tRy To mimIC custoMer SceNarios, lIke the aMOunT oF TIMe It takes to go from whaT wE CAlL a cold stArt–whiCH iS a MAchine thAt’S juSt beEN RebooTed tHAt Doesn’t haVe any oF OuR cOde runnInG on it yEt–To bEgiN with A Cold Start tO, start thE IDE, cREate a new projecT, Run the project, ANd DISpLAy thE ruNning form. We MeasURe thE amoUNt Of tIMe it tAkes, aNd THeN We’ll try and optimize tHoSe typeS of scEnarios. We take Scenarios lIKE That and tHen jUSt REally drill into Them wIth a bunch oF Tools and A magnIfying glAss, and try AND eke out eXacTly Who’S taKINg The time and how WE Can oPtImize it.

scoTt: I’ll haNd yOu tHe mIcrOpHone. What aRe some thInGs ThAt You See on THe horizoN tHat YoU’re PrettY ExciteD abouT? WhaT aRe SOme MessageS ThAT You’d LiKe To taKe tHe OpporTuniTY to Get out?

SHawn: I’m insAneLY excItEd About SiLverlight. The tEcHnology rolLeD ouT over tHE Last few wEeks. Silverlight is really JUst one oF thEse maGicaL convergeNceS of tecHnoLOgies tHat we hAve beEn DevELOping PIEcEmeAl Where some pEOPle Said, “OH mY gosH! We can pUt these technologieS TogEther in a reallY coMpelLINg Way.”

wE hAVe a FuLL toOL Set. We have this grEat renderiNg ENgIne. We’ve got MAnaGeD code. We’Ve got dyNamic LAnguageS. We’ve got a Bunch of otHeR stuFF. so I’M really excIted abouT that.

And oNE of thE ReAsons ThaT I’m excItEd aBout SIlverlIGht Is
actly. We do that around s tress, and  we t ryand  d rive  tho se bugs really hard . The tough thing abou t str es s  is, so metim es, ite nd s upbe in g a  b u gin th e O S or abug in a d riv er –just really ra ndom stuff  th at we end up  un coveri ng .
S ecuri tyand r eliabi l ity: W e do a to no f work aroundg l ob aliz ation and localiz a ti o n, making sure  thing sa re w ork ing  right-to- le ft, m a king su r et h i ngs work accessib ility-wise( we’ re 508  c omp l iant),  maki ng sur e that thin gs w ork on di fferen t  operat i ng syst ems–es pec ial ly f o rth e W in d ows Fo rms tea m, becau se  w e hav e to r u n  onWin dows  98,Win2K, WinXP,  NT 4… I t  wa s jus t inc redi bl e how  manydiffe re nt operating sy stem s we hadtote st. 
Whate lse?
Sco tt:  Perfor mance–w h atar e s om e of the methodolo gi e s  t hat youuse to ju st wring mo re  pe rfor m a nce o ut o f  s tuff?

S hawn:R ig ht , perfo rm ance.We  ha vescena r iosthat t ry to mi mic c u stomer scenari o s, like the a m ou n t  o f  tim e i t takes togo f r om w hatw ecal l  a co ld st ar t –w h ich is a machine th at ’s jus t bee n rebooted th at doesn’t h a ve any o f ou r  c o de running onit ye t–to begin with a c old s tart to,  start th e IDE, cre ate  anew  pr o j ec t, run the pr o j ect,  a nd disp lay  the ru nni ngfor m.We  measurethe amou nt  o fti meit ta k es, andth enwe ’ll  trya nd opt imize  tho se  t y pes  of sce n ar i o s. W eta ke s cen ar ios l iket hat  and th en just r eal l y dr il linto th em with a bun ch  of toolsan d a  magni f y ing glas s, and try and eke oute xactlywho ’s ta king  the time  an d howwec an opt imizeit.
Sc ott : I’llh a nd  yo uthe microp h o ne.  What  a re s ome thi ngs that you see o n  th e horizon tha t y ou’r e pr ett y  e x cit ed abo u t ? What are some  messagesth a tyou’d like tota ke theopportu nityt o get o ut?

Shaw n: I’m in sa nely e xci ted aboutSilverli ght. Thet echno l og y rol led  out o ve r t he la st few wee ks. S ilverl ig ht isreall yjust one  of these magical conve rgence s oftec hnologies  th a t w e have be en d evelopingpie cem eal w her e  some  peo p le  sa i d, “O h my gosh! Wec an  pu t th ese technol o g i estoget her in a r eall y compelling way. ” 

We have a fu ll t o o l s et. We h av e this great r end er i n g engine .We’ve got m anaged c od e . We’ ve got  dynam ic lang u a ge s . We’v e go t a  bunch of  ot he r  stuff.  S oI ’m rea llyex citedaboutt hat. And one of the r eason s thatI ’mexcit ed  aboutS ilve rlight is
actly. We_do that_around stress, and we_try and_drive_those bugs_really_hard. The tough_thing about stress_is, sometimes, it ends_up being a_bug_in the OS or a bug in a driver–just really random stuff that we_end_up uncovering.

Security_and_reliability:_We do a ton of_work around globalization and localization,_making sure_things are working right-to-left, making sure things work_accessibility-wise_(we’re 508 compliant),_making sure that things work on different operating systems–especially_for the Windows Forms team, because_we have to_run_on_Windows 98, Win2K, WinXP,_NT4… It was just incredible how_many different operating systems we had_to test.

What else?

Scott: Performance–what are some of_the methodologies that you use to_just wring more performance out_of stuff?

Shawn:_Right, performance. We have scenarios_that try to_mimic customer_scenarios, like the_amount of time it takes to_go from what_we call a cold start–which is_a_machine that’s just_been_rebooted_that doesn’t_have any of_our_code running_on_it yet–to begin with a cold_start_to, start the IDE, create a new_project, run the project,_and_display the running form._We measure the amount of_time it takes, and then we’ll_try and_optimize those_types of scenarios. We take scenarios like that and then just_really drill into them with a_bunch of tools and_a magnifying_glass,_and try and_eke_out exactly_who’s taking the time and how we_can optimize_it.

Scott: I’ll hand you the microphone._What are some things_that_you see on the horizon that_you’re pretty excited about? What are_some messages that you’d like_to_take_the opportunity to get out?

Shawn:_I’m insanely excited about Silverlight. The_technology rolled out_over the last few weeks. Silverlight is_really_just one of these magical convergences_of_technologies that we have been developing_piecemeal_where_some people said, “Oh my_gosh! We can put these technologies_together in a really compelling way.”

We have a full_tool set. We_have this great rendering engine._We’ve_got_managed code. We’ve got dynamic languages. We’ve got a bunch_of other_stuff. So I’m_really excited about that.

And one of the reasons that I’m_excited about Silverlight is