Thursday, July 13, 2017

Anti-Company Policies

Or, How To Sabotage Company Meetings And Routines

Greetings:

Now, this is a topic with which we should all be concerned.  It seems that way back in WW II, the forerunner of the CIA published a document for the underground in Nazi-occupied territories on how to upset Nazi war efforts.  Believe it or not, many of these activities are still being carried on today in many companies in the free world by unknowing and well-meaning employees who do not know that they are unknowingly harming rather than helping the company.  Listed below are some of the "suggestion" from that WW II document:

Managers and Supervisors:
  1. Demand written orders for everything
  2. "Misunderstand" orders.  Ask endless questions or engage in long correspondence of such orders.  Quibble over them when you can.
  3. Do everything possible to delay the delivery of orders.  Even though parts of an order may be ready beforehand, don't deliver until it is completely ready.
  4. Don't order new working materials until your present stocks have been virtually exhausted, so that the slightest delay in filling your order will cause a shutdown.
  5. Order high-quality materials that are hard to get.  If you don't get them, argue about it.  Warn that inferior materials will mean inferior products.
  6. In making work assignments, always sign out the unimportant jobs first.  Always see that the important jobs are assigned to the inefficient workers of poor machines.
  7. Insist on perfect work on relatively unimportant products; send back for refinishing those that have the slightest flaw.  Approve others that whose flaws that are not visible to the naked eye.
  8. Make mistakes in routing so that parts and materials are sent to the wrong places in the plant.
  9. When training new workers, give incomplete or misleading instructions.
  10. To lower morale, and with it production, be pleased with inefficient worker; give them undeserved promotions.  Discriminate against efficient workers; complain unjustly against their work.
  11. Hold conferences when there is more critical work to be done.
  12. Multiply paper work in plausible ways.  Start duplicate files.
  13.  Multiply the procedures and clearances involved in issuing instructions, pay checks, andso on. See that three people have to approve everything where one would do.
  14. Apply all regulations to the last letter.
General Interference With Organizations and Conferences
  1.   Insist on doing everything through "channels".  Never permit short-cuts to be taken in order to expedite decisions.' 
  2. Make "speeches."  Talk as frequently as possible and at great length.  Illustrate your points by long anecdotes and accounts of personal experiences.  Never hesitate to make a few appropriate "patriotic" comments.
  3.  When possible refer all matters to committees for "further study and consideration."  Attempt to make the committees as large as possible - never less than five.
  4.  Bring up irrelevant issues as frequently as possible.
  5. Haggle over precise wordings of communications, minutes and resolutions.
  6. Refer back to matters decided upon at the last meetings and attempt to re-open the question of the advisability of that decision.
  7.  Advocate "caution".  Be unreasonable and urge your fellow-conferees to be "reasonable" and avoide haste which might result in embarrassments or difficulties later on
  8. Be worried about the propriety of any decision.  Raise the question of whether such action as is contemplated is within the jurisdiction of the group and whether it might conflict with the policy of some higher echelon.
In light of full disclosure, the original idea for this was taken from the blog of a friend of mine BUT he made the mistake of disclosing the location of the original document which, unfortunately, also gave many, many idea for sabotaging railway lines, bus lines, undergrounds, power plants, natural gas plants, bomb plants, ammunition plants, etc.  I think that ISIS has enough ideas of their own and that they don't need any more from us.  Anyway, this is supposed to be humorous and not REAL ideas for sabotage. 

Bottom line:  Do you know anyone like this?  (We used to call such folks "anal-retentive".)  Have you seen this kind of behavior in any of your meeting or office procedures?  If so, try to pass this around and discourage it.  Immediately.  It might just possibly make for better office and/or meeting behaviour.  Bon Chance!

jco

Tuesday, July 11, 2017

Real Programmers

Greetings:

For those who regularly visit my almost hidden-from-view postings, I thought that we might revisit Bernstein's now-famous (infamous) take-off from "Real Men Don't Eat Quiche" book.  


REAL PROGRAMMERS DON'T EAT QUICHE

Real programmers don't eat quiche. They like Twinkies, Coke, and palate-scorching Szechwan food.

Real programmers don't write application programs. They program right down to the base-metal. Application programming is for dullards who can't do systems programming.

Real programmers don't write specs. Users should be grateful for whatever they get; they are lucky to get programs at all.

Real programmers don't comment their code. If it was hard to write, it should be even harder to understand and modify.

Real programmers don't document. Documentation is for simpletons who can't read listing or the object code from the dump.

Real programmers don't draw flowcharts. Flowcharts are, after all, the illiterate's form of documentation. Cavemen drew flowcharts; look how much good it did them.

Real programmers don't read manuals. Reliance on a reference is the hallmark of the novice and the coward.

Real programmers don't write in RPG. RPG is for the gum-chewing dimwits who maintain ancient payroll programs.

Real programmers don't write in COBOL. COBOL is for COmmon Business Oriented Laymen who can run neither a business nor a real program.

Real programmers don't write in FORTRAN. FORTRAN is for wimp engineers who wear white socks. They get excited over the finite state analysis and nuclear reactor simulation.

Real programmers don't write in PL/I. PL/I is for insecure anal retentives who can't choose between COBOL and FORTRAN.

Real programmers don't write in BASIC. Actually, no programmers program in BASIC after reaching puberty.

Real programmers don't write in APL unless the whole program can be written on one line.

Real programmers don't write in LISP. Only sissy programs contain more parentheses than actual code.

Real programmers don't write in PASCAL, ADA, BLISS, or any of those other sissy computer science languages. Strong typing is a crutch for people with weak memories.

Real programmers' programs never work right the first time. But if you throw them on the machine they can be patched into working order in a few 30 hour debugging sessions.

Real programmers don't work 9 to 5. If any real programmers are around at 9 A.M., it is because they were up all night. 

Real programmers don't play tennis or any other sport which requires a change of clothes. Mountain climbing is OK, and real programmers wear climbing boots to work in case a mountain should spring up in the middle of the machine room.

Real programmers disdain structured programming. Structured programming is for compulsive neurotics who were prematurely toilet trained. They wear neckties and carefully line up sharp pencils on an otherwise clear desk.

Real programmers don't like the team programming concept. Unless, of course, they are the chief programmer.

Real programmers never write memos on paper. They send memos via mail.

Real programmers have no use for managers. Managers are a necessary evil. They exist only to deal with personnel bozos, bean counters, senior planners and other mental midgets.

Real programmers scorn floating point arithmetic. The decimal point was invented for pansy bedwetters who are unable to think big.

Real programmers don't believe in schedules. Planners make schedules. Managers firm up schedules. Frightened coders strive to meet schedules. Real programmers ignore schedules.



Real programmers don't bring brown-bag lunches. If the vending machine sells it, they eat it. If the vending machine doesn't sell it, they don't eat it. Vending machines don't sell quiche. 

I added the emphasis but thanks to http://www.bernstein-plus-sons.com/RPDEQ.html for the "real deal" quote.  Loved it.

Ya'akov