[Knitebane]

*Chuckle*

Unlike you trend followers, I blazed my own trail by buying a Zenith Z-100 with the Z80 processor, the 8086 card and a whopping 128K of RAM. A year later I bought a 10Mb hard drive for it. I had to pull out one of the two 360K disk drives to make it fit.

It was a big step up from the Heathkit I had.

I remember that the DOS card was all elbows. If you were running in Z80 mode and switched to DOS, you couldn't switch back because DOS would grab all of the low memory space and wouldn't give it back, even if you terminated DOS.

There are a few programs that are still coded as tight as those we typed in or borrowed on cassete tape. Well, they aren't written in assembly, but they're still tight.

Go download a copy of the source for qmail or djbdns. I threw in the programming towel a long time ago, but my small exposure to C is enough to know really good code when I see it.

flamebait

Then again, if he was a real programmer, he'd program in COBOL.

/flamebait

[jae471]

Then again, if he was a real programmer, he'd program in COBOL.

Real Programmers...

• Don't eat quiche. Real programmers don't even know how to spell quiche. They like Twinkies, Coke, and palate-scorching Szechwan food.

• Don't write applications programs. They program right down to the bare metal. Applications programs are for dullards who can't do systems programming.

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

• 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 use COBOL. COBOL is for wimpy applications programmers.

• 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 simulations.

• Don't use LOGO. In fact <no> programmers use LOGO after puberty.

• 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.

• Don't use Pascal, BLISS, ADA, or any of those sissy-pinko computer science languages. Strong typing is a crutch for people with weak memories.

• Never work 9 to 5. If any are around at 9 a.m. it's because they were up all night.

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

• 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. They are for dealing with personnel bozos, bean counters, senior planners, and other mental defectives.

• Don't drive around in clapped out mavericks. They prefer BMW's, Lincolns, or pick-up trucks with floor shifts. Fast motorcycles are highly regarded.

• 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 the corn is 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.

[capt. norm]

"Then again, if he was a real programmer, he'd program in COBOL."

You have given yourself away as one of us "cave men" who used to write COBOL by the mile. A typical program (fan-fold print-out) listing would be as thick as a telephone directory. Fortunately those miles of COBOL compile down to some machine code that the old IBM 'Frames' seemed to love.

And who could forget CPF...my favorite CPF error message. "Error ocurred during file transfer. Approximately 0 files were copied."
And it always was zero files...maybe IBM was being cautious, thinking a few bytes may have slipped through.