3 ms·
140 pages on coding style. This looks straight out of the CIA handbook for sabotage [1]. I am sure China or Russia have a version of that. > (12) Multiply pape
by cm2187 10mo ago
140 pages on coding style. This looks straight out of the CIA handbook for sabotage [1]. I am sure China or Russia have a version of that.
> (12) Multiply paper work in plausible ways. Start duplicate files.
> (13) Multiply the procedures and clearances involved in issuing instructions, pay checks, and so on. See that three people have to approve everything where one would do..
> (14) Apply all regulations to the last letter.
[1] https://www.cia.gov/static/5c875f3ec660e092cf893f60b4a288df/SimpleSabotage.pdf https://www.cia.gov/static/5c875f3ec660e092cf893f60b4a288df/...
- conception 10mo agoAlso see corporate grift.
- eastbound 10mo agoFunnily enough, when I look at my codebase, I often think about this handbook. I try intendedly to ascribe it to incompetence but I always have a doubt. If I only listen to my inner voice, I’d fire everyone all the time.
- chrisfosterelli 10mo agoWhat's the right amount of standards to have when you're writing 9 million lines of code that controls a 30,000lb machine moving through the sky at mach 1 with a human life inside?
- cm2187 10mo agoIt is whatever they used for ALIS [1] [1] https://en.wikipedia.org/wiki/Lockheed_Martin_F-35_Lightning_II#Maintenance_and_logistics https://en.wikipedia.org/wiki/Lockheed_Martin_F-35_Lightning...
- JohnBooty 10mo agoI'm confused by the responses to this document, as if developers were expected to memorize it or consult it after every line of code. The obvious expectation here is that these rules would be incorporated into some kind of automated linting tool. I really need to get the fuck out of this industry.