...and I've been meaning to ask this question for a while...
What's the deal with the names in the first place, and where do they come up with them? It's not like they are trying to sell cars or something, I would think model numbers (like they already have) would be sufficient.
Not cracking on it, just find it kind of curious...
Well, you need a name to tell the teams apart and you need a name to put on presentations and such. So clearly you have to call the projects something. But you are right, numbers are easier. Back when I first joined Intel in 1995, all projects just had names that were like model numbers.
The original Pentium was internally called the "P5" project which was a 0.8um process (800nm

) called p650 (6" wafer, process node #50, they increase by two with each generation, 22nm is p1270 - 12" wafer, process node #70, or 10 more than the p650 process... but I digress). Then they did the equivalent of a "tick" ported it to the p852 process technology which was 0.6um process generation, and called that project P5C (the "C" for compaction), then they ported P5C to 0.35um (p854) and called that P54CQS (the "QS" for "quick-shrink"), then they did a better compaction of the design for the process and called that P54CS. Then after that, the Pentium Pro was internally called the P6, and then there was P6C, etc.
The problem was, as I recall, that other companies would name their things by Intel's model numbers and that got confusing. I don't remember what the actual example was, but it was as if someone called something their chip "P54CS" and then because Intel was calling it something and some other company called their thing the same thing, it led to confusion. So then Intel tried to trademark these project numbers - like "P6" - but the trademark office said that the numbers were too generic - again, all this is from my memory, and I'm old (and thus forgetful) and I wasn't directly involved so this is hearsay as well. So the trademark office effectively said "you need something that's not just a letter and a couple of numbers" so then Intel started naming things after local cities, towns and landmarks and then trademarking these names as project names. And they still do this today.
At the time, there was a whole lot of engineers who were irritated by the change. Before if someone said "I work on P6CS" then you knew right away what it was. But then after we made this shift to project names they'd come back afterwards and say "I work on Klamath" and you'd have to ask "I forget... what is Klamath again?" and then they'd say - and this is totally true because I remember it - they'd say "oh, it's P6C" and as an engineer you'd nod and go "oh, P6C, cool. How's that going?". And for a long time after that, people would still call the projects by the old naming system when they would talk to each other, but all the slides would have the names, and there was a fair bit of confusion translating so then we'd have "decoder rings" that would tell us what the names meant. But nowadays, we just use the names and there's less confusion... sort of.
And for what it's worth, I am not an official Intel spokesperson, and you should take my stories as accurate as I remember them, but not as anything official from the company.