« Blogging a dead horse | Main | Linksys - no longer a great wireless router »

June 16, 2006

Broken windows conversation broken

Robert Scoble drew the world's attention to "a great post" on Philip Su's blog, The World as Best I Remember It, on MSDN. Su, a Microsoft staffer who had managed developer teams in Windows for five years, explored reasons for the delays in shipping Microsoft Vista. Too bad that Philip quickly reacted by pulling the post, on the grounds that "what started as an opinion on the challenges of managing large software projects has turned out to be a rallying point for detractors, which isn't interesting or productive."

Philip claimed to have removed it "of my own volition, without any external pressure whatsoever", but that also turned out to be a rallying point for detractors in the comment thread at Scobleizer, many of whom speculated on other motivations for the sudden end of the "great post".

What happened next was that the post was reinstated, with the explanation that it was only removed for editing. Then - uh-oh - it came back down again.

However, over at Mini Microsoft, readers learned how to resurrect the post. What you do is add Su's feed to your Bloglines subscription.

Posted by cw at June 16, 2006 09:29 AM

Trackback Pings

TrackBack URL for this entry:
http://bleedingedge.com.au/cgi-bin/mt/mt-tb.cgi/930

Comments

Windows process has gone thermonuclear. Imagine each little email you send asking someone else to fill out a spreadsheet, comment on a report, sign off on a decision – is a little neutron shooting about in space. Your innocent-seeming little neutron now causes your heretofore mostly-harmless neighbors to release neutrons of their own. Now imagine there are 9000 of you, all jammed into a tight little space called Redmond. It’s Windows Gone Thermonuclear, a phenomenon by which process engenders further process, eventually becoming a self-sustaining buzz of fervent destructive activity.

Old saying circa 1980s - the productivity of programmers increases by the square root of the number of programmers - with 9000 programmers, let's see, the productivity improvement over one programmer is 95. Don't forget the coordinators, architects, program managers, marketing types and so on who stick a finger in.

Posted by: anandasim [TypeKey Profile Page] at June 16, 2006 10:32 AM