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

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

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...