adamxentcom adam rifkin rohit wondering microsofts definition chief software architect consequently microsoft thinks roadmap go mr ballmer mr gillmor mr fork architecture war love em hate em least microsoft understands chief sa billg oversees product strategy two things road map one piece paper tells everyone records bunch bottomup plans something impose broadly vision top going try get everything shared thats path getting everything stopped time trying take top four five things trying longhorn wave yukon wave net wave really enough time crosscutting discussions make happen bill gates dedicated fulltime chief software architect also happens chairman company spends time chief software architect body meets every month sltt senior leadership technical team basically top people involved productcreating strategy present discuss issues bill driving process waves instance ask crosscutting scenarios want get right product groups together bring things front sltt people talk takes good manager people talk good coach getting people like large organization things important certain level important thing people make better give framework work harmony people company bills perspective framework technical road map sltt process scenarios perspective pl profit loss structure multiple businesses given work giving people framework gets make whole bigger sum parts mean better offerings httpwwwinfoworldcomarticlesplxml020722020722plballmerxml ballmer charge july 18 2002 101 pm pt one knows better microsoft ceo steve ballmer net platform evolves success microsoft depends well company coordinates tool server client strategies well communicates vision interview infoworld test center director steve gillmor infoworld editor large ed scannell microsoft fusion 2002 ballmer discussed progress net changes companys approach product development microsofts efforts simplify product licensing inspire trust customers partners last time talked two years ago beginning net era net evolution let start talking think xml revolution first talk net believe industry collectively decided last three four years world going replatformed xml key foundation like anyone ever got together decide like magnetic north clearly indicated everyone rallying around concept think degree xml pervasive might still underestimated lot partners even conference see btob big companies really way software general designed way security work management everything changed answer direct question two years ago might said jury still whether xml going happen questioning going legitimate competitor java world decided embrace xml basis next generation technology lot benefits come could something xml sure could wasnt specific technical implementation merely fact comes internet standards deeper semantic abilities interoperability connection context net ill say couple things 1 would say momentum market customers using net product line like merrill lynch credit suisse marks spencer citibank variety others people things real feel like degree front ways smaller ways larger smaller sense everyone talking xml talk even sun bigger execution sense weve delivered delivered first batch products really built xml core visual studio net biztalk server getting traction feel good execution relative everyone else say people arent reasonable bolton xml support stuff heavy lifting convince customers partners follow along set standard adoption upgrading next generation present picture behaving consistently within framework focusing customer issues customer satisfaction trustworthy computing articulated things would done differently 2020 hindsight would increased focus security deployment lot security problems actually deployment problems fix sometimes cant get tools hands deploy fixes fast enough licensing know would given time better ways plan around kinds changes made still going get smart full ramifications expect changes made july 31 licensing 60 lot pushback nothing happen july 31 continue learn time need earn customers trust earn business think many people pushing back really dont even know new terms isnt fault educating yes fault meet plenty customers whose companies already licenses saying think theres problem dont deny problems sure issues work time july 31 going see real issues talking customer show saying thought would problem told completed deal company universally licensed total costs company lower said oh really well go july 31 lot customers signed licenses sure going find issues bigger concerns today probably larger accounts may issues need address among smallersize companies net initiative change way inhouse client server developers work together trying health net health company sanity people work quality products produce orchestrated berroad map going two things road map one piece paper tells everyone records bunch bottomup plans something impose broadly vision top going try get everything shared thats path getting everything stopped time trying take top four five things trying longhorn wave yukon wave net wave really enough time crosscutting discussions make happen bill gates dedicated fulltime chief software architect also happens chairman company spends time chief software architect body meets every month sltt senior leadership technical team basically top people involved productcreating strategy present discuss issues bill driving process waves instance ask crosscutting scenarios want get right product groups together bring things front sltt people talk takes good manager people talk good coach getting people like large organization things important certain level important thing people make better give framework work harmony people company bills perspective framework technical road map sltt process scenarios perspective pl profit loss structure multiple businesses given work giving people framework gets make whole bigger sum parts mean better offerings seems scenarios construct really working evolution solutions approach would say pretty direct extrapolation solutions stuff think getting little experience think use word scenarios often solutions less solution sounds like fixed thing end day things customizable programmable people make solution want still scenarios software deployment look like well scenario involves windows office applications working hard make sure whole bigger sum parts thats say people always comfortable cant even say perfectly lot better think would big step forward customers approach cut technology civil wars microsoft past involving going gain control project seems democratic approach development would use word democracy describe people come together ultimately make decisions voting process agenda think important get lot input decided people dont get vote feet try make quantum leap terms ability improve pulling together pieces customers want us simplifying concepts unifying customers dont say want us go ahhh get makes sense dont want go six meetings people say workflow strategy biztalk whats office workflow strategy synchronization ways better email outlook file folders web pages get sort synchronization sometimes get highlevel road map work build something dont today talking unifying storage best way get stuff work get work one way keep tuning one set parameters instead thousand flowers blooming fusion keynote today talked competitors usual suspects one didnt mention competing last generation technology always given stuff doesnt wear break question whether breaks ballmer grins doesnt break like machinery get anyone something new something interesting innovative people think ok upgrades try sell new product decided users like us level systems integration dont get involved take sharepoint team services put office could sold team services separate product could introduced new sku stock keeping unit could decided work level old office new version office could realtime communications tend like put things together integrate release batches1202 upgrades form introducing new innovation matter stuff wear convince people idea better powerful older idea two aspects one aspect given product upgrade release make sense convince nyear period time enough innovation want licensed innovation part whole licensing discussion moved new licensing two reasons would say 1 wanted simplify licensing look back year guarantee simpler nothing simpler transition learning new familiar old think people eventually realize simpler licensing got pretty complicated years people came understand issue timing delivering innovation dont want lot rough questions customers new ideas like ok put upgrade one stream stuff best customers access terms contract think long run better chance satisfying latter hitting six different upgrades fan letting customer decide ok want piece piece licensed two things sought gets back trust issue frontload thats big lumpy upgrade backload vision net 2003 servers long gap middle sell untrusting audience truth need better things big lumpy like new file system like sort small user feature change file system storage backup probaby things going change probably shell ought changethe applications lot things going change call lumpy put four new features powerpoint sure would look lumpy users think build trust model going deliver time come overnight people see things innovation lumpy comes evenly steadily people develop confidence faith like aspects model time support needs become intimately involved story know dont know exactly means yet whole notion software service licensing business discussion software get rearchitected world internet mean many software products fundamentally different internet many probably antivirus guys keep best always feeding new virus support asked audience fusion many use windows update thats small piece software big thats consumer market weve got get really purr corporate market lack broadband buildout adoption seems holding ability users take advantage new services youre talking bill gates invested comcast cable triggered baby bells get board dsl deal issue 1 thing make software compelling people start saying well course going get broadband 80211 one compelling features yes hotel sun valley utah week wired turned pc xp tells wireless network available connect something called mountaineer well dont know vpn microsoft worked dont know whose broadband used didnt see bills room called said hey come room soon everyone connecting internet room support modalities whether gprs general packet radio service 80211 make easy provision software perspective things go dsl cable modems software want broadband link many things say really care performance downloading powerpoint files want broadband things speed otherwise cant without speed going put lot pressure broadband community thats weird answer normal answer yeah isnt awful enough broadband prices charge agree look happened japan recently big drop 25 month dsl vroom gone almost dsl connections year ago 15 million 18 million subscribers make happen country think beyond us enough interest consumers looking intensely broadband whether todays prices tomorrows prices going shake marketplace think marketplace good job make something obvious consumers want happen live neigborhood broadband network dsl cable modems well neighbor teledesic chairman coceo craig mccaw wireless network think piggyback ballmer laughs yes broadband bottleneck also think look oursleves software industry say arent bottleneck built software makes broadband musthave microsoft ceo weighs ballmer addresses number key issues customers partners security trust things would done differently coordinating product groups working hard make sure whole bigger sum parts product licensing still going get smart full ramifications adamxentcom long sig alert believe quite possible productively apply supposedly incompatible approaches rest soap together ill sketch prescriptive form note proscriptive expected local adaptations provided 1 start modeling persistent resources wish expose persistent resources referring entities typical life expectancy days greater ensure instance unique url possible assign meaningful names resources 2 whenever possible provide default xml representation representation unlike traditional object oriented programming languages unique getter per property typically single representation entire instance representations often contain xlinks aka pointers references instances 3 add high level methods take care composite create update delete operations key aspect design messages operations need self contained sender receiver able make absolute minimum assumptions others state multiple requests required implement single logical operation requests provide appearance executed atomically 4 query operations deserve special consideration general purpose xml syntax provided every case addition reasonable expectation exists query parameters relatively short size require significant encoding http get parameters encoded query string also provided implications following table emphasizes unified approach differs pure albeit hypothetical different positions described 1 resource post operations explicitly possibility modifying multiple resources put delete operations rarely used ever gets may contain query arguments 2 get gets must never used operations observably change state recipient post used instead 3 message presume urls static instead presume identify resource particular recognize urls dynamically generated expect urls soap resources responses use soap response mep pure retrieval operations 4 procedure treat url implicit first parameter allow urls dynamically generated returned structures use http get retrieval operations conclusions looking future application level internetworking protocols emerge today likely application level intranetworking protocols next decade rest soap contain features others lack significantly rest soap xlink key bit functionality soap applications miss today ability link together resources soap 12 makes significant progress addressing hopefully wsdl 12 complete important work soap rest stored procedures looking large scale systems cope updates provides key insights productive areas future research respect rest finally bears repeating service using http get doesnt mean rest encoding parameters url probably making rpc request service retrieving representation resource worth reading roy fieldings thoughts subject exception rule routinely condoned within rest crowd queries sam ruby httpradioweblogscom0101679stories20020720restsoaphtml httpxentcommailmanlistinfofork mon 22 jul 2002 215144 0700 pdt infoworld ballmer describes chief software architect