Graham is VP of Marketing at Real Intent. He has over 20 years experience in the design automation industry. He has founded startups, brought Nassda to an IPO and previously was Sales and Marketing Director at Internet Business Systems, a web portal company. Graham has a Bachelor of Computer … More »
Reporting Happiness: Not as Easy as You Think
January 18th, 2015 by Graham Bell
Like other successful design automation companies we have many happy customers that use our tools. Marketeers like myself crave getting customer stories and comments to share with the world at large. While an individual engineer is happy to share his point of view why he likes one of our tools, before it can be made public and ascribed to engineer X at company Y, it must pass through a gauntlet of approvals by upper management at the customer. Often there is a “quid pro quo” in this process. In other words, to get company management to approve the quote, some benefit in the form of additional pricing discount, or extra short-term licenses is negotiated. Or sometimes management sees Real Intent’s static solutions as one of their ‘secret weapons’ and don’t want to share the good news with potential competitors.
I recently got a comment from an RTL engineer regarding our Ascent Lint tool, which does code and style checks. We like to think it is the market leader in speed, capacity, low-noise and designer debug productivity. It is is gratifying to get reports that confirm this from a customer. As outlined above, I can only share this quote anonymously which certainly makes it mysterious regarding who said it:
“Our company has been a proponent of RTL linting since inception in order to deliver high quality functional designs on schedule”, said RTL Engineer. “Our engineers lint their designs constantly in order to uncover common and uncommon code issues before ever spending expensive cycles in the simulation and synthesis stages. Our Ascent Lint flow gives designers a setup-free, push-button process that provides interactive results and can be run at any point in the hierarchy from chip level to complete blocks to leaf modules. Designers have confidence in the tool because the report of false failures is very low. The support by the Real Intent staff has been excellent in terms of quickly fixing bugs, finding coverage holes with existing rules, and expanding the rule-set to meet our company’s design methodology.”
Do you share your comments with your tool vendor? They want to hear your feedback, especially if it includes some nuggets of happiness. Drop me a line if you would like to submit your comments about any of the Real Intent products at email@example.com.
2 Responses to “Reporting Happiness: Not as Easy as You Think”