Taking down a published post is a no no with Microsoft.

Last week, I posted a blog entry outlining why I picked a fight with Adobe (actually Fight is an aggressive word, it was more of a debate). I posted it the other night at 11:00pm. It was the last thought of the day so to speak, and then went to bed.

I woke up the next morning and it was the first thought of the day. Usually, my gut tells me when I wake up thinking of something this politically hot, maybe its not in my own best interest to keep it there. So I took it down, thinking that since my blog is quite new, folks wouldn't care.


You do, and I can appreciate the conspiracy theories out there on why but to be honest, I'm new to the job, I've had to read all the policies within Microsoft I could find, and this was one of these things were I wasn't sure if it was a gray area or not (so to my readers of the press whom are thinking there is a juicy story there, sorry to disappoint). That being said,  to be keep safe, I thought I'd jump ahead of the curve and take it down.

Internal discussions occured, and I was asked to put it backup which has taught me a valuable lesson. Stand by what you beleive in, and Microsoft will also do the same (within reason and upholds our internal policies etc).

Its clear to me, being an outsider looking in, that Microsoft continues to suprise me daily on how open the company truly is to change. It at times appears to welcome it more so then anything else they wish to do. This is a positive thing for the development community of old and new as it means that admit they aren't perfect and want to push themselves further to be perfect.

So there will be more disagreements with competitors, friends and what not. There will also be more agreements with them, but overall my role is to engage both new developers and old about all that encompasses the web and how Microsoft can play a role.

Yet, between you and me: I'm into it more to bring fun back to development, as when I first started it was about fun, watching code and design mash together. Microsoft has new toys, and I've played with the old ones and also folks like Adobe's toys, but I find the new Microsoft ones more appealing (3D and XML, it takes me back to the days when I played with VRML, so I'm loving it).

Anywho, appreciate the feedback and conspiracy theories and I chuckle at the notion that Bill or Steve sent an internal urgent memo stating "Take down, he could bring us all down" or something along those lines. (It's flattering to think I appear that prominent, but sorry, it's misguided)

Comments (3)

  1. davidlem says:

    There are no bad posts Scott! Just bad readers!

  2. John Dowdell says:

    Yup, "post-posting regret" takes on new dimensions when you’re an individual writer who is associated with a group, particularly when it’s a group which draws as many hot-button reactions as Microsoft does.

    Sometimes deleting a post actually attracts far more attention to it… I can’t find a good search term right now to bring up a full set of examples, but in both politcal and technical blogs there are notable prior examples of others retrieving the deleted text from search engine caches or other internet archives… here’s one:


    ah, here’s more:


    If you’ve got second thoughts after publishing, then one tactic is to use strikethroughs to replace the text while still leaving the historical record, or to put an "Update" block at the top with your later thoughts on the issue.

    A related technique is to "bulletproof" your posts… to write shorter texts which emphasize the core points you wish to convey… minimizing the extraneous material others might find objectionable… speaking of your own direct personal experience and knowledge rather than generalizing to the whole.


  3. Garry Trinder says:

    I bow before your wisdom JD, and take on board your thoughts. I’m famous amongst my peers/friends/etc for long rants.

    My old mananger use to limit me to 10 bullet points and 2 sentences per bullet points for new ideas. It was tough! 😉

Skip to main content