A Test for Whether You Support Innovation, would you promote someone who breaks the rules

When I joined Microsoft an executive spoke at new employee orientation.  There are two stories that come to mind.

First story.  The executive had been a long time developer in Excel and had decided he wanted to get his MBA.  He was accepted into Harvard and was ready to resign.  Given he was employee #105 at Microsoft it is expected he would talk to Bill before leaving.  Bill asked him why he wanted to get his Harvard MBA.  His response is he wanted business experience.  Bill responded if you want business experience, I'll give you business experience.  You are now the General Manager of Microsoft Word.  The executive of course didn't go to Harvard and he eventually became a VP of Office.

Second story.  Same executive.  Same employee orientation.  He starts telling a story.  I'll tell it slightly different than he did.  

He was a senior developer on Excel and was working on a new feature.  As part of the feature being complete he wanted to put it on the toolbar.  Here is an image of Mac Excel 2011's tool bar.

NewImage

And a bit of early history of Excel.  I remember this history from the Apple side when I worked there and Excel quickly became the standard spreadsheet program.

Microsoft originally marketed a spreadsheet program called Multiplan in 1982. Multiplan became very popular on CP/M systems, but on MS-DOS systems it lost popularity to Lotus 1-2-3. Microsoft released the first version of Excel for the Macintosh on September 30, 1985, and the first Windows version was 2.05 (to synchronize with the Macintosh version 2.2) in November 1987.[61] Lotus was slow to bring 1-2-3 to Windows and by 1988 Excel had started to outsell 1-2-3 and helped Microsoft achieve the position of leading PC software developer. This accomplishment, dethroning the king of the software world, solidified Microsoft as a valid competitor and showed its future of developing GUI software. Microsoft pushed its advantage with regular new releases, every two years or so.

Back to the feature, the developer wanted to put it on the toolbar, so he met with the program managers and product managers to discuss where to put his feature.  They told him no, his feature would be in pull down menu, not on the tool bar, because the tool bar at the time was reserved for formatting features - font, justification, %/$, etc.  After weeks of trying the developer gave up trying to convince the program/product managers to put his feature on the tool bar.  Late one night, he checks in the code for his feature into the build, and he adds code to put his feature in the tool bar.

The next day the build is released to test teams and development, and there is his new feature on the format tool bar.  The program/project managers were of course upset and told him he must remove the feature from the tool bar.  He refuses.  They get more angry.  He tells them he will remove the feature from the tool bar after they run usability tests with end users.  They still insist he remove the feature.  He stands his ground.  Eventually the program/product managers agree to run usability tests.  And, the results show the new feature is the popular feature on the tool bar.  Know which one it is?

NewImage

Autosum.  The executive/developer is Chris Peters.

BELLEVUE, Wash. -- Chris Peters was vice president of Microsoft's Office division, responsible for 400 software developers and more than $4 billion in annual revenue. Last year, he startled his colleagues by taking a leave of absence to train for a new career-pro bowling.

Now, Mr. Peters spends many afternoons at Sun Villa Bowl, an aging bowling alley tucked between a grocery store and a Mormon temple in this eastside Seattle suburb. On a recent weekday, Mr. Peters, 41 years old, is the only bowler present below what used to be called retirement age. He raises a red ball to his side, steps off, slides and releases. The ball skids down the lane, hooks hard to the left and explodes into the pocket. Strike!

"You can tell when it leaves your hand," he says. "It's so satisfying."

More satisfying, for now, than his old job at Microsoft. Mr. Peters says he realized as he neared his 40th birthday that he had lost his passion for the all-consuming, 16-year career that made him rich but led him to neglect almost everything else, including his health and family.

Now to finish the second story.  Chris did warn the audience that his actions getting Autosum is not something that should be done unless you are sure you are right.  If you are right, you should push for doing the right thing.

This may sound OK.  But, you need to take into account that Chris was Microsoft employee #105 with huge credibility in the company, and so valued Bill would give him running Microsoft Word to keep him from leaving the company to get his Harvard MBA.

What Chris did with putting Autosum was innovative and still one of the most valued features on the Excel Tool Bar. Do you think he would be promoted?

 

Oh I get it the NSA Data Center is a Cloud and Clouds have Lighting (Arc Flashes) - Humor

ABC reports on the NSA data center and has a quote.

"The failures that occurred during testing have been mitigated," Vines said in a statement. "A project of this magnitude requires stringent management, oversight, and testing before the government accepts any building."

I was thinking maybe somewhere buried deep in the huge stack of requirement documents are that the NSA data center is a Cloud environment.  And, someone could interpret the Cloud as we need lightning.  :-)

Here is an Arc Flash Demonstration with sound.

With all this PR on the electrical problems that are a whole of people at the NSA trying to figure out what went wrong with the electrical design, equipment, and installation.  

Heading to 7x24 Exchange San Antonio, are you?

A bunch of us our coordinating our schedules to get together at 7x24 Exchange San Antonio.

Here is the site for registration.

NewImage

I'll be there and looking forward to report on the presentations.

More and more of my data center friends are attending 7x24 Exchange and I am making more friends at 7x24 Exchange.  If your goal is to network in the industry and you haven't gone to 7x24, you should give it a try.

3 Forces for the Magic of Insight

I posted about a book on Seeing What Others Don't.  The book focuses on developing insights.

The last paragraph in the book is

The magic of insights stems from the force for noticing connections, coincidences, and curiosities; the force for detecting contradictions; and the force of creativity unleashed by desperation.  That magic lives inside us, stirring restlessly.

There are too many words in this.  I like to think of this as.  

The three secrets for achieving the magic of insight are seeing patterns, recognizing anomalies, and tapping the source of trying what others haven't.

Slate.com dives into the details on Healthcare.gov issues, discusses back-end server issues

Healthcare.gov's availability and usability is in the new since Oct 1 launch.

Slate.com has a post on what is behind the problems.

They are finding Oracle DB errors.

“Error from: https%3A//www.healthcare.gov/oberr.cgi%3Fstatus%253D500%2520errmsg%253DErrEngineDown%23signUpStepOne.”

To translate, that’s an Oracle database complaining that it can’t do a signup because its “engine” server is down. So you can see Web pages with text and pictures, but the actual meat-and-potatoes account signup “engine” of the site was offline.

And who the contractors are for the client web front end and the back-end.

This failure points to the fundamental cause of the larger failure, which is the end-to-end process. That is, the front-end static website and the back-end servers (and possibly some dynamic components of the Web pages) were developed by two different contractors. Coordination between them appears to have been nonexistent, or else front-end architect Development Seed never would have given this interviewto the Atlantic a few months back, in which they embrace open-source and envision a new world of government agencies sharing code with one another. (It didn’t work out, apparently.) Development Seed now seems to be struggling to distance themselves from the site’s problems, having realized that however good their work was, the site will be judged in its totality, not piecemeal. Back-end developers CGI Federal, who were awarded a much larger contract in 2010 for federal health care tech, have made themselves rather scarce, providing no spokespeople at all to reporters. Their source code isn’t available anywhere, though I would dearly love to take a gander (and so would Reddit). I fear the worst, given that CGI is also being accused of screwing up Vermont’s health care website.

Part of the reason why this post makes sense and is researched well is it written by a SW developer.

 

About

davidheadshot-300x221I am a writer and software engineer. I’ve worked for Google and Microsoft. I live in New York with several thousand books. I have contributed to Slate, the Times Literary Supplement, The Nation, n+1Bookforum, Triple Canopy, The Quarterly Conversation, and elsewhere.

The closing remarks are proof the author knows what he is talking about.

Bugs can be fixed. Systems can even be rearchitected remarkably quickly. So nothing currently the matter with healthcare.gov is fatal. But the ability to fix it will be affected by organizational and communication structures. People are no doubt scrambling to get healthcare.gov into some semblance of working condition; the fastest way would be to appoint a person with impeccable engineering and site delivery credentials to a government position. Give this person wide authority to assign work and reshuffle people across the entire project and all contractors, and keep his schedule clean. If you found the right person—often called the “schedule asshole” on large software projects—things will come together quickly. Sufficient public pressure will result in things getting fixed, but the underlying problems will most likely remain, due to the ossified corporatist structure of governmental contracts.