Veteran Microsoft engineer Raymond Chen has penned a blog that gives further insight into the inner workings of the software titan under Bill Gates's leadership.

A few years ago, Chen gave a [1]brief history of several Microsoft projects, all code-named Highlander. One of them gave rise to Passport, which would evolve into the Microsoft Account known and beloved by all today. "There can be only one" … password. Get it? (It's the tagline of the movie [2]Highlander .)

It's a theory familiar to many engineers: A corporation might have several teams working on several projects, all with the same goal, and the team with the "best" project would win.

[3]

The definition of "best" is open to debate, but we digress.

[4]

[5]

Chen also gave another example of the code-name Highlander being used. We're told there was, back in the day, a team (Chen called it Team 1) responsible for a client-server product that developed both the server and client software, while another (let's call it Team A) wrote an alternative client with what it felt was a better user interface.

Microsoft management looked at the options and chose to go with Team 1's client over Team A's.

[6]

But that was not the end of the story. According to Chen: "Team A did not go down without a fight." It came up with "an even more awesome" client, dubbing this version Highlander, and built an internal website for it that played the music from the movie when visited. Chen wrote: "The tag line There can be only one reflected their belief that the battle was to the death and that their project would emerge victorious."

Once again, management chose Team 1.

[7]Microsoft whiz dishes the dirt on the Blue Screen Of Death's colorful past

[8]Porting the Windows 95 Start Menu to NT

[9]How many Microsoft missteps were forks that were just a bit of fun?

[10]Techie told 'Bill Gates' Excel is rubbish – and the Microsoft boss had it fixed in 48 hours

However, that is not quite the end of the story. While Chen has been scrupulous in not revealing the actual name of the product concerned, [11]his more recent blog offers some more details about this internal politicking within Microsoft.

Team A, you see, chose the name Highlander not because they had to be selected – although that would have been nice – but because somebody had to win. Chen wrote: "They chose the code name Highlander to highlight that the situation with two clients for the same back-end was ridiculous and needed to be fixed."

One unnamed colleague from Team A remarked: "The internal competition was driving us nuts for years." According to Chen, the colleague added that his friends on Team 1 also thought the situation was ridiculous.

[12]

As for the resolution, in true Microsoft style, the teams were so far apart on the corporate hierarchy that the nearest common manager who could make a decision was none other than Bill Gates himself.

"Magically, the issue was resolved before we built Highlander," the colleague on Team A said, according to Chen, "so maybe our code name helped." Yeah; Microsoft went with the other one.

Thankfully, Highlander II was not mentioned. After all, "The Quickening" is hardly a moniker that could be applied to much of what comes out of Redmond these days. ®

Get our [13]Tech Resources



[1] https://devblogs.microsoft.com/oldnewthing/20140923-00/?p=44003

[2] https://www.imdb.com/title/tt0091203/

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Zr93pYOiT@KVJKVIkGDnkwAAAEE&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Zr93pYOiT@KVJKVIkGDnkwAAAEE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Zr93pYOiT@KVJKVIkGDnkwAAAEE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Zr93pYOiT@KVJKVIkGDnkwAAAEE&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://www.theregister.com/2024/08/02/who_wrote_windows_bsod/

[8] https://www.theregister.com/2024/07/17/porting_the_windows_95_start/

[9] https://www.theregister.com/2024/06/27/microsoft_windows_fun_fork/

[10] https://www.theregister.com/2024/08/09/on_call/

[11] https://devblogs.microsoft.com/oldnewthing/20240813-00/?p=110127

[12] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Zr93pYOiT@KVJKVIkGDnkwAAAEE&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[13] https://whitepapers.theregister.com/