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

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…