Archives
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- January 2006
- December 2005
- November 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- January 2005
- December 2004
- October 2004
- September 2004
- January 2004
- December 2003
- October 2003
- June 2003
- January 2003
- December 2002
- June 2002
- January 2002
- January 2001
- May 2000
- April 2000
Categories
Meta
Monthly Archives: February 2008
How To Deal With Analysts: #11 Kicking the Tires
I remember a briefing I once had with Oracle, where the Oracle marketing man proudly proclaimed that “we now have a Soundex capability.”
In case you didn’t know: The Soundex algorithm is a method for indexing names by sound, according to their English pronunciation. The idea is that names with a similar sound like Smith and Smythe will have the same index. It’s a simple algorithm that collapses any name into a 4 character code. Rumor has it that the algorithm was invented in an effort to sort out the names of English casualties in World War One – because many of the conscripts were not literate, so some of their names were recorded wrongly.
Replying to the Oracle marketeer I said, “but that only amounts to about 10 lines of C code.” The response burst his balloon. He had no clue as to how complex Soundex is to implement and he was astounded that I knew. It was an unlikely event, but he’d run into an analyst that had actually coded a Soundex search.
This is a powerful reason, by the way, for keeping a profile on analysts that you brief, with specific reference to their technical background and understanding. I was a software engineer once. That doesn’t mean that I’ll always be right about whether a software product is good or bad, but it does mean that I’m pretty good at “kicking the tires”.
Lies, Damn Lies and Heuristics
Listen to me! I have a software product to die for. It can develop applications that are much more sophisticated than are ever developed using Microsoft’s Visual Studio, or any configuration of Eclipse with any set of build tools. If it’s fed with the right information, it can duplicate or exceed all the functionality of SAP, including every one of its modules and likewise it can deliver anything that any of Oracle’s application portfolio can offer, or Microsoft’s for that matter.
And best of all, it’s free!
It’s the GNU C compiler.
You see, I didn’t tell a lie, but I mangled the truth so badly that it’ll never walk again.
In the 1990s when I used to spend a good deal of time evaluating development tools and CASE tools, I’d run into that dishonest kind of presentation again and again.
Probing into a product’s capability, I’d ask, “if you put water into it and boil it, can it make a decent cup of tea”.
And the marketeer would reply, “yes, we can achieve that via the low-level API,” which means “no”. And by the way, every technical analyst worth his sodium chloride knows that means “no”.
The Right Briefing Presenter
Just as you set a thief to catch a thief, you should send a technician to brief a technician. If you don’t, you risk having a poor opinion of your product proliferate. Even on a good day, an analyst with good technical skills is capable of assuming that the deficiency is in the product, as well as the presenter.
And by the way, that’s one of the reasons why IT vendors pay analysts to do message testing.
Note: This posting is one in a series of postings that deals with the topic of dealing with analysts. Click here for links to other postings in the series.
Posted in Campaigns
Tagged analyst relations;, analysts;, Microsoft, Oracle, sodium chloride;, software tools;, Soundex algorithm;, Subject, Visual Studio;
2 Comments
Shock, As Diebold Accidentally Releases Result of 2008 Election Early
The Onion is perhaps the best satirical web site in the US. They hit the nail firmly on the head at times, as they do in this video which reflects concerns about voting fraud in New Hampshire and New York State. Lol funny.
Note: If your company blocks videos (some do) you won’t be able to see anything below this sentence. If that’s the case, then log on at home to view it.
Posted in R&R
Tagged Diebold, Humor, New Hampshire;, Politics, satirical web site;, Subject
Leave a comment
Ten Reasons Why Software Cannot Be Free
Information wants to be free! Software should be free! PCs should be free! Cars should be free! Beach side properties in Hawaii with 200 yards of beach front and 20 acres of grounds should be free! Can you see where I’m going with this? Not into the arms of French Anarchist Pierre-Joseph Proudhon, who declared “La propriété, c’est le vol!” (property is theft).
The capitalist system is not without its faults, but it is very effective at “allocating scarce resources among competing uses”. The market mechanism, implemented in a multitude of ways, is the engine of the capitalist system, and it has the wonderful advantage that it doesn’t require a great deal of oversight. But it appears to raise paradoxes when you examine the software market. Consider the issue of Falling Transaction Costs, which is relevant to what I’m discussing here. The key fact from the link above is that computer transaction costs fall at the rate of about 20% per year driven by both Moore’s Law and Metcalfe’s Law. You would think, wouldn’t you, that the cost of software ought to follow the same type of curve?
The Software Market
Here we are in 2008 and I go into the Apple store yesterday to discover that Microsoft wants to charge me $239 for an upgrade to Office 2008 (from Office 2004 on the Mac). I’m not sure I even paid that much for Office 2004 in the first place, and I’m certainly not going to buy. Now if I look on the Internet I’ll discover that NeoOffice, a very capable Office clone and a reputable Open Source effort is available for nothing at all. If Microsoft Office is overpriced, is it fair to say that NeoWare is underpriced? Nothing does seem like a very low price.
Let’s deal with Microsoft first.
The company is a monopolist that takes no note of the cost of production of its software. It charges a high price that leverages its monopoly position. The only mechanism available to correct this “market defying tactic” is antitrust action. From a business perspective Microsoft got very lucky in 2000. George Bush got elected and one of his first moves was to squash the action that the US DOJ was taking against Microsoft. The US policy on regulating monopolies has since been “Companies shouldn’t be regulated for any reason, in any way, any where, at any time, by any one, ever, at all.”
Europe (an economic block that is actually larger than the US) has a different policy which can roughly be stated as: “Monopolies are fundamentally unhealthy and need to be regulated, and that means you Microsoft.” Action by the European Union against Microsoft resulted in the recent $1.3billion-do-we-have-your-attention-now fine. No matter whether you think the fine is too high or too low or, as Goldilocks would say, “just right”, it’s worth noting that the fine is only likely to push the price of an Office 2008 upgrade higher. So that’s a result? Not.
The only thing likely to pull the price down is competition. And, as I have said, MS Office has such competition on the Mac from NeoWare. And the price of NeoWare is nothing.
Or is it?
Ten Reasons Why Nothing is not Nothing
Conceptually you’d expect free software that is pretty similar in function to seriously over priced software to sweep the market. In some areas it does, but in some it doesn’t. Why?
The answer is that all software has hidden costs and some of these costs are prohibitive for some buyers. Here’s a list of ten reasons why free software may not be free, as far as the buyer is concerned:
So, like it or not, that’s why Microsoft can charge $239 for an Office upgrade.