Skip to main content

Taking Heat for a Great Idea

Johnnie Moore's take on Scoble is definitely a bit fresher than the others comments .

Corporate deals with the "what is a blog supposed to be" ramifications.

Some immediate points on Scoble's letter and the comments afterwards:

1. Robert is a microsoftie in the same vein as the Excel 3.0 team : that is, we can create the best ________ possible. You know something? They can. The Fox team does it regularly (despite some comments posted on Channel nine's video). It's not arrogance - it's a challenge. I want my software to run on everyone's computer - I want everyone cool to be using my music player.... the fact that he works for the biggest software company doesn't mean it's going to work. It just means he's laying the challenge: build a "cool" media player. (and some people are responding)

2. Points should be given for anyone who is willing to write an open letter to his boss for everyone to see and also put the steps out there.

3. MS is going after two areas: the business world and the "cool" area. They own the business world but feel some pressure - they've never really made true in-roads in the "cool" area. Very few companies, other than Apple, have. I know Linux is all very good and exciting but come on make a user interface that CHANGES the way we work. "Cool" must be revolutionary not evolutionary and that's a hard step for a company as large as MS to make.

4. MS does have companies making media players - the problem is, it's a consumer market. As they've realized with the xBox, it's hard to be "cool" and make tons of money. Apple knows that -

5. People need to stop looking at companies based on their lawyers. Once a company starts relying on their lawyers for real basic things (like MS does), they need to take a step back. - Robert, this may be the place where you want to START telling BillG to work on. He gets technology - but someone is giving him really bad legal advice if he wants to play nice.

Corporate lawyers believe that everyone is bad, wanting to screw them. Most people don't - they want something that works and want to try it out to get it going right (this is what great customer service is all about). If you aren't happy with it, tell them and if you're reasonable, they will likely take it down.

In a nutshell, arrogant? Hardly - Scoble is throwing down the gauntlet to his own organization. The real issue with MS is whether or not their lawyers will allow anyone to do anything with it.

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

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

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