• don't write specs. Users should consider themselves lucky to get any programs at all and take what they get.
• don't comment their code. If it was hard to write, it should be hard to read.
• don't write application programs, they pro- gram right down on the bare metal. Application programming is for feebs who can't do systems programming.
• don't eat quiche. Real programmers don't even know how to spell quiche. They eat Twinkies, Coke and palate-scorching Szechwan food.
• don't draw flowcharts. Flowcharts are, after all, the illiterate's form of documentation. Cavemen drew flowcharts; look how much it did for them.
• don't read manuals. Reliance on a reference is a hallmark of the novice and the coward.
• programs never work right the first time. But if you throw them on the machine they can be patched into working in only a few 30-hours debugging sessions.
• don't use Fortran. Fortran is for wimpy engineers who wear white socks, pipe stress freaks, and crystallography weenies. They get excited over finite state analysis and nuclear reactor simulation.
• don't use COBOL. COBOL is for wimpy application programmers.
• never work 9 to 5. If any real programmers are around at 9 am, it's because they were up all night.
• don't write in BASIC. Actually, no programmers write in BASIC, after the age of 12.
• don't document. Documentation is for simps who can't read the listings or the object deck.
• don't write in Pascal, or Bliss, or Ada, or any of those pinko computer science languages. Strong typing is for people with weak memories.
• know better than the users what they need.
• think structured programming is a communist plot.
• don't use schedules. Schedules are for manager's toadies. Real programmers like to keep their manager in suspense.
• think better when playing adventure.
• don't use PL/I. PL/I is for insecure momma's boys who can't choose between COBOL and Fortran.
• don't use APL, unless the whole program can be written on one line.
• don't use LISP. Only effeminate programmers use more parentheses than actual code.
• disdain structured programming. Structured programming is for compulsive, prematurely toilet-trained neurotics who wear neckties and carefully line up sharpened pencils on an otherwise uncluttered desk.
• don't like the team programming concept. Unless, of course, they are the Chief Programmer.
• have no use for managers. Managers are a necessary evil. Managers are for dealing with personnel bozos, bean counters, senior planners and other mental defectives.
• scorn floating point arithmetic. The decimal point was invented for pansy bedwetters who are unable to 'think big.'
• don't drive clapped-out Mavericks. They prefer BMWs, Lincolns or pick-up trucks with floor shifts. Fast motorcycles are highly regarded.
• don't believe in schedules. Planners make up schedules. Managers 'firm up' schedules. Frightened coders strive to meet schedules. Real programmers ignore schedules.
• like vending machine popcorn. Coders pop it in the microwave oven. Real programmers use the heat given off by the cpu. They can tell what job is running just by listening to the rate of popping.
• know every nuance of every instruction and use them all in every real program. Puppy architects won't allow execute instructions to address another execute as the target instruction. Real programmers despise such petty restrictions.
• don't bring brown bag lunches to work. 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.

• No curriculum there for information technology > ETH Mathe/Physik > Pascal (Mathem. Algorithmen) > Speicherung Lochkarten
• Firma  (Cobol) PDP11
• …

“Man misst sich mit dem, der den Schutz gemacht hat. Es ist im Prinzip ein Wettkampf. Darum strahlt es einen gewissen Reiz aus. Es ist eine Sucht”.

Hcc, Rudolf Stramm, Min 15:09, in: (Schlumpf/Trinkler 1989)

1. Program/file name: Ideally, all uppercase and followed by one space. Carriage returns are ignored in this file.
2. Version number: In the format "v1.123", followed by a space.
3. ASP number: Only if an actual ASP member, otherwise ignored.
4. Description separator: A single short hyphen "-".
5. Description: The description of the file. The first two lines should be the short summary, as older boards cut off the rest. Anything beyond that should be extended description, for up to eight lines, the official cut-off size. Additional text could be included beyond that but might not be included by the board.