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

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…