There is no excuse to not have any documentation. One must always make an attempt to write a reasonable amount of documentation so there isn't a situation where there is no hope to understand anything except read all the source code.
But a lot of people (managerial types especially) expect docs will be "step 1 look here, step 2 look there, step 3 fix with this exact command"
Docs should explain how a system works, and perhaps some important places to look, but it's not a checklist to fix all problems. The consumer must still possess the ability, and will, to investigate and fix problems using their own critical thinking.
For anyone else out there who may be a chess imbecile like myself... it took me a while to figure out why black king doesn't take white rook:
It's because if they do, white has no legal moves, but king isn't in check. This condition, where a player can't move, but the king currently isn't in check, results in a stalemate (which is considered a draw).
Therefore, white's baiting of black into that position by sacrificing pieces is interesting.
I agree. There was a report in December that they had lost $800 million in the previous quarter. It seems like utter insanity that:
1. They'd even bat an eyelash at paying retail for the needed quantity, and
2. They'd think it's even remotely ok to exclude a section of the team completely due to any reason (sex, race, size, whatever)
Yes, it's just a jacket, but this definitely smells of a deep seeded cultural problem due to how ludicrous it is.
Not really fair to blame the plane in that case.