Do I Dare Redefine the Cloud… Part 1 - To Define or Not to Define

I cannot count the number of times I was presented with a PowerPoint slide depicting the NIST definition of Cloud Computing. I also cannot tally the substantial amount of time that many IT professionals spent trying to explain what the cloud means and how the NIST definition would relate to any use case in any environment.  Truth of the matter, I am not sold… I have tried time and time again to convince myself that having the NIST definition is better than having no definition at all. Or in fact better than having hundreds of colliding definitions. But why not give it a try…

According to Dictionary.com, a definition must meet “the condition of being definite, distinct, or clearly outlined”. In other words, definitions must maintain the characteristics (not to borrow from NIST) of simplicity, clarity, and preciseness.  Definitions are human’s way for simplifying complex constructs and controlling their knowledge of their focus subjects. Definitions use categorization and classification methods to narrow down the qualities and features of what’s defined.   Their components must not contradict or overlap, or they will lose their value.  

Additionally, definitions in the IT world must wed the reality and constructs of both business and technology. That only will make them a good tool for defining useful IT strategies and providing a clear path of technology adoption. Most importantly, good definitions become the basis of solid Enterprise Architectures and the foundational elements of the technical terminology that organizations communicate with. Otherwise, an IT definition becomes no more than a modest theory.

That’s why I believe that technical definitions should never be set in stone. They should rather evolve over time and with the collaboration of the industry, standards organizations as well as the community. In my coming blog entries, I will attempt to simplify and refine the NIST Cloud Computing definition. I will also make the case for how businesses and organizations could consume this definition and employ it to facilitate technology adoption. Stay tuned… 

The 11 E-Mail Habits That Annoy Me… (in random order)

1. E-mailing the same attachment back and forth… Just give me a link for God’s sake!
2. Sending a huge trail of FYI forwards… if it takes me half an hour to get to the original e-mail, chances are; I will just forward it with an FYI to someone else!
3. Replying with too many “Thank You” e-mails… yes, you can thank me enough!
4. Using tacky backgrounds and colors (stationary)… your fancy designs will be copied every time your e-mail is forwarded or replied-to creating a massive trail of repulsiveness!!!!
5. Footnoting your e-mail with a 2000 word legal disclaimer… once again the e-mail will turn “jumbo” after 2 or 3 forwards! No one reads them, stop using them!
6. Using capital letters to type your entire e-mail… STOP SHOUTING PLEASE!!!
7. Sending the entire e-mail content in the subject line… isn’t that why they created instant messaging!
8. Requesting delivery receipts for every single e-mail you send… why is it so important for you to know whether or not I read your “Thank You” email!
9. Not using signatures… if you want my attention and help, please tell me who you are and how I can reach you!
10. Marking all your e-mails URGENT… I know I’m not that important!
11. Manually signing your e-mail when you have already assigned an automatic signature. The resulting:“Respectfully yours, John Respectfully yours, John” is guaranteed to give you double vision for the rest of the day!