Final Thoughts in Three Parts, Crossposted from Intel Internal Blogs

Things that were not explained adequately upon conversion from CW to ICE.

1. Bonuses- it was thought by my management that QPB applied to all blue badge employees including ICE. If I had known I wasn't going to get bonuses, I would have asked for higher base pay.
2. Vacation Time- MUST be taken while still an employee, and unlike what the recruiter who wrote my job offer told me, cannot be used to extend your final week. Any unused vacation time will be lost at end of contract, by policy. In addition, apparently you lose it at the end of the year, I really should have taken WW52 off, then the sting would not be so bad now.
3. ICE as a stepping stone to full employment at Intel is a lie. I couldn't get anybody, despite spending many hours on networking, to give my resume a second look. I even learned a new tool in this contract that is internal and can only be used at Intel and is completely worthless outside of Intel. No matter, I've had many interviews outside of Intel, and will land well, but I'll keep this in mind the next time I am tempted to take a short term contract at Intel.
4. Being a blue badge, if you are ICE, still means you're treated more like a resource than like a human by human resources. Many policies are used to reverse decisions that your manager, who is working more closely with you, has made.
   

Software Project Management At Intel in non-software divisions

1. Brooks Law is almost unheard of at Intel. Hardware Managers think that all software projects can be completed in less than six months, and therefore throw contingent workers at the project. Since software estimates, in general, are 75% engineering and 25% new science, they are wildly inaccurate. When the project inevitably fails to be complete in the first six months, the temptation is to break Brook's Law by adding more contingent workers. The time to ramp up CWs on the project of course exceeds the time to complete the project if you kept software engineers working for more than 18 months at a time.
2. Agile or Waterfall- Pick one and stick to it. This crazy combination used on software projects in hardware divisions is ridiculous, as is the general lack of written requirements.
3. It's hard to hit a moving target- input data integrity must be respected. If you don't have input data integrity, then there will be bugs. Bugs add complexity. Bugs make software estimates inaccurate. Lather, rinse, repeat.

On the new diversity initiative

1. There is no link between surface appearance and how a person thinks, or how capable they are. None at all. While this makes the apparent racism of the past a mistake, this also makes modern affirmative action programs equally racist and invalid.
2. There is no link between religion, sexual orientation, or disability and how a person thinks, or how capable they are. Such factors should not enter into hiring or promotion decisions at all, and when they do, that is what Intel needs to eliminate from the system.
3. There IS a link between certain forms of mental illness and the ability to innovate. Since mental illness affects the brain directly, having somebody with a well controlled mental illness on your team increases diversity of thought, which leads to innovation.
4. I believe that the uncertainty surrounding the diversity initiative was a part of my failure to convert to FTE. Not necessarily outright discrimination against a white male, and due to my autism I fall into one of the protected groups anyway and HR is well aware of that. But I believe the way the diversity initiative was announced, and the weeks of confusion surrounding it before BK finally clarified his position, coming at the same time I was trying to convert to FTE, meant that I had a harder time of trying to get my resume noticed and find open, externally advertised jobs for my skillset.

Final Thought and contact info

While my search to convert to FTE at Intel has failed, my external search has succeeded. I have at least one, maybe two job offers in hand; I will likely be back to work sometime between March 25 to March 30. This posting will be crossposted to Inside Blue before I leave Intel. Comments section below is open.