Commentary

Thomas Claburn
 

Intel's Awful Code Names

Apple's relationship with Intel has done wonderful things for both companies. When Apple's engineers were managing the complicated transition from PowerPC chips to Intel silicon, Intel engineers were there to help. No doubt computer buyers are better off for this intermingling of talent.

Apple's relationship with Intel has done wonderful things for both companies. When Apple's engineers were managing the complicated transition from PowerPC chips to Intel silicon, Intel engineers were there to help. No doubt computer buyers are better off for this intermingling of talent.If only Intel's marketing department engaged with Apple's sales personnel in the same way.

Apple has a pretty good track record in terms of coming up with engaging product code names. Jaguar, Tiger, and Leopard may not be brilliant wordplay, but they're pretty good. The words are evocative and not particularly open to ridicule, as might be the case if Apple chose a code name like Shrew or Vole. Likewise, even for code names intended for internal use, like Dulcimer, the iPod's working title, Apple does well.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Intel, on the other hand, has some of the worst product code names ever, based on place names. Consider Harpertown, Penryn, Conroe, or Merom. It's like Intel's marketing people are just throwing darts at a map.

Back in the early '90s, Intel's 486 and Pentium chips had formidable-sounding code names: Triton, Mercury, Aries, and Saturn. Compare those with more recent ones that don't so much evoke anything as make you scratch your head: Whitney, Tehama, Colusa, and Canterwood. These aren't the sort of names that generate excitement. Sure, if you live in Colusa, it may be nice to get the nod from Intel. But in the wider world, the name isn't fraught with meaning.

Intel archrival AMD has done a bit better, having moved from the excessively whimsical names of dinosaurs in The Land Before Time (Sharptooth and Chomper) and the blandness of its K-series chips to code names like Mustang, Corvette, Sledgehammer, and Spitfire.

Granted, Intel has had a lot of chips to name -- Wikipedia has a rather lengthy list. But surely Intel can put a bit more effort into giving its chips distinct identities. The company is calling its new "many-core" architecture Larrabee.

It's a great name ... for a mule, or maybe for a necktie designed to double as a bib.

# # #

"What's that?"

"It's a 'Larrabee.' "

(Puzzlement.) "It's sorta wide for a tie."

"It's not just a tie. It's also a bib." (Silence.) "You know, for eating lobster and such. They advertise them on TV."

# # #

Next time, Intel, how about a code name that aims to convey something that might actually make you want to buy the product?

(I know your legal team is telling you to stay away from trademark territory, where all the interesting words live, but you've got to take some risks. And what better publicity could you get than a lawsuit?)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links