-
Software development cycle
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. Repeat three times steps 3 and 4.
6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
7. Users find 137 new bugs.
8. Original programmer, having cashed his royalty check, is nowhere to be found.
9. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
10. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
12. New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
13. Programmer produces code he believes is bug-free.
-
Girlfriend 1.0 software
Last year, my friend upgraded his GirlFriend 3.1 to GirlFriendPlus1.0 (marketing name: Fiancee1.0).
Recently he upgraded Fiancee1.0 to Wife1.0, and it's a memory hogger! It has taken all his space; and Wife1.0 must be running before he can do anything. Although he didn't ask for them, Wife1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw. These too slow down the system and cause a slow drain on the resources and well-being of the computer.
Some features I'd like to see in the upcoming GirlFriend4.0:
1. A "Don't remind me again" button.
2. Minimize button.
3. Shutdown feature - An install shield feature so that Girlfriend4.0 can be completely uninstalled if so desired (so you don't lose cache and other objects).
I tried running Girlfriend 2.0 with Girlfriend 1.0 still installed; they tried using the same I/O port and conflicted. Then I tried to uninstall Girlfriend 1.0, but it didn't have an uninstall program. I tried to uninstall it by hand, but it put files in my system directory.
Another thing that sucks--in all versions of Girlfriend that I've used is that it is totally "object orientated" and only supports hardware with gold plated contacts.
Bug warning
Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.
-
Hacker syndrome
by Tad Deriso
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.
-
How to shoot yourself in the foot
Which language is right for you?
Assembler: You shoot yourself in the foot.
Ada: The Department of Defense shoots you in the foot after offering you a blindfold and a last cigarrette.
BASIC (interpreted): You shoot yourself in the foot with a water pistol until your leg is waterlogged and rots off.
BASIC (compiled): You shoot yourself in the foot with a BB using a SCUD missile launcher.
C++: You create a dozen instances of yourself and shoot them all in the foot. Not knowing which feet are virtual, medical care is impossible.
COBOL: USE HANDGUN.COLT(45), AIM AT LEG.FOOT, THEN WITH ARM.HAND.FINGER ON HANDGUN.COLT(TRIGGER) PREFORM SQUEEZE, RETURN HANDGUN.COLT TO HIP.HOLSTER.
cah: After searching the manual until your foot falls asleep, you shoot the computer and switch to C.
dBASE: You buy a gun. Bullets are only available from another company and are promised to work so you buy them. Then you find out that the next version of the gun is the one that is scheduled to shoot bullets.
Fortran: You shoot yourself in each toe, interactively, until you run out of toes. You shoot the sixth bullet anyway, since no exception-processing was anticipated.
Modula-2: You perform a shooting on what might currently be a foot with what might currently be a bullet shot by what might currently be a gun.
Pascal: Same as Modula-2, except the bullet is not of the right type for the gun and your hand is blown off.
PL/1: After consuming all system resources, including bullets, the data processing department doubles its size, acquires two new mainframes, and drops the original on your foot.
Smalltalk, Actor, etc: After playing with the graphics for three weeks, the programming manager shoots you in the head.
Snobol: Grab your foot with your hand and rewrite your hand to be a bullet.
-
Twas the night before crisis
Twas the night before crisis,
And all through the house,
Not a program was working,
Not even a browse.
Programmers were wrung out,
Too mindless to care,
Knowing chances of cutover
Hadn't a prayer.
The users were nestled
All snug in their beds,
While visions of inquiries
Danced in their heads.
When out in the lobby
There arose such a clatter,
That I sprang from my tube
To see what was the matter.
And what to my wondering
Eyes should appear,
But a Super Programmer,
Oblivious to fear.
More rapid than eagles,
His programs they came
And he whistled and shouted
And called them by name.
On Update! On Add!
On Inquiry! On Delete!
On Batch Jobs! On Closing!
On Functions Complete!
His eyes were glazed over,
His fingers were lean,
From weekends and nights
Spent in front of a screen.
A wink of his eye,
And a twist of his head,
Soon gave me to know
I had nothing to dread.
He spoke not a word,
But went straight to his work,
Turning specs into code,
Then he turned with a jerk.
And laying his fingers
Upon the ENTER key,
The system came up,
And worked perfectly!
The updates updated;
The deletes they deleted;
The inquiries inquired;
And the closing completed.
He tested each whistle,
He tested each bell,
With nary an abend,
And all had gone well.
The system was finished,
The tests were concluded,
The client's last changes
Were even included!
And the client exclaimed,
With a snarl and a taunt,
"It's just what I asked for,
But it's not what I want!"
-
Emacs acronyms
EMACS: Escape-Meta-Alt-Control-Shift
EMACS: Eight Megabytes And Constantly Swapping
EMACS: Even a Master of Arts Comes Simpler
EMACS: Emacs Manuals Are Cryptic and Surreal
EMACS: Energetic Merchants Always Cultivate Sales
EMACS: Each Manual's Audience is Completely Stupified
EMACS: Emacs Means A Crappy Screen
EMACS: Eventually Munches All Computer Storage
EMACS: Even My Aunt Crashes the System
EMACS: Eradication of Memory Accomplished with Complete Simplicity
EMACS: Elsewhere Maybe Alternative Civilizations Survive
EMACS: Egregious Managers Actively Court Stallman
EMACS: Esoteric Malleability Always Considered Silly
EMACS: Emacs Manuals Always Cause Senility
EMACS: Easily Maintained with the Assistance of Chemical Solutions
EMACS: Edwardian Manifestation of All Colonial Sins
EMACS: Extended Macros Are Considered Superfluous
EMACS: Every Mode Accelerates Creation of Software
EMACS: Elsewhere Maybe All Commands are Simple
EMACS: Emacs May Allow Customised Screwups
EMACS: Excellent Manuals Are Clearly Suppressed
EMACS: Emetic Macros Assault Core and Segmentation
EMACS: Embarrassed Manual-Writer Accused of Communist Subversion
EMACS: Extensibility and Modifiability Aggravate Confirmed Simpletons
EMACS: Emacs May Annihilate Command Structures
EMACS: Easily Mangles, Aborts, Crashes and Stupifies
EMACS: Extraneous Macros And Commands Stink
EMACS: Exceptionally Mediocre Algorithm for Computer Scientists
EMACS: EMACS Makes no Allowances Considering its Stiff price
EMACS: Equine Mammals Are Considerably Smaller
EMACS: Embarrassingly Mundane Advertising Cuts Sales
EMACS: Every Moron Assumes CCA is Superior
EMACS: Exceptionally Mediocre Autocratic Control System
EMACS: EMACS May Alienate Clients and Supporters
EMACS: Excavating Mayan Architecture Comes Simpler
EMACS: Erasing Minds Allows Complete Submission
EMACS: Emacs Makers Are Crazy Sickos
EMACS: Eenie-Meenie-Miney-Mo- Macros Are Completely Slow
EMACS: Experience the Mildest Ad Campaign ever Seen
EMACS: Emacs Makefiles Annihilate C- Shells
EMACS: Eradication of Memory Accomplished with Complete Simplicity
EMACS: Emetic Macros Assault Core and Segmentation
EMACS: Epileptic MLisp Aggravates Compiler Seizures
EMACS: Evenings, Mornings, And a Couple of Saturdays
EMACS: Emacs Makes All Computing Simple
EMACS: Emacs Masquerades As Comfortable Shell
EMACS: Emacs: My Alternative Computer Story
EMACS: Emacs Made Almost Completely Screwed
EMACS: Each Mail A Continued Surprise
EMACS: Every Mode Acknowledges Customized Strokes
EMACS: Eating Memory And Cycle-Sucking
EMACS: Everyday Material Almost Compiled Successfully
EMACS: Elvis Masterminds All Computer Software
EMACS: Emacs Makes A Computer Slow
-
Possible IBM acronyms
IBM: It's Being Mended
IBM: Inmense Ball of Muck
IBM: I Believe in Memorex
IBM: It's Better than Macintosh!
IBM: Idiots Built Me
IBM: Intense Bowel Movement
IBM: Inferior But Marketable?
IBM: I've Been Mislead
IBM: It's Better Manually
IBM: Infinitly Better Macintosh
IBM: Indefinitly Boggled Machine
IBM: I Bought a Mac
IBM: I Blame Microsoft.
IBM: I Bought Macintosh
IBM: I'll Buy Macintosh
IBM: I've Been Moved
IBM: I've Been Mugged
IBM: Incontinent Bowel Movement
IBM: Identical Blue Men
IBM: Idiotic Bit Masher
IBM: Idiots Become Managers
IBM: Incompatible Business Machines
IBM: Incredibly Boring Machine
IBM: Infernal Bloody Monopoly
IBM: Institute of Black Magic
IBM: Internal Beaurocratic Mess
IBM: International Brotherhood of Magicians
IBM: Intolerant of Beards and Mustaches
IBM: It'll Be Messy
IBM: It's Backwards, Man
IBM: Itty Bitty Machines
IBM: Itty Bitty Morons
IBM: It Barely Moves
IBM: I Buy Mainframes
IBM compatible - IBM contemptible
-
Computer help stories
This article is from the Wall Street Journal, Tuesday, March 1, 1994: Befuddled PC Users Flood Help Llines, and No Qquestion Seems To Be Too Basic
AUSTIN, Texas - The exasperated help-line caller said she couldn't get her new Dell computer to turn on. Jay Ablinger, a Dell Computer Corp. technician, made sure the computer was plugged in and then asked the woman what happened when she pushed the power button.
"I've pushed and pushed on this foot pedal and nothing happens," the woman replied. "Foot pedal?" the technician asked. "Yes," the woman said, "this little white foot pedal with the on switch." The "foot pedal," it turned out, was the computer's mouse, a hand-operated device that helps to control the computer's operation.
Personal-computer makers are discovering that it's still a low-tech world out there. While they are finally having great success selling PCs to households, they now have to deal with people to whom monitors and disk drives are as foreign as another language.
"It is rather mystifying to get this nice, beautiful machine and not know anything about it," says Ed Shuler, a technician who helps field consumer calls at Dell's headquarters here. "It's going into unfamiliar territory," adds Gus Kolias, vice president of customer service and training for Compaq Computer Corp. "People are looking for a comfort level."
Only two years ago, most calls to PC help lines came from techies needing help on complex problems. But now, with computer sales to homes exploding as new "multimedia" functions gain mass appeal, PC makers say that as many as 70% of their calls come from rank novices. Partly because of the volume of calls, some computer companies have started charging help-line users.
The questions are often so basic that they could have been answered by opening the manual that comes with every machine. One woman called Dell's toll-free line to ask how to install batteries in her laptop. When told that the directions were on the first page of the manual, says Steve Smith, Dell director of technical support, the woman replied angrily, "I just paid $2,000 for this stupid thing, and I'm not going to read a book."
Indeed, it seems that these buyers rarely refer to a manual when a phone is at hand. "If there is a book and a phone and they're side-by-side, the phone wins time after time," says Craig McQuilkin manager of service marketing for AST Research, Inc. in Irvine, Calif. "It's a phenomenon of people wanting to talk to people.
And do they ever. Compaq's help center in Houston, Texas, is inundated by some 8,000 consumer calls a day, with inquiries like this one related by technician John Wolf: "A frustrated customer called, who said her brand new Contura would not work. She said she had unpacked the unit, plugged it in, opened it up and sat there for 20 minutes waiting for something to happen. When asked what happened when she pressed the power switch, she asked, "What power switch?
Seemingly simple computer features baffle some users. So many people have called to ask where the "any" key is when "Press Any Key" flashes on the screen that Compaq is considering changing the command to "Press Return Key.
Some people can't figure out the mouse. Tamra Eagle, and AST technical support supervisor, says one customer complained that her mouse was hard to control with the "dust cover" on. The cover turned out to be the plastic bag the mouse was packaged in. Dell technician Wayne Zieschan says one of his customers held the mouse and pointed it at the screen, all the while clicking madly. The customer got no response because the mouse works only if it's moved over a flat surface.
Disk drives are another bugaboo. Compaq technician Brent Sullivan says a customer was having trouble reading word-processing files from his old diskettes. After troubleshooting for magnets and heat failed to diagnose the problem, Mr. Sullivan asked what else was being done with the diskette. The customer's response: "I put a label on the diskette and rolled it into the typewriter."
At AST, another customer dutifully complied with a technician's request that she send in a copy of a defective floppy disk. A letter from the customer arrived a few days later, along with a Xerox copy of the floppy. And at Dell, a technician advised his customer to put his troubled floppy back in the drive and "close the door." Asking the technician to "hold on," the customer put the phone down and was heard walking over to shut the door to his room. The technician meant the door to his floppy drive.
The software inside the computer can be equally befuddling. A Dell customer called to say he couldn't get his computer to fax anything. After 40 minutes of troubleshooting, the technician discovered the man was trying to fax a piece of paper by holding it in front of the monitor screen and hitting the "send" key.
Another Dell customer needed help setting up a new program, so Dell technician Gary Rock referred him to the local Egghead. "Yeah, I got me a couple friends," the customer replied. When told Egghead was software store, the man said, "Oh! I thought you meant for me to find couple of geeks.
Not realizing how fragile computers can be, some people end up damaging parts beyond repair. A Dell customer called to complain that his keyboard no longer worked. He had cleaned it, he said, filling up his tub with soap and water and soaking his keyboard for a day, and the removing all the keys and washing them individually.
Computers make some people paranoid. A Dell technician, Morgan Vergaran says he once calmed a man who became enraged because, "his computer has told him he was bad and an invalid." Mr. Vergara patiently explained that the computer's "bad command" and "invalid" responses shouldn't be taken personally.
These days PC-help technicians increasingly find themselves taking on the role of amateur psychologists. Mr. Shuler, the dell technician who once worked as a psychiatric nurse, says he defused a potential domestic fight by soothingly talking a man through a computer problem after the man had screamed threats at his wife and children in the background
There are also the lonely hearts who seek out human contact, even if it happens to be a computer techie. One man from New Hampshire calls Dell every time he experiences a life crisis. He gets a technician to walk him through some contrived problem with his computer, apparently feeling uplifted by the process.
"A lot of people want reassurance," says Mr. Shuler.
-
Architect programmer
If architects had to work like programmers . . .
Dear Mr. Architect,
Please design and build me a house. I am not quite sure of what I need, so you should use your discretion.
My house should have between two and forty-five bedrooms. Just make sure the plans are such that the bedrooms can be easily added or deleted. When you bring the blueprints to me, I will make the final decision of what I want. Also, bring me the cost breakdown for each configuration so that I can arbitrarily pick one.
Keep in mind that the house I ultimately choose must cost less than the one I am currently living in. Make sure, however, that you correct all the deficiencies that exist in my current house (the floor of my kitchen vibrates when I walk across it, and the walls don't have nearly enough insulation in them).
As you design, also keep in mind that I want to keep yearly maintenance costs as low as possible. This should mean the incorporation of extra-cost features like aluminum, vinyl, or composite siding. (If you choose not to specify aluminum, be prepared to explain your decision in detail.)
Please take care that modern design practices and the latest materials are used in construction of the house, as I want it to be a showplace for the most up-to-date ideas and methods. Be alerted, however, that kitchen should be designed to accommodate, among other things, my 1952 Gibson refrigerator.
To insure that you are building the correct house for our entire family, make that you contact each of our children, and also our in-laws. My mother-in-law will have very strong feelings about how the house should be designed, since she visits us at least once a year. Make sure that you weigh all of thses options carefully and come to the right decision. I, however, retain the right to overrule any choices that you make.
Please don't bother me with small details right now. Your job is to develop the overall plans for the house: get the big picture. At this time, for example, it is not appropriate to be choosing the color of the carpet. However, keep in mind that my wife likes blue.
Also, do not worry at this time about acquiring the resources to build the house itself. Your first priority is to develop detailed plans and specifications. Once I approve these plans, however, I would expect the house to be under roof within 48 hours.
While you are designing this house specifically for me, keep in mind that sooner or later I will have to sell it to someone else. It therefore should have appeal to a wide variety of potential buyers. Please make sure before you finalize the plans that there is a consensus of the population in my area that they like the features this house has.
I advise you to run up and look at my neighbor's house he constructed last year. We like it a great deal. It has many features that we would also like in our new home, particularily the 75-foot swimming pool. With careful engineering, I believe that you can design this into our new house without impacting the final cost.
Please prepare a complete set of blueprints. It is not necessary at this time to do the real design, since they will be used only for construction bids. Be advised, however, that you will be held accountable for any increase of construction costs as a result of later design changes.
You must be thrilled to be working on as an interesting project as this! To be able to use the latest techniques and materials and to be given such freedom in your designs is something that can't happen very often. Contact me as soon as possible with your complete ideas and plans.
PS: My wife has just told me that she disagrees with many of the instructions I've given you in this letter. As architect, it is your responsibility to resolve these differences. I have tried in the past and have been unable to accomplish this. If you can't handle this responsibility, I will have to find another architect.
PPS: Perhaps what I need is not a house at all, but a travel trailer. Please advise me as soon as possible if this is the case.
-
New Microsoft Windows advertising slogans
At the time of writing, Microsoft's slogan for Windows 95 was "Where do you want to go today?" These are some alternative and probably more truthful ad slogans for use with Windows.
1. Microsoft gives you Windows - OS/2 give you the whole house.
2. A computer without Windows is like a fish without a bicycle.
3. Windows and DOS: A turtle and its shell.
4. Bang on the left side of your computer to restart Windows.
5. Windows: The colorful clown suit for DOS.
6. Error #152 - Windows not found: (C)heer (P)arty (D)ance.
7. Windows 3.1: The best $89 solitaire game you can buy.
8. Windows NT: Insert wallet into Drive A: and press any key to empty.
9. I'll never forget the first time I ran Windows, but I'm trying.
10. I still miss Windows, but my aim is getting better
11. My lastest screen-saver: Curtains for Windows.
12. Double your drive space: Delete Windows!
13. OS/2. Opens up Windows, shuts up Gates.
14. Out of disk space. Delete Windows? [Y]es [A]solutely [O]f Course!
15. How do you want to crash today?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks