And, like I said, this is not an isolated incident. I don't know if this particular problem has ever happened to anyone else, but I have experienced similar issues that have affected others in addition to myself. This sort of thing happens regularly. No one is at all surprised by it. There are multiple processes that are deeply broken with no possibility of fixing them.
Here is another example: the design group I work with has been assigned a shared storage area of 100GB -- and no, that is not a typo: one hundred gigabytes shared across a dozen engineers. And we do chip design, so we generate lots of data. Needless to say, that shared storage is always very nearly full, and we get regular emails nagging us to delete stuff that we no longer need. So we have a dozen engineers spending time triaging their data in order to save a few dollars on storage costs. Yes, it is every bit as insane as it sounds. I once tried to point out that this is insane, with the result being that I was admonished for being a troublemaker. So now I don't bother any more.
So there is no doubt in my mind that at least some of Intel's troubles are entirely of their own making, and I'm in a position to know.
I remember a late 90's labs with that type of storage.
Any chances you somehow posted this from your Sun Machine?
Now if that's what you want, godspeed. But you're perfectly identifiable to anyone managing insider threats at INTC; you're strongly advised to delete everything you posted under this account.
You run the risk of impacting not just yourself but the contractor you work for, and depending on how crucial this business is to the contractor, the outcome could be a years-long pain in the neck.