Skip to main content

The Microsoft Code

When I started reading this, I was worried it would get really long (and possibly boring). At 6 chapters, it's short, sweet and just down-right funny. A hilarious send-off of the Da Vinci Code right at Microsoft.

The funniest exchange (abridged) - a discussion on the user interface choices in Microsoft products:

"It should be easy to rotate, I think it's here on the Format menu, you just choose Font or Paragraph. Hmm, there is no Paragraph choice..."

"Maybe it's on the Edit menu, under Object."

The level 71 developer clicked a couple of times. "Object just highlights it. It's probably somewhere on the Format menu. Is it Alignment? No, that's just left/right/center."

"Let's try the Text Box option on the Format menu," "Great, it's a modal dialog with tabs. What about the Position tab?"

"Hey, what about the Text Box tab. Of course, we'll have a dialog called Text Box and then put a tab called Text Box on it. Oh look, you can rotate the text by 90 degrees, but not 180 degrees."

"What about the Size tab?"

"The Size tab? Why would rotation be on a tab called Size? Never mind, here it is on the Size tab.


Quick and easy to read and just down-right funny.

So who is Mini anyways?

Proudly Serving My Corporate Masters: The Microsoft Code: Chapter 6

Comments

Carlos Alloatti said…
"Mini is an anonymous blogger, who generally talks about things that Microsoft is doing wrong, and/or that he wants to see improved. His motto is to, by slimming down Microsoft, make Microsoft a more lean profit-making machine"

http://scobleizer.wordpress.com/2006/04/24/how-microsoft-can-shut-down-mini-microsoft/

http://minimsft.blogspot.com/
Andrew MacNeill said…
Thanks Carlos - I knew "what" he was - the Code actually hints at who he might be , which is why it's funny.
Carlos Alloatti said…
Oh! lol. I understand know, you meant "who".

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...