(Note: This post has nothing specifically to with Ubuntu or Linux. It's more about what naming conventions actually work best for me versus everyone else
( Read more... )
i have that problem at work. the hardware and firmware teams call the models by their code names, which are (obviously?) not written on the product itself.
Now here's the ironic thing: I have the opposite problem at work most of the time. Since I work with the design long before marketing comes up with the part number, and since the same design actually sells as multiple part numbers, just configured differently, I have to get a cheat sheet that maps the large space of numbers down to the small space of design names I know.
For example, C6414, C6415, C6416 I know as "Kelvin". There's probably a half dozen or more part numbers associated with the design I know simply as "Faraday". TCI6488? C6474? etc.
I guess the problem there is that the number is late to the party (and in many cases, I don't hear it until a field engineer uses it in a question sent to me) and there's many numbers for one product. For something like Ubuntu, which uses release dates for version numbers, the number is known in advance and it's a 1:1 relationship.
Comments 2
Reply
For example, C6414, C6415, C6416 I know as "Kelvin". There's probably a half dozen or more part numbers associated with the design I know simply as "Faraday". TCI6488? C6474? etc.
I guess the problem there is that the number is late to the party (and in many cases, I don't hear it until a field engineer uses it in a question sent to me) and there's many numbers for one product. For something like Ubuntu, which uses release dates for version numbers, the number is known in advance and it's a 1:1 relationship.
Reply
Leave a comment