Backup - What you do when you sight a skunk in the woods.

Bar code - Them’s the fight’n rules down da local tavern.

Bug - The reason you is a giv’n for calling in sick.

Byte - What yer pit bull dun to cusin Jethro.

Cache - Needed when you go to da store.

Chip - Yer cusin’s uncle’s mother’s boyfriend’s name.

Terminal - Time to call da undertaker.

Crash - When you go to Junior’s party uninvited.

Digital - The art of counting on your fingers.

Diskette - A female Disco dancer.

Hacker - Uncle Leroy after thirty years of smoking.

Hardcopy - Picture looked at when selecting tattoos.

Internet - Where cafeteria workers put their hair.

Keyboard - Where you hang the keys to the John Deere.

Mac - Big Bob’s favorite fast food.

Megahertz - How your head feels after seventeen beers.

Modem - What ya did when the grass and weeds got too tall.

Mouse pad - Where Mickey and Minnie live.

Network - Scoop’n up a big fish before it breaks the line.

Online - Where to stay when taking the sobriety test.

Rom - Where the pope lives.

Screen - Helps keep the skeeters off the porch.

Serial port - A red wine you drink with breakfast.

Superconductor - Amtrak’s Employee of the year.

Scsi - What you call your week-old underwear.

Webster’s Dictionary definition of Windows 95

Windows95: n.

32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can’t stand 1 bit of competition.

Real software engineers eat quiche.

Real software engineers don’t read dumps. They never generate them, and on the rare occasions that they come across them, they are vaguely amused.

Real software engineers don’t comment their code. The identifiers are so mnemonic they don’t have to.

Real software engineers don’t write applications programs, they implement algorithms. If someone has an application that the algorithm might help with, that’s nice. Don’t ask them to write the user interface, though.

If it doesn’t have recursive function calls, real software engineers don’t program in it.

Real software engineers don’t program in assembler. They become queasy at the very thought.

Real software engineers don’t debug programs, they verify correctness. This process doesn’t necessarily involve executing anything on a computer, except perhaps a Correctness Verification Aid package.

Real software engineers like C’s structured constructs, but they are suspicious of it because they have heard that it lets you get “close to the machine.”

Real software engineers play tennis. In general, they don’t like any sport that involves getting hot and sweaty and gross when out of range of a shower. (Thus mountain climbing is Right Out.) They will occasionally wear their tennis togs to work, but only on very sunny days.

Real software engineers admire PASCAL for its discipline and Spartan purity, but they find it difficult to actually program in. They don’t tell this to their friends, because they are afraid it means that they are somehow Unworthy.

Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.

Real software engineers write in languages that have not actually been implemented for any machine, and for which only the formal spec (in BNF) is available. This keeps them from having to take any machine dependencies into account. Machine dependencies make real software engineers very uneasy.

Real software engineers don’t write in ADA, because the standards bodies have not quite decided on a formal spec yet.

Real software engineers like writing their own compilers, preferably in PROLOG (they also like writing them in unimplemented languages, but it turns out to be difficult to actually RUN these).

Real software engineers regret the existence of COBOL, FORTRAN and BASIC. PL/I is getting there, but it is not nearly disciplined enough; far too much built in function.

Real software engineers aren’t too happy about the existence of users, either. Users always seem to have the wrong idea about what the implementation and verification of algorithms is all about.

Real software engineers don’t like the idea of some inexplicable and greasy hardware several aisles away that may stop working at any moment. They have a great distrust of hardware people, and wish that systems could be virtual at ALL levels. They would like personal computers (you know no one’s going to trip over something and kill your DFA in mid-transit), except that they need 8 megabytes to run their Correctness Verification Aid packages.

Real software engineers think better while playing WFF ‘N’ PROOF.

The Life Cycle of Software

1. Programmer produces code he believes is bug-free.
2. Product is tested. 20 bugs are found.
3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
4. Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
5. See 3.
6. See 4.
7. See 5.
8. See 6.
9. See 7.
10. See 8.
11. Due to marketing pressure and an extremely pre-mature product announcement based on over-optimistic programming schedule, the product is released.
12. Users find 137 new bugs.
13. Original programmer, having cashed his royalty check, is nowhere to be found.
14. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
15. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
16. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
17. New CEO is brought in by board of directors. He hires programmer to redo program from scratch.
18. Programmer produces code he believes is bug-free.
19. See step 2

LETTERS TO THE EDITOR (The Times of London)

Dear Sir,

I am firmly opposed to the spread of microchips either to the home or to the office, We have more than enough of them foisted upon us in public places. They are a disgusting Americanism, and can only result in the farmers being forced to grow smaller potatoes, which in turn will cause massive unemployment in the already severely depressed agricultural industry.

There is some compelling force in all Hackers that seems to draw them to their computers every day. Why they get up at 4am to use the modem, and why they continue to rack up a truly incredible phone bill is beyond me.

Most computer areas, at your home or at your office, tend to be messy. Even you try to keep it clean, it is truly impossible. Whether it be empty Coke cans laying all around, soldering devices, electric diodes, computer parts, or integrated circuits, it is not only a pain for your mother to look at, but a prime Russian ICBM missile target as well.

There is much detail needed to explain a Hacker. For instance, instead of organizing his clothes by color, best ones, or style, he organizes his by pile. Also, he likes to sing songs such as, “Let’s get Digital”, “We all live in a yellow subroutine”, and “Somewhere over the RAMbow”.

Most Hackers do well in school. The reason is not to impress their teachers, not to get money from their parents, and not to be educated, but they do it so they can hopefully get a scholarship to MIT. You can’t blame them, though, if they are looking out into space. It might be because they are worried if MCI traced the calls that they sent to NORAD.

All Hackers, big or small, love computers, whether they be Trash-80’s or an IBM 360/VM workstation. When they get on one, it’s mighty hard to get them off of it.

There are 2 types of Hackers. One who likes to crash local BBS’s, and the one who writes programs in Assembly Language. The Hacker who crashes systems is the one that most people think that a Hacker is. A typical example of one is John Fredrickson (A.K.A. “The Phone Man”). He loves to crash computers, and break into illegal systems. The ones that he has gotten in to are MCI, CitiBank, school systems, IBM, Southern Bell, and Georgia Tech, not to mention all the ones in between.

The second type of Hacker is the programmer. He writes games, utilities, and anything else that he can think of. Take for example, John Harris, a freelance software writer for On-Line Software Co. John had a brainstorm one day, and decided to write Frogger for the Apple. He thought that it would take about 3 weeks to complete. He started on Frogger a week late, because of the complicated music set that he had to write. After two months, he was almost done. He decided to take a break and go to the Software Expo. He decided to take his nearly completed Frogger, and show it to the consumers at the show. He also took with him the only back-up copy, in case the main disk did not boot.

While at the fair, he was talking to the Manager about getting a booth. He had his disks with him. Then, when he got a booth reserved, he reached down to get his disks, and they were gone! All his hard work, including the MultiLevel character generator, music lines, disk subroutines, assembly routines, debugging programs, etc. All gone.

After that tragedy, John was in a deep depression. He finally started working on it again in 3 months. He completed it in 4 months and 3 days.

Part Two:

Hackers always take time off. There is always one way to notice a true Hacker. At a party, the true Hacker is the one in the corner talking about operating system security and how to get around it. At the beach, the True Hacker is the one drawing flow charts in the sand. At a football game, the true Hacker is the one comparing the football plays against a simulation printed on 11 by 14 fanfold paper.

Most Hackers work for the U.S. Government– mainly the Department of Defense. You can see the best Hackers at the Jet Propulsion Laboratory in California.

What sort of environment does a Hacker function best in? No, not a heated room with a clean table and disks organized neatly, but they do best in rooms that have line-printed Snoopy calendars from the year 1969. They do not know how to cook, so they survive on Twinkies and coffee. Instead of wasting electricity for a heater, they spend it on air-conditioners to cool of their computer system in mid-January when the temperatures are below freezing. They wear layers and layers of clothing to keep the body heat in. When you see one of these people, instead of a Hacker coming into your mind, you think that he is about to go on a Polar expedition somewhere in the North Pole.

Hackers also like to hang around arcades. (This is also true for kids, little old ladies, and fighter pilots.) There, secluded in their

own environment, Hackers can talk freely on computer hints and short cuts while playing Pac-Man, or Joust.

All Hackers like Graphics. They like low-resolution, but prefer high-resolution the best. These graphics, such as Sine waves, rotating 3-D boxes, and little balloons, are confined to the limits of a systems capability. The older more experienced Hackers are the ones who are lucky enough to get to work on a VAX system, and maybe even a CRAY-1 SuperComputer. If they use these, they have only the limits of their imagination to stop them.

Most Middle School Hackers between the ages of 10 through 14, like to use computers to do reports on, and play games. Some of these younger generation Hackers have gotten into BASIC programming.

Some people, like to impress real Hackers by making them think that they know everything. There is a name for this kind of person. He is a Sub-Hacker (Intillectuous dumbfoundeth). For instance, you come up to them one day, and say,”Hey so-and-so what does BASIC stand for?” and you could sit there for days, and he would act like the answer was on the tip of his tongue, when it was probably in his toes. It is people like this that give Hackers a bad name.

Part Three:

All Hackers have rules that they go by. One is to never call long distance on Monday, because of the high phone charge. If builders built buildings they way programmers wrote programs, the first woodpecker that comes along would destroy civilization. Another is, if the computer accepts a program on the first run without any errors, either there is a malfunction, or it must be a dream.

Hackers are a unique breed. Combining intelligence, personality, and a morale sense of good taste. A Hacker enjoys the environment that appeals to him the most. Such as, the computer room, the arcade, science lab, or the Atari downstairs. They like to be alone. Secluded in their own thoughts, thinking of what the password could be to log on to General Electric. Hackers are the people who are going to make our future brighter, and more exciting in the field of electronics, data processing, artificial intelligence, and programming. We need to support these people in all the ways that we can, so we will be insured of a more happier future in the world of technological advancements.

10. It doesn’t take minutes to build the picture when you change TV channels.

9. When was the last time you tuned in to “Melrose Place” and got a “Error 404″ message?

8. There are fewer grating color schemes on TV–even on MTV.

7. The family never argues over which Web site to visit this evening.

6. A remote control has fewer buttons than a keyboard.

5. Even the worst TV shows never excuse themselves with an “Under Construction” sign.

4. Seinfeld never slows down when a lot of people tune in.

3. You just can’t find those cool Health Rider infomercials on the Web.

2. Set-top boxes don’t beep and whine when you hook up to HBO.

1. You can’t surf the Web from a couch with a beer in one hand and Doritos in the other.

10. New seats would require everyone to have the same body size.

9. We’d all have to switch to Microsoft Gas.

8. The U.S. government would get subsidies from an automaker–a first.

7. The oil, alternator, gas, and engine warning lights would be replaced by a single “General Car Fault” warning light.

6. Sun Motorsystems would make a car that was solar-powered, twice as reliable, five times as fast, but ran on only 5% of the roads.

5. You would be constantly pressured to upgrade your car.

4. You could have only one person in the car at a time, unless you bought Car 95 or CarNT - but then you would have to buy more seats.

3. Occasionally your car would die for no apparent reason and you would have to restart it. Strangely, you would just accept this as normal.

2. Every time the lines on the road were repainted, you’d have to buy a new car.

1. People would get excited about the new features of Microsoft cars, forgetting that the same features had been available from other carmakers for years.

The Ultimate Computer stood at the end of the Ultimate Computer Company’s production line. At which point the guided tour eventually arrived. The salesman stepped forward to give his prepared demo.

“This”, he said, “is the Ultimate Computer. It will give an intelligent answer to any question you may care to ask it.”

At which a Clever Dick stepped forward — there is always one — and spoke into the Ultimate Computer’s microphone.

“Where is my father”?, he asked.

There was a whirring of wheels and flashing of lights that the manufacturers always use to impress lay people, and then a little card popped out.

On it were printed the words, “Fishing off Florida.”

Clever Dick laughed.

“Actually,” he said, “my father is dead”!

It had been a tricky question!!

The salesman, carefully chosen for his ability to think fast on his feet, immediately replied that he was sorry the answer was unsatisfactory, but as computers were precise, perhaps he might care to rephrase his question and try again?

Clever Dick thought, went to the Ultimate Computer and this time said, “Where is my mother’s husband”?

Again there was a whirring of wheels and a flashing of lights.

And again a little card popped out. Printed on it were the words, “Dead. But your father is still fishing off Florida.”

There was a pilot flying a small single engine charter plane, with a couple of very important executives on board. He was coming into Seattle airport through thick fog with less than 10m visibility when his instruments went out. So he began circling around looking for landmark.

After an hour or so, he starts running pretty low on fuel and the passengers are getting very nervous. Finally, a small opening in the fog appears and he sees a tall building with one guy working alone on the fifth floor.

The pilot banks the plane around, rolls down the window and shouts to the guy “Hey, where am I? To this, the solitary office worker replies “You’re in a plane.” The pilot rolls up the window, executes a 275 degree turn and proceeds to execute a perfect blind landing on the runway of the airport 5 miles away. Just as the plane stops, so does the engine as the fuel has run out.

The passengers are amazed and one asks how he did it. “Simple” replies the pilot, “I asked the guy in that building a simple question. The answer he gave me was 100 percent correct but absolutely useless, therefore that must be Microsoft’s support office and from there the airport is just a while away.”