Skip to main content

MSDN Channel 9

Hey - wow - now this is kind of neat.

Discussions and the like with the actual devs (or maybe more to the point the program leads) at MS.

Here are the basic rules. If they sound kind of like a Wiki or the like, I think that's because it is like one. A multi-person Blog with video. And hey, there's Yag in there too. Very cool - check it out.

1. Channel 9 is all about the conversation. Channel 9 should inspire Microsoft and our customers to talk in an honest and human voice. Channel 9 is not a marketing tool, not a PR tool, not a lead generation tool.

2. Be a human being. Channel 9 is a place for us to be ourselves, to share who we are, and for us to learn who our customers are.

3. Learn by listening. When our customers speak, learn from them. Don't get defensive, don't argue for the sake of argument. Listen and take what benefits you to heart.

4. Be smart. Think before you speak, there are some conversations which have no benefit other than to reinforce stereotypes or create negative situations.

5. Marketing has no place on Channel 9. When we spend money on Channel 9 the goal is to surprise and delight, not to promote or preach.

6. Don't shock the system. Lasting change only happens in baby steps.

7. Know when to turn the mic off. There are some topics which will only result in problems when you discuss them. This has nothing to do with censorship, but with working within the reality of the system that exists in our world today. You will not change anything by taking on legal or financial issues, you will only shock the system, spook the passengers, and create a negative situation.

8. Don't be a jerk. Nobody likes mean people.

9. Commit to the conversation. Don't stop listening just because you are busy. Don't stop participating because you don't agree with someone. Relationships are not built in a day, be in it for the long haul and we will all reap the benefits as an industry.

Levy and Griver - Why not complete transparency?

Comments

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

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. ...

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...