Afternoon Doughnuts 8

Due to a temporary reassignment this morning, I spent my usual blogging time moving all of my computer equipment from one cube to another.

  • Sam Gentile writes about the ALT.NET moniker. My favorite of his principles is number 4 where he discusses the importance of tools versus principles and knowledge. I really agree that knowledge and principles are more important because the best tools in the world can’t help us if we don’t know how and when to use them.
  • I find Mark Cuban’s ideas (here and here) about how advertising on the Internet is different than traditional media advertising. He points out that the ability of a provider to deliver higher simultaneous views is more important and valuable than delivering views for a longer period of time. I think he right on here, even if I believe his football league is going to fail. (via Blog Maverick)
  • Worse Than Failure has been running an unusual contest to get the most interesting, buggy, and unusual way of writing a calculator application. They have 12 finalists for readers to review. I find that the descriptions of how the programs work (or don’t) to be hilarious.
  • As I have been working on service-oriented management and monitoring I have given a lot of thought to the best way to present the data. Doesn’t it make the most sense to primarily display information from the business process point of view? I would be interested in your feedback.


Hi Dale, The best way to present data in a SOA infrastructure... interesting problem. The data being passed, if the design is good, is a subset of the canonical data model needed to understand or interpret a particular business event. However, each producer or consumer will display or lay out that data differently. Many will translate it. Therefore when you present the information from the 'middle', it is unlikely that the business would necessarily recognize it! Therefore, I'm not sure what it means to display information from the business process point of view. I believe that it makes sense that the canonical schema for the event in question should register a stylesheet or provide a link to one that can be used to display the data.
Hmmm...that is an interesting point. I wasn't actually thinking about presenting it from the middle point, but more from an overall view. I would think that the business would understand the process if it was named after what it does like create customer. Monitoring could then show the process from initiation to completion. You should then be able to drill down to each service along the way. I would consider this somewhat similar to how Amberpoint shows it.