(Vendor and Software/Hardware Producers Guide)
This paper is the result of much research among the wretched rank and file of T/S users, to discover the things that irk, confuse and disappoint them most about the products they buy for their computers. It is hoped that this paper will provide new insight into the ways and means of reducing your business’s profit, thereby enhancing its value as a tax writeoff.
Of course, a measure of caution should be used in applying the principles and measures described herein, lest you go out of business entirely, leaving the field open to those few miserable vendors who insist on providing user-friendly goods, services and support.
Closed Architecture
A closed mind is a great aid to designing closed architecture into your software and/or hardware and documentation.
The basic idea here is to PREVENT the user from using your product in any other way than the narrow and limited way in which you designed it to be used. Closed architecture also helps to keep your product incompatible with other products. This ensures that your product will have a narrow, limited market and a brief life.
Software
DO NOT provide a return to BASIC from MC.
DO NOT make source code available.
DO NOT answer any questions about your software.
Ideally the user should be kept totally in the dark about what he has bought from you, so that the product cannot possibly be modified or improved or put to other uses. The mere existence of such improvments would surely increase the marketability of your product, which is to be avoided at all costs.
The “BREAK” problem, or what your software should do when the user attempts to use the “BREAK” key: There are only three possibilities, listed in order of preference.
1: CRASH. This teaches the users a good lesson, and prevents them from ever buying your products again. Clearly the best.
2. Print the words “Naughty, Naughty, Naughty” on the screen in big flashing letters. This tells the users you are NOT to be trifled with, and impresses them with your software know-how. The danger with this choice is the semblance of HUMOR, a definite no-no. Crashing is better.
3. Simply ignore the user. This has the advantage of being mildly infuriating or boring. At least, it does prevent the more ignorant users from fiddling with your software or adapting it to work with their own brand of mass-storage device, thereby forcing them to stick with cassette, which is maddeningly slow and unpredictable. (That is to say, ideal.)
Hardware
DO NOT provide schematics. These would be an open invitation to the user to improve your product, fix it if it breaks, or put it to (shudder) OTHER USES!
DO grind the part numbers off as many parts as possible, and paint the rest purple.
(An aside: I simply cannot understand why automobile manufacturers do not weld the hoods shut. The fools provide schematics, parts lists and all sorts of information in something they call “shop manuals,” which they will even sell to USERS!! Worse, their user-documentation provided with the car is often large, informative and LEGIBLE! No wonder they are showing a profit!
What do you do if a user calls you up and tells you about a “wonderful” new use he has found for your product? Here there is only ONE choice: scream at him in a childish fit of range, and slam the receiver down. This will surely end the user’s enthusiasm for “new uses.” Furthermore, news of your response wiil spread far and wide, providing the best kind of adverse publicity: word of mouth.
If you have been so wise as to provide such a response, DO NOT weaken or call the user back to apologise. This would UNDO all your good work, and would surely once again encourage enthusiasm.
Documentation
This should be as small, illegible and unhelpful as possible. Be stern, give dire warnings and be intimidating.
Speling and grammar errorrs seem to be much in vogue as a way of unfavorably impressing user’s. However, our research indicates that most users do not even notice such things, so that they are not worth the effort.
Try your best to make the documentation uncopyable. Blue ink on black paper is very, very good. (Same applies to Basic programs.) Remember that IF the users can copy your documentation, they are likely to pass out copies to interested parties at meetings, who are then likely to be impressed and send you unwanted ORDERS!
DO NOT release your software without a good number of problems or deficiencies. DO NOT mention them in the documentation, despite your natural tendency to do so. There are many users who for some reason are FAVORABLY impressed by honesty.
The general rules for documentation are the same as those for dealing with users in person or on the phone: scrupulously AVOID forthrightness, sincerity, humor and humanity. Always remember that “shared laughter” and “good vibes” are treacherous to your bad-business goals, and will ultimately cause you big problems with the IRS owing to drastically increased income.