[JohnLocke4]

It is often that seemingly irrelevant factors play a big role. In this case, a 141 page highly dense (and frankly boring to read) document is in its essence a liability. Engineers get bored too and it is obviously more fun to just code rather than to read a document that might aswell have been written by a lawyer.

This is also why car makers name their cars things like "Jeep Expedition" or "Ford Escape". The name doesn't change the car, but it does make it more exciting.

[JohnBooty]

    In this case, a 141 page highly dense (and frankly 
    boring to read) document is in its essence a liability

So, do you think that the intent was for developers to memorize this document?

Or do you think the expectation was something more reasonable, like using this document as a tool to configure linting tools so that developers could get realtime feedback as they code?

[JohnLocke4]

No, that is not what I mean. The efficiency of a piece of knowledge is not only a function of its intrinsic value, but also how easy it is to understand. Sure, the people who are expected to read the document are smart and this is probably the best way to do it, but even Lockheed engineers are fallible.

If anything, the enemy will be defeated before they have had the time to understand the document in case it gets leaked xD