It's important to make a distinction between "guerilla" tactics, and putting the civilian population in danger. Guerilla tactics are essentially hit and run, something the US colonies learned from the Native Americans, which the colonies used quite well against the British.
Putting the civilian population in danger, such as shooting from within a crowd, storing ammunition in hospitals, using ambulances as troop carriers is QUITE different. Those are the "underhanded" actions complained about.
While guerilla tactics do negate much of the American advantage, I believe you'll find most American military members will have grudging respect for a well executed guerilla action. However, shooting at US troops from within a crowd of school children is the sort of action that engenders contempt.
It is one thing to use your resources effectively to negate another forces advantages. It is quite different to put your own civilian population in danger.
For one project I worked on, the code name started out as "Cezanne" (after the artist, I would assume) but was renamed to a geographical location mid-way through the development cycle. We engineers never understood why, and most of the team still kept using the old name in server directories, passwords, etc. We thought we were rebels... ah, the joys of youth.
Likely, Intel legal got wind of the non-conforming name, and decided you needed a "proper" name. I worked on a project where each release was named after elements, then Intel legal descended on us, changed all of our names. Arguing over that is what gave me the education in Intel code name policy.
Other times, the project manager got to choose a "custom" name based on one of his/her favorite places to visit.
Like I mentioned, you can submit suggestions to Intel legal. If all goes well, legal will go with your suggestion. But there is no guarantee of that.
I'd also argue that code names do have meaning, at least for the engineers involved with the project. A code name gives a team a rallying point, or a central concept by which we can understand our involvement in the project. Depending on our experiences in that project, whenever we hear or see that name later on in life, we engineers can either feel bursts of pride, or shudders of grief and disgust.
I'll agree that the code names should have meaning. And of course people will attach a meaning to whatever projects they work on. Even more, people should at least like the name of the projects they are working on. But, there are often some real loser names picked out for things. The basic fact is, Intel legal really doesn't care about meaning, or if the name is stupid or not.
BTW - Hi Brad! I used to work with you on "Rainier".
Really? I happen to be currently contracting at Intel.
I can authoritatively state that Intel code names are meaningless.
All Intel code names are names of some geographical place because geographical locations can not be trademarked. There is no inner meaning, that is by design.
Intel legal has to approve every code name before it is used, to make sure code names don't match up with someone's trademarked name. Because the code names are used in trade press to talk about upcoming products, they are subject to trademark law. Because Intel makes lots of money, they are subject to legal colonoscopy.
The official process to name something entails the following actions:
Open up MapQuest
Find some geographical names.
Compile the list of names into an email to Intel legal.
Pray Intel legal picks one of the names you suggested.
Name the project whatever Intel legal tells you in the emailed reply. If you're really lucky it will be one you suggested.
I used to have terrible handwriting. At one point I decided to fix that, and started printing everything, very slowly. Now I am complimented on my neat penmanship.
I found I need to focus on two things, the first is to slow down enough that I do write well. Second, get all the extra help for pen control you can. There are environmental factors that make handwriting bad, eliminate those.
What I found to work for me is:
SLOW DOWN
Print everything, when that is working well, move to cursive.
Always have extra paper under what you are writing on. The paper provides padding that slows down the pen and keeps it easier to control, and keeps the texture of whatever you write on from messing up your text.
Keep the paper so it does not move. I use a clipboard all the time. The clip keeps the paper from moving.
When starting, only use a Bic Roundstick pen. These are the classic cheap ball point pen, with very slow, but reliable ink flow. You do not want a liquid ink pen, or any of the "roller" ball types of pens. The ink flows way too fast in these "fancier" pens, which is great when your speed is up but causes blotting when you move the pen slowly.
If needed press hard. When I started I used two pieces of paper for every page I wrote. The top sheet would curl into a little scroll, and the it was possible to simply read the indentations left on the second sheet.
Use lined paper or graph paper for everything.
As you get better you'll be able to lighten up on the pressure. When you can get neat writing with barely any pressure on the pen then you'll be able to get your speed up. At this time you'll also likely want to change to using a "gel" ink pen. Never go with a liquid ink pen, they'll blot if you move the pen to slow.
You are rather misinformed about the real situation when Novell acquired WordPerfect. I worked for Novell, through 1999 and know many of the people involved with what happened.
First, what most people don't understand is that WordPerfect was broke when Novell acquired them. Novell, had paid the WordPerfect payroll for months before the acquisition. WordPerfect didn't have enough money to pay their employees.
Second, WordPerfect was a massively mismanaged company. The types of excesses (overly expensive offices, outrageous salaries) now associated with the dot com boom, were all done at WordPerfect. Common receptionists were often pulling in over $80K/yr. There were a lot of reasons for this, the founders were genuinely nice guys that wanted to share what the money they made, they wanted to make people happy. However, while the founders were nice, they were not the smart businessmen.
Third, WordPerfect had a technical culture that didn't like software engineering practice. The big wigs at the company believed they knew better than anyone else how to build software and would not listen to advice. I know people that tried to help WordPerfect improve their software engineering practices but were rather rudely rebuffed. As a result software development at WordPerfect was very expensive.
Novell by contrast was a much tighter ship. Ray Noorda was a businessman that knew how to run a company. He was Novell's angel investor that saved them from going out of business when Novell was in a garage. The finances were much better controlled at Novell, software development was better controlled, everything was managed better at Novell.
Ray Noorda is truly a nice guy, he always looked for ways to help people. Noorda described Novells approach to business as "coopertition" you cooperated on standards and technology, while you competed on value. That did a lot to grow the PC networking industry.
The roots of Novell and WordPerfect are pretty deep too. Both companies were started by Brigham Young University (BYU) students, professors or alumni. Both companies were still close to the BYU campus. Both companies predominately employed Mormons (BYU is a Mormon school, and Utah is a Mormon state). Novell and WordPerfect were the predominate employers in the Utah Valley, the only other major employer was a steel factory. The engineers and management at each company knew each other very well, they went to school together, lived close to each other, and went to church together.
Noorda saw WordPerfect as a victim of Microsoft aggression, Noorda also saw that Novell was also on Microsoft's target list. Look at the choices Noorda had. He could watch WordPerfect die, and see thousands of people in his community lose their jobs, watch the Utah economy tank, and then wait for Bill Gates to do the same to Novell. Or he could try to pull things together and fight it. He chose to fight.
The fact is Noorda is a nice guy, and saved WordPerfect and thousands of employees from going out of business. He also realized that no one else was going to stop Microsoft. If he was going to save WordPerfect, and Novell it required fighting Microsoft. Add to that, the fact that Noorda, genuinely despises Bill Gates, then you have a recipe for a real fight.
The biggest failure of Noorda was that he retired. Noorda's successor Bob Frankenberg was the worst thing that ever happened to Novell. Frankenberg took a company that was very nimble and responsive to users and turned the management into a black hole. The number of managers ballooned, the time to make the company budget went from Noorda taking 6 hours at his dining room table to Frankenberg taking 6 months, with tons of employees. Things only changed when Eric Schmidt took over and eliminated about 70% of the management.
When I left Novell, the culture of the engineers was finally starting to recover from the Frankenberg years. I can only hope Novell gets things together again.
Slashdot Mirror
AirTunes has an amazingly powerful remote. It's called a Powerbook (must be purchased separately...). ;->
Putting the civilian population in danger, such as shooting from within a crowd, storing ammunition in hospitals, using ambulances as troop carriers is QUITE different. Those are the "underhanded" actions complained about.
While guerilla tactics do negate much of the American advantage, I believe you'll find most American military members will have grudging respect for a well executed guerilla action. However, shooting at US troops from within a crowd of school children is the sort of action that engenders contempt.
It is one thing to use your resources effectively to negate another forces advantages. It is quite different to put your own civilian population in danger.
Likely, Intel legal got wind of the non-conforming name, and decided you needed a "proper" name. I worked on a project where each release was named after elements, then Intel legal descended on us, changed all of our names. Arguing over that is what gave me the education in Intel code name policy.
Other times, the project manager got to choose a "custom" name based on one of his/her favorite places to visit.
Like I mentioned, you can submit suggestions to Intel legal. If all goes well, legal will go with your suggestion. But there is no guarantee of that.
I'd also argue that code names do have meaning, at least for the engineers involved with the project. A code name gives a team a rallying point, or a central concept by which we can understand our involvement in the project. Depending on our experiences in that project, whenever we hear or see that name later on in life, we engineers can either feel bursts of pride, or shudders of grief and disgust.
I'll agree that the code names should have meaning. And of course people will attach a meaning to whatever projects they work on. Even more, people should at least like the name of the projects they are working on. But, there are often some real loser names picked out for things. The basic fact is, Intel legal really doesn't care about meaning, or if the name is stupid or not.
BTW - Hi Brad! I used to work with you on "Rainier".
Really? I happen to be currently contracting at Intel.
All Intel code names are names of some geographical place because geographical locations can not be trademarked. There is no inner meaning, that is by design.
Intel legal has to approve every code name before it is used, to make sure code names don't match up with someone's trademarked name. Because the code names are used in trade press to talk about upcoming products, they are subject to trademark law. Because Intel makes lots of money, they are subject to legal colonoscopy.
The official process to name something entails the following actions:
- Open up MapQuest
- Find some geographical names.
- Compile the list of names into an email to Intel legal.
- Pray Intel legal picks one of the names you suggested.
- Name the project whatever Intel legal tells you in the emailed reply. If you're really lucky it will be one you suggested.
Cheers!I used to have terrible handwriting. At one point I decided to fix that, and started printing everything, very slowly. Now I am complimented on my neat penmanship.
I found I need to focus on two things, the first is to slow down enough that I do write well. Second, get all the extra help for pen control you can. There are environmental factors that make handwriting bad, eliminate those.
What I found to work for me is:
As you get better you'll be able to lighten up on the pressure. When you can get neat writing with barely any pressure on the pen then you'll be able to get your speed up. At this time you'll also likely want to change to using a "gel" ink pen. Never go with a liquid ink pen, they'll blot if you move the pen to slow.
You are rather misinformed about the real situation when Novell acquired WordPerfect. I worked for Novell, through 1999 and know many of the people involved with what happened.
First, what most people don't understand is that WordPerfect was broke when Novell acquired them. Novell, had paid the WordPerfect payroll for months before the acquisition. WordPerfect didn't have enough money to pay their employees.
Second, WordPerfect was a massively mismanaged company. The types of excesses (overly expensive offices, outrageous salaries) now associated with the dot com boom, were all done at WordPerfect. Common receptionists were often pulling in over $80K/yr. There were a lot of reasons for this, the founders were genuinely nice guys that wanted to share what the money they made, they wanted to make people happy. However, while the founders were nice, they were not the smart businessmen.
Third, WordPerfect had a technical culture that didn't like software engineering practice. The big wigs at the company believed they knew better than anyone else how to build software and would not listen to advice. I know people that tried to help WordPerfect improve their software engineering practices but were rather rudely rebuffed. As a result software development at WordPerfect was very expensive.
Novell by contrast was a much tighter ship. Ray Noorda was a businessman that knew how to run a company. He was Novell's angel investor that saved them from going out of business when Novell was in a garage. The finances were much better controlled at Novell, software development was better controlled, everything was managed better at Novell.
Ray Noorda is truly a nice guy, he always looked for ways to help people. Noorda described Novells approach to business as "coopertition" you cooperated on standards and technology, while you competed on value. That did a lot to grow the PC networking industry.
The roots of Novell and WordPerfect are pretty deep too. Both companies were started by Brigham Young University (BYU) students, professors or alumni. Both companies were still close to the BYU campus. Both companies predominately employed Mormons (BYU is a Mormon school, and Utah is a Mormon state). Novell and WordPerfect were the predominate employers in the Utah Valley, the only other major employer was a steel factory. The engineers and management at each company knew each other very well, they went to school together, lived close to each other, and went to church together.
Noorda saw WordPerfect as a victim of Microsoft aggression, Noorda also saw that Novell was also on Microsoft's target list. Look at the choices Noorda had. He could watch WordPerfect die, and see thousands of people in his community lose their jobs, watch the Utah economy tank, and then wait for Bill Gates to do the same to Novell. Or he could try to pull things together and fight it. He chose to fight.
The fact is Noorda is a nice guy, and saved WordPerfect and thousands of employees from going out of business. He also realized that no one else was going to stop Microsoft. If he was going to save WordPerfect, and Novell it required fighting Microsoft. Add to that, the fact that Noorda, genuinely despises Bill Gates, then you have a recipe for a real fight.
The biggest failure of Noorda was that he retired. Noorda's successor Bob Frankenberg was the worst thing that ever happened to Novell. Frankenberg took a company that was very nimble and responsive to users and turned the management into a black hole. The number of managers ballooned, the time to make the company budget went from Noorda taking 6 hours at his dining room table to Frankenberg taking 6 months, with tons of employees. Things only changed when Eric Schmidt took over and eliminated about 70% of the management.
When I left Novell, the culture of the engineers was finally starting to recover from the Frankenberg years. I can only hope Novell gets things together again.