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

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
1 comment
Read more

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