Skip to main content

Josh Ledgard: The Issue is What Shouldn't We Share With Customers

Josh makes a note about why the MS Dev Team is sharing information and the concept behind it is a great one. One of the nice things about open source projects is the overall transparency of how the project is going - well, it's possible to have that same transparency in non-open source projects which is precisely what they're doing here.

It's also a concept that I'm reading about in Guy Kawasaki's Art of the Start. When you're a start-up and coming out with a new idea, you need to keep it hush-hush until you're ready to come out with it (in fact, RIM did this with their Blackberry device) - but when you're a larger company and you need people to support you, you need to open it up and share it with as many people as possible to get them behind you.

I wish a few companies I work for would do the same with their dev teams. There's nothing worse than having to speak to customers about what the Development team is doing when getting information from them is like pulling teeth.

MS is the whipping boy for so many different groups right now - it's nice to see that they are openly canvassing for greater transparency in their new development.

Giuliani and a Glimpse of Transparency to Come

Comments

Anonymous said…
Thanks for the positive re-enforcement of our ideas. - Josh ledgard
October 30, 2004 at 2:30 AM
Post a Comment

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 .
4 comments
Read more

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...
Post a Comment
Read more

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...
11 comments
Read more