claim

Allow or Enable Part 2

Just after I posted Part 1 I found:

A Bill of Rights for Users of the Social Web

No less than 4 lines starting with 'Allow' - oh no.

Empowerment not permissions please.

Allow or Enable Part 1

So I'm starting a new season of conferences and development days MIX:UK07 is on Tuesday. I am very likely to be hearing what the major corporations are going to Allow developers to do. I don't want to be Allowed - I want the development Enabled.

Allowed / Enabled, what's the big deal? What's the difference?

Well consider the two following statements:

My parents allowed me to go to college.
My parents enabled me to go to college.

It is a difference of attitude - it ranks up there with 'expose the
functionality'. It is actively supporting instead of giving permission.

Part 2

MIXUK07 Software Development

Offline RIA?

So I need to build a cross-platform (Mac & PC) RIA that works offline - Silverlight 1.1 plus Google Gears? Or the competition?

That's why I'm going to Mix 07 - any opinions?

Expose the Functionality

Whenever I hear the words "Expose the Functionality" it makes my blood run cold.

I guess we can just about forgive the guys standing in front of the PowerPoints, they don't know any better, but if a developer ever uses those words just fire them, it will save you so much in the long term. Why?

Software development 101. First - define the requirements. If your requirement is to "Expose the Functionality" then that is the best outcome you are ever going to get out of this project. If the requirement is to provide a great platform for creating and executing software then you may get a lot more.