The Silicon Jungle by David H. Rothman

Chapter 12, “How I Found ‘God’ on MCI (and a Few Other Odds and Ends

4588 words  |  Chapter 3

about Electronic Mail),” tells more about sending computer messages over the phone lines. Some E-mail nets even link up with the old Telex networks. During the writing of this book I corresponded via computer with people ranging from William F. Buckley, Jr., to Captain Zap and the MCI mail-Telex connection transmitted last-minute changes to my publisher. In Chapter 13, “Net Gain$,” you’ll learn how different computers in your own office can share the same programs and exchange information without people constantly having to carry floppy disks from one desk to another. A Michigan company may be enjoying as much as DLR $1,000 a year more in effective work time from each staffer as a result of its internal computer net. Of course, with today’s imperfect technology, such hookups can be a real struggle. But so often they’re worth it. You could say the same, indeed, of micros in general—today and in the future. It seemed especially true when, for my last chapter, I tried to reach Arthur Clarke’s micro in Sri Lanka. I wanted him to answer questions about microcomputers in 2001—the year in which his Hal was killing humans. Did our phone-computer connection succeed? Read Chapter 14, “As the Jungle Thickens.” Struggles notwithstanding, computers often _do_ pay for harried professionals and business people. “This $5,000 machine has saved me from hiring a $20,000-a-year assistant,” said a New York investment adviser using an IBM PC to write reports and make financial calculations at home. A young trader forsook the bedlam at the New York Cotton Exchange for an electronic office in his apartment. Now he can go to work in his bathrobe and delay his shower until lunchtime. “It’s more challenging this way,” he said. “More contemplation, less raw instinct.”[5] Footnote 5: The examples of the investment adviser and cotton trader come from _New York_ magazine. Another self-employed man, Jimmy Carter, composed his memoirs on a word processor—perhaps inspired by the example of a former Carter speech writer who wrote a well-reviewed book on national defense. Then there’s Isaac Asimov, the legendary science-fiction novelist, who, even with an ancient manual, could write faster than the old Teletype machines could clatter along. But he didn’t always produce the neatest copy. “How different now!” he exulted in an article. “Staring at a page of type on a television screen, I eagerly look for typos so I can have the fun of changing them.” You needn’t be a professional author, however, to benefit from computerized writing. In Maryland, an architect-consultant, once typewriter shy, is now churning out reports several hundred pages long on his IBM PC. “A boon to the small businessman” is how Hugh Hunt, a son of the late oilman H. L. Hunt, described micros. “Now he can compete with the larger corporations as far as obtaining data and processing it quickly.” Hunt himself was using portable computers in his land-development business. But he also noted their helpfulness in law: “Computers are one of the ways that small attorneys can compete with large corporations. By joining a computer bank, they can research briefs and do word processing, just as the large companies can.” Many Americans apparently shared his views. In 1985, they might buy six million computers for business use, and within two more years, that number might almost double.[6] While I was writing this book, the United States was emerging from the worst economic ordeals since the Great Depression; a few college graduates had been reduced to shopping-bag ladies, but the microcomputer business was still growing, even if at a reduced rate. You might wait three months or more for your Macintosh or IBM. Some companies died, but others took their places; and even in times of inflation most prices on micros were dropping; years would pass before scientists could no longer keep dramatically increasing the silicon chips’ powers. Forget about the physical smallness of the chips. It was as if the entrepreneurs in Silicon Valley—in exploiting the scientists’ advances—were opening up a vast electronic territory. “The only thing you worry about with computers,” Hunt said, pleased, “is ‘Should I wait until something better comes along?’” Footnote 6: The estimates of the number of business computer buyers come from the Yankee Group’s Chris Christiansen. “I’m sort of a computer groupie,” said Art Buchwald, the syndicated humor columnist. He was caught up in the new pornography of the era: those luscious, ad-packed micro magazines crammed with the vital statistics of IBMs and Apples. “It used to be that when _Playboy_ arrived at the house, my wife would say, ‘Your _Playboy_’s here,’” Buchwald told an advertising magazine. “Now she says, ‘Your _InfoWorld_’s here.’ I’m not sure which she prefers. I have a feeling that _Playboy_, at least, she could discuss with me.” It was like radio during the 1920s, this micro craze. _Time_ had proclaimed the computer “Machine of the Year” in 1982, and I recalled a song that a friend of my parents, an old woman, had written years ago. “Marconi, Marconi,” the lyrics went, “the world is at your feet.” How long until the novelty of microcomputers seems just as quaint as that of radio? The parallels could be there. Two San Francisco-area authors, Andrew Fluegelman and Jeremy Joan Hewes, in _Writing in the Computer Age_, urged readers to “become full-fledged computer citizens—as writers, poets, artists, musicians, programmers, number-crunchers, networkers....” The Fluegelman-Hewes book was useful and well done. But “computer citizens”? The phrase grated. I was a user at the keyboard, a “citizen” in the voting booth. Still, I could understand why Fluegelman and Hewes called themselves “computer evangelists.” I felt the same way. After having brought us Muzak and junk food, technology for once was making life better. I say this with reservations. Educators correctly warned of the computer literacy gap between Harlem and Scarsdale—of the dearth of machines in the slums and the bounty in some suburbs. Rich and poor clashed at school-board meetings. In my own county, Fairfax County, Virginia, a well-off PTA reportedly saved up for micros, then withheld purchases until it learned whether the school board would spend tax money helping other schools catch up. And what about unemployment as automation cost more jobs? Or U.S. firms using computer-satellite hookups to pipe in the work of $3-an-hour clerks? The People’s Republic of China was even preparing to sell programming skills to the rest of the world. A billion _programmers_, maybe? So much for high tech as a refuge for the American jobless. How could you make computerization a joy to all? That was one answer you’d never find in a computer store. You could, however, set up the right retraining program for valued employees to see them through automation. You could fight the Hal Syndrome. You could work to end boring tasks. In short, you could do your best to make your computers benefit both your employees and your company’s earnings. 2 ❑ The Kaypro Phenomenon: How Solana Beach Took on Silicon Valley As _The Silicon Jungle_ was lighting up my Kaypro screen one September day in 1983, several similar machines were whirring and clicking in the Washington offices of Walter Mondale’s presidential campaign. Kaypros kept track of donations and the $18-million budget. They helped churn out news releases, speeches, and letters to voters in important primary states. Just eighty people worked at headquarters seven months into the campaign; Kaypros and other affordable micros were a major reason why Mondale wouldn’t need legions of back-room staffers in Washington later on. I didn’t know if Mondale would win or lose the primary, but whatever happened, it wouldn’t be for want of computing power. Forty-five miles away, near Baltimore, Kaypros at a Westinghouse plant were receiving computer messages from defense installations abroad. Other Kaypros sat on the desks of William F. Buckley, Jr., ex-Governor Jerry Brown’s research director, and the president of Tootsie Rolls; and still another, some months earlier, had helped study Barney Clark, the first man with an artificial heart. A Kaypro in the Midwest was tracking something else, the milk and manure output of cows. All of us, Mondale’s people, the others, and I, had benefited from the struggle between Adam Osborne and Andy Kay. Osborne, a brash ex-columnist for computer magazines, had marketed the first mass-produced portable computer. Andy Kay had soon followed with the Kaypro. Adam Osborne was a dark-haired, mustached man in his forties who enjoyed toting his product within sight of photographers. His father, a British missionary of unconventional stripe, had tried to convert Christians to Hinduism. Nor did the younger Osborne himself blend into the crowd; he founded his computer company in 1981 and was soon comparing himself to Henry Ford and the Osborne 1 to the Model T. “I give you,” he said, “ninety percent of what most people need.” His rival, Kay, was shorter, about five feet seven inches, but also slim; like Osborne, he had studied chemical engineering and was a maverick and newcomer in the personal-computer business. There, however, the resemblances ended. Kay was soft-spoken, graying, an old electronics hand; his friends depicted him as a quality-obsessed engineer and Osborne as a flashy marketing man. They said Osborne had seemed technically incapable of making a good portable with a nine-inch screen. Adam Osborne, in turn, spoke of Kay’s computer as if he were a four-hundred-pound wrestler forecasting an instant demise for a foe: “The Kaypro’s gonna die.”[7] Footnote 7: “Gonna die” is from _Popular Computing_. The Osborne statements come from oft-repeated statements to newspapers or from magazines. “Mr. Osborne,” an aide said when I revealed that this chapter was on Brand X, “does not want to discuss the Kaypro.” Andy Kay himself did not speak to me in a normal interview. His literary agent-friend, William Gladstone, feared that it might conflict with a project of their own, and Gladstone sought to deny me ownership of quoted material. Normally I would have told him to stuff it, but I needed the right quotes to tell the full story of _my_ computer. So Gladstone and I worked out a compromise. After I sent thousands of words of questions via my Kaypro over the phone lines, he obtained Kay’s replies on tape. I submitted follow-up queries when Kay’s answers did not satisfy me. Gladstone insisted on reading this chapter for accuracy but never tried to censor me; in fact, he was helpful and pleasant to deal with. He even brought this manuscript to the attention of a publisher he knew (although I placed it through my agents). Gladstone’s help, incidentally, didn’t influence my perception of the Kaypro II as better than the archrival Osborne. I bought a Kaypro at a time when “William Gladstone” was nothing more to me than the name of a nineteenth-century English statesman; I _already_ loved the company’s product. Just the same, determined not to write an extended press release, I’ve consulted with the corporation’s critics, and I have run this chapter past a _San Diego Union_ reporter named Dan Berger, who exposed some of Kaypro’s less admirable management practices. I’m as grateful to Dan as to Bill. The computer magazines had portrayed Osborne as a lone maverick taking on the Silicon Valley establishment with the portable that the rest of the industry said couldn’t be built. But Kay claimed a similar idea had hit him at the same time. Andy Kay had seen his son-in-law struggling to carry an Apple and its trimmings between home and office and decided that a market might exist for a small machine for engineers, architects, and other professionals. _Then_, Kay said, he had heard of the Osborne. Modifying their original plans somewhat, his people at Non-Linear Systems had homed in on their rival’s weaknesses, giving their own computer a better screen and a better keyboard and the ability to store more data. Adam Osborne had struck back with a jazzed-up version of his first machine. By 1983, many other companies were in the fray, including Seequa Computer Corporation, a Maryland manufacturer whose computer sold for less than $2,000 and ran most IBM-style programs. In mid-1983 an industry expert was saying Kay and Osborne might together enjoy $200 million a year in micro sales at the retail level. That was just a fraction of the $5-billion-a-year market for business micros, but the two firms then seemed the largest makers of portables in the $1,000-$2,000 range.[8] Their fight was pivotal. Lines were fuzzing between economy business computers and the home machines; the winner of the portable battle might go on to fight Apple and IBM, provided it survived the onslaught of $1,000 computers that Japan was expected to unleash. By the end of the decade, powerful portables with a quarter the bulk of the Kaypro II might jam the shelves of the discount stores. Footnote 8: The $200-million and $5-billion estimates came to me from Chris Christiansen of the Yankee Group, who said the latter figure might be very conservative. _InfoWorld_ quoted another research firm, InfoCorp, as saying that 527,000 portable computers were sold in 1982—and that 5.1 million would be sold by 1987. Kay waged his marketing war from several hillside buildings in Solana Beach, a small town near San Diego, hundreds of miles south of Osborne and the rest of Silicon Valley. His was a family business. Kay’s personal housekeeper served salads and fruit juice in the corporate lunch room, and his eighty-six-year-old father, known around the plant as “Grandpa,” repaired electronic equipment and ran a forklift. Andy Kay’s wife was secretary of the company. One son, David, was the vice-president for marketing and had helped develop the Kaypro; a second son worked in personnel, and a third ran the print shop; and Andy Kay’s daughter and her husband had designed the buildings—which were now the same light blue as the “KAYPRO II” lettering on the computer. Altogether, some 450 people worked for Kay’s company by mid-1983. That was more than twice the number a year earlier when the Kaypro II was just hitting the market and Kay was counting on a mere $10 million in sales. Bulldozers were growling away amid the expansion, and the company newspaper said equipment-cluttered grounds resembled a scene from a bad disaster movie. No longer was Kay a semiobscure maker of voltmeters and oscilloscopes and other test equipment. Sales, once $4 or $5 million annually, were barreling along toward $100 million. Even his company name soon changed—from Non-Linear Systems to Kaypro—in recognition of the success of the division making his hot new computer. Wall Street and Andy Kay were getting to know each other. That summer four million shares of common stock hit the market at $10 each; and the prospectus said Arthur B. Laffer, the “Laffer Curve” economist, would serve on the board of directors. Kay still owned most of the company personally. And now, with the new money, he could give IBM and Apple a better fight. “After 30 years in business,” _San Diego Magazine_ had said, “he’s suddenly the new kid on the block, clutching under his arms a couple of excellent bags of marbles.”[9] Footnote 9: The _San Diego Magazine_ article appeared in May 1983. Before the Kaypro, Kay hadn’t exactly been on the verge of starvation—he owned an art-filled home overlooking the Pacific and gave to the local symphony and other cultural causes—but now he’d reached the point where his admirers were depicting him as a silicon-age Horatio Alger character. That’s a little exaggerated. Kay, though poor in his New Jersey days, was never an orphaned newsboy toughing it alone. “Grandpa” prodded Andy. Frank Kopischiansky—an Eastern European immigrant and an ex-coal miner—worked in silk mills and wool factories and as a chauffeur. Frank had come to the United States from what is now Poland. Andy Kopischiansky would later become Andy Kay after his original name baffled some colleagues at work and they kept calling him “Kay” for short. The Kopischiansky home lacked a bathtub. “But,” Andy recalled, “we always had food, and I always had a nickel in my pocket.” Frank enjoyed fixing broken-down cars and tinkering with electrical equipment, and Andy himself built a shortwave radio when he was only twelve years old. Math was another love. Andy even considered a career as an actuary after Prudential Life told him he could eventually make $15,000 a year. “I flipped out,” Andy said, “because it was a lot of money in 1935.” Frank shrugged off the $15,000, however. “That’s not very much,” he said. The words, incredibly, came from a man who seldom made more than $1,000 a year during Andy’s youth and who sometimes earned just $15 a week. Andy, growing up in Clifton, New Jersey, took it for granted he could never afford college, but then the letters M.I.T. came up in a drafting class. “What’s that?” Andy asked. “I’ve never heard of the place.” Frank had lost most of his savings in a bank crash, but his wife somehow scraped up enough money to help Andy reach M.I.T. on a partial scholarship. Andy graduated in 1940 with a bachelors degree in chemical engineering, mathematics, and premedicine and worked for the Bendix Corporation and several other companies before founding Non-Linear Systems in 1953. Kay reached California through a job, although for years he’d been hoping to enjoy the warm climate there. He started his company in Solana Beach rather than Silicon Valley because he was already working in the area. Osborne himself would found his own firm while living in Berkeley—he’d locate it in Hayward, a medium-sized city within twenty miles of the Valley proper, the Palo Alto-San Jose area southeast of San Francisco. For Non-Linear Systems Kay developed the world’s first commercially successful digital voltmeter. It was the result of some memories from World War II, when unskilled workers were constantly damaging voltmeters and having trouble reading them accurately. Kay’s new machine easily survived the careless. The instrument displayed numbers and didn’t require workers to make a reading off the thin needle of a conventional meter adjusted for the right voltage. “I don’t look at myself particularly as an inventor,” Kay said. “I’m a solver of problems. There are inventors who have many, many more ideas than I get.” Instead, he tried to refine ideas in “ways that make sense from an industrial-engineering standpoint and a customer standpoint.” Kay’s digital voltmeter was perfect for the military and for the National Aeronautics and Space Administration (NASA) and their contractors; unskilled people could help test thousands of voltages on American missiles. “The silos are full of our instruments,” he said. But the NASA cutbacks of the Nixon era hit Non-Linear Systems hard. “The seven vice-presidents went,” recalled a trade publication, “as did their white Cadillacs.” Frank Kopischiansky was willing to help see Non-Linear Systems through bad times, loaning thousands of dollars of painfully saved money. But that was hardly enough to sustain a corporation. What about the future? How to avoid the boom-and-bust cycle of government spending? Kay decided to carve out a niche as a maker of rugged portable test gear for private industry. He wanted to offer many of the same wrinkles found in costly, bench-bound equipment, and one of those features was a microprocessor in a voltmeter: a miniature electronic brain that would make it easier to use. The idea came from an old friend, Bill McDonald, whom Kay had met decades earlier at M.I.T. Their gym lockers were next to each other’s there; both men had loved handball and hated team sports. McDonald, a husky man of basketball-player height, had worked for Non-Linear Systems in the early 1950s, then had returned East, where he had acquired a computer background. Then, in the late 1970s, he’d rejoined Non-Linear Systems, where his friend Kay hoped he would help develop a computer. Correctly or not, Kay believed that “ninety percent of the electronics business was computer and ten percent was test equipment, hi-fi, stereo, and stuff like that.” Non-Linear Systems had offered other companies’ minicomputers in systems it packaged for military contractors, but still wasn’t making machines of its own. Maybe a small business machine would be one way to enter computerdom. “Two months after Bill came to work for me,” Kay recalled, “he showed me some microprocessor-based computers for doing accounts payable-receivable at the local computer dealer’s place. “They were very reasonable, so I bought some and was very intrigued with them. And I wondered: ‘Why not make this stuff? I could make a better disk drive. And look at this: this connector doesn’t work too well.’ And Bill said, ‘We could make them, all right, but I don’t know where you’d sell them.’ This was in late 1979. I said okay and dropped the idea.” Two years later, however, Kay watched his architect son-in-law, Michael Batter, struggling with an Apple and knew the time was ripe for an easier-to-tote portable. Kay tried VisiCalc, the electronic spreadsheet, on the Apple and came away thinking the machine was too complicated, beyond being a hassle to move from home to office. So Kay told Bill McDonald, “Listen, we’re selling instruments to engineers. Let’s make a computer that we can walk in to an engineer and set on his desk and say, ‘Hey, look at this. You can use it.’” Still, Kay worried about the new technology. “It’s a fairly stylized dance,” McDonald reassured him in spring 1981. “You buy the chips, and there is black magic in getting them to work—but not in how they work.” “Okay,” came the reply, “that’s it. We’ll get rid of the disadvantages of the Apple and cram our computer into one box without cables all over the place.” In ads the Apple looked incredibly compact. Actually, though, serious computer users needed disk drives to store large amounts of information for quick retrieval. They also needed a TV-like monitor to see the letters and numbers they typed out on the computer. And Kay wisely wanted everything squeezed into one box. If you bought his machine, you’d get the whole works except perhaps for the printer, which spewed out your calculations or typed up your letter. Also, it would cost you less than a full Apple system. Kay could bring down the cost of a complete machine if he planned on every computer being one. All this was the logical culmination of Kay’s skill in shrinking gear for the military and aerospace industry. For years he had been making printed circuit boards and filling them with components. And he could order the disk drives, keyboards, and other special computer-type parts from outside suppliers. The way Kay tells it, he had no idea—at first—that he was about to take on Adam Osborne. “It was six months,” he said, “before we ever saw Osborne’s literature. He introduced his computer in March 1981, but I didn’t know anything about it.” Some would question that statement, of course, given the novelty of the Osborne 1 and its creator’s flair for publicity. Whatever happened—with Osborne in mind or not—Kay selected the same basic technology and essentially similar parts. A Z80-Style Microprocessor A =microprocessor= is simply the main brains that tie together the memory devices, the keyboard, and other parts of the computer. You can also call it a =central processing unit= (=CPU=). Okay, but why a Z80 in the Kaypro? That’s simply a style of chip from a company called Zilog. “You could buy those all over the place,” Kay said. “We wanted something proven and reliable.” The Z80 was the only kind of CPU that could run =CP/M= (=Control Program for Microcomputers=)-style programs, then an industry standard. The Z80, though, can’t handle programs as complicated as the newer 8088 chip that ended up in IBM PCs and countless clones. Here’s why. A =bit= is a “1” or a “0.” Patterns of bits form =bytes=. And what’s a byte? Nothing more than a letter or number. So how does this tie in with the early Kaypro’s Z80 versus the IBM’s 8088? Well, the Z80 processes information in =words= of only 8 bits at a time. The 8088 in the IBM, however, gulps it down in 16-bit chunks and works with larger memories—so that the IBM can run more complicated programs, like the more elaborate electronic spreadsheets for forecasting profit and loss. There’s another benefit, too. A 16-bitter doesn’t need to call up programming information as often from the spinning floppy disks, which are slower than the purely electronic memories. The Kaypro II, however, won’t _immediately_ become a has-bit—er, has-been. “Converting the Kaypro to a 16-bit machine is no big deal,” Kay observed. In fact, several months after he said it, his company announced a computer called the Kaypro II Plus 88 with both the 8-bit Z80 and the 16-bit 8088. It couldn’t run all IBM programs, especially those boasting =graphics= or pictures as well as words and numbers. Here, as in many cases, the term “IBM compatible” is grossly misleading. There are degrees of compatibility, and even if a computer supposedly uses the same style of floppy disks, you must test it with the program _you_ want to run. (Many computer aficionados test for general IBM compatibility by running a game called Flight Simulator, or Lotus 1-2-3, a program combining a spreadsheet with graphics and several other capabilities.) Some existing programs, by the way, are configured so that it doesn’t matter much whether you’re running the 8- or 16-bit version. That will change as special programs come out for the 16-bit machines and as old ones, like WordStar, begin to take full advantage of 16-bit capabilities. Already Apple and other companies are writing new software for computers like the Macintosh, which, if not universally regarded as a true 32-bit machine, contains chips faster than the IBM’s 8088. For many small businesses, however, 8 bits may be powerful enough even for number crunching as long as the right programs are available. The wisdom in the micro business is that no machine is ever obsolete—just so it does the job for you. 64K Random-Access Memory (RAM) RAM, once the power goes off, will throw out everything you’ve typed. This temporary computer memory, this electronic scratchpad, is like a bright student cramming for a quiz in a useless subject: he’s a quick learner—and a quick forgetter. Don’t confuse RAM with =ROM=, or =read-only memory=. ROMs keep remembering even after the power goes off. But you can’t “write” new material on them; commonly, ROMs store programs used over and over again. What about the RAM, though? How to get around the forgetting? You just transfer the information to floppy disks, which are slower but as stable as a music cassette. Different computers hold different amounts of information in their RAMs. The Kaypro II holds 64K; =K= is normally a scientific abbreviation for 1,000. So 64K stands for a memory capacity of about 64,000 letters or numbers. No, I won’t mess with the technical explanation of why it isn’t exactly 64,000. Okay, but why _64_K? It’s a magic number to the computer. Sixty-four K bytes is the largest memory with which the Z80 and other 8-bit microprocessors can easily communicate without too much technical trickery. Also, you need at least 64K to make good use of some popular software like the WordStar word-processing program. Moreover, the RAM must be roomy enough to handle electronic spreadsheets. Most small businesses will find that the 64K Kaypro can juggle around enough columns and rows on the sheets. But in some cases you _may_ still want a micro with 500K or even 1,000K or more of RAM. To sum things up, that’s because:

Chapters

1. Chapter 1 2. Chapter 7 and Backup VII, you’ll learn (1) the basics, (2) when charts 3. Chapter 12, “How I Found ‘God’ on MCI (and a Few Other Odds and Ends 4. 1. Bigger RAMs can work with more and larger numbers—a handy capability 5. 2. More RAM can accommodate programs more complicated for the computer. 6. 3. You may want the most sophisticated software to thwart computer 7. 1. You can quickly make safety copies of valuable disks—something that’s 8. 2. You can more easily work with long electronic documents. 9. 1. Absence of bugs. The software maker should have gotten all the bugs 10. 2. General ease of use. A program should be easy enough to learn _and_ 11. 3. Good documentation. The manual should be clear and logically 12. 4. Usefulness to beginners and old pros alike. You can adjust the best 13. 5. Speed. It lets you do your job fast, especially when you use it with 14. 6. Power. Related to speed. The program can quickly accomplish 15. 7. Fewer chances for botch-ups. Good programs limit the chances for 16. 8. The Jewish-uncle effect. Ideally, your software will slow you down or 17. 10. After-the-goof feedback. After you’ve botched up—and we all do 18. 11. Ability to customize. You or at least a software expert can 19. 12. Availability of “accessory” programs to make your original software 20. 13. Support. Ideally, the software seller will stand behind his product 21. 1. A =cursor= is just the marker on your screen—a blinking line, 22. 2. A =file= is an electronic version of a letter, report, or other 23. 3. A =control key= is what you start holding down to turn a letter or 24. 4. To =scroll= just means to move from place to place in your 25. 5. A =menu= lists commands on your screen. It can tell you how to 26. 6. A =block move= is the ability to move material from one part of 27. 8. A =search and replace= substitutes one word (or group of words) for 28. 1. When you work for a stuffy old bureaucracy that’s rich and afraid 29. 2. When you’re a procurement officer on probation. As they say, no 30. 3. When you want to dump the training problems in the manufacturer’s 31. 4. When you prefer an extra-large, extra-sharp screen and giant 32. 5. When you’re looking for a machine that will run special software 33. 1. It takes all of two or three minutes—maybe less—to copy a disk 34. 3. Computer users want to befriend others with similar machines so 35. 4. Many software companies overprice their wares. Yes, it’s expensive 36. 5. Some people in large companies think software houses don’t give 37. 6. Many software companies don’t offer enough guidance or other help. 38. 2. A file in a data base is the electronic version of a file drawer or 39. 3. A =field= is a category of fact like the amount of money spent on 40. 4. =Structure= is simply the way a record is set up. There are three big 41. 5. The EDIT command changes the contents of a data field. You can type 42. 6. A command to APPEND can add new records to your electronic filing 43. 7. =Sorting= lets you reshuffle records alphabetically, by date or other 44. 8. The LIST command tells dBASE II to flash across the screen the 45. 9. .AND. helps you narrow down the information you’re looking for or 46. 10. .OR. is another way to describe the desired facts. LIST FOR 47. 11. LIST FOR .NOT. SALE:PERSN = ‘BABBITT’ could help weed from view, or 48. 12. =Command files= are programs that tell the machine how to manipulate 49. 1. A large number of rows and columns. A spreadsheet of 254 rows and 65 50. 2. Speed. “Even with a simple spreadsheet,” says Scharf, “someone might 51. 3. General simplicity and ease of use. In tricky places, does the 52. 4. Range of commands. Most spreadsheets nowadays let you easily move or 53. 5. The ability to do what-if tables. The best spreadsheets won’t just 54. 6. Easy consolidation of figures from different spreadsheets. That’s no 55. 7. =Natural order of recalculation.= Cells must influence the numbers in 56. 8. A useful =macro language=. Macros are combinations of commands that 57. 1. Deciding whether to hire a computer consultant. How much in your time 58. 2. Hiring and using a consultant. It isn’t just a matter of asking, 59. 3. Training employees. Don’t clutter your people’s minds with 60. 4. Working with your company’s data-processing people. Know which 61. 1. The computer company’s FORTRAN, according to Stewart, was as badly 62. 2. FORTRAN wasn’t as good as BASIC for micro data bases that stashed 63. 3. Brown was still basically a mainframer. And micro FORTRAN was 64. 3. “What’s the quality of the work? 65. 1. Who’s teaching? Can he or she communicate well with the students, and 66. 3. Why is the material taught? To make your people computer literate in 67. 4. When do the students learn? On their time or yours? Will you reward 68. 5. Where is the learning happening? Ideally, your students can take the 69. 6. How do the students learn? Through instruction manuals, mainly, or 70. 1. Even the best-intentioned companies may fail miserably in easing some 71. 2. The traits which make somebody valuable to his company _may_ be the 72. 3. At the same time you can’t stereotype anyone—by age, folksiness, or 73. 4. An important part of training is simple salesmanship—persuading the 74. 5. Don’t make computerization seem more threatening than it has to be. 75. 6. As early as possible start people on real projects. The first day at 76. 2. Helped them with some learning aids like color-coded keys showing 77. 3. Motivated them by explaining how their new computer skills would make 78. 1. Before approaching Data Processing, ask who-how questions about the 79. 2. Ask your informal Data-Processing contact about possible technical 80. 3. When you’re ready to deal with the Data-Processing manager, tell 81. 4. Make it clear you’re aware of your project’s complications. 82. 1. =The canary-in-the-mine= theory of labor relations. Ergonomics is 83. 3. =“Terminal” happiness.= Detachable keyboards are just a start, 84. 7. =Air conditioning, heating, and ventilation=—basics neglected by a 85. 8. Honest assurances to your people that you’re exposing them to the 86. 9. A willingness to consider alternatives to the TV-like CRTs that 87. 10. Sensible use of wrinkles like the mouse—the hand-sized gizmo you use 88. 11. A related ingredient, good software—the topic of earlier chapters. 89. 2. How far the keyboard platform protrudes from the platform on which 90. 4. The angle at which the screen faces you. You can swivel away to your 91. 5. The height of your chair. You don’t of course need high-tech 92. 1. Removing half the tubes from existing fluorescent fixtures. You’ll 93. 2. Parabolic fluorescent fixtures with baffles to keep the light out of 94. 3. Parawedge louvers, which, according to Eisen, “have been particularly 95. 4. Desk and floor lamps. You might buy rheostats you can plug in between 96. 5. Indirect lighting. The disadvantage is the expense. You may have to 97. 1. Coatings or etching applied during manufacture of the video displays. 98. 2. Coatings put on after manufacture. Generally, but not always, they 99. 3. “Colored plastic panels and etched faceplates,” which, says Eisen, 100. 4. Micromesh filters, favored by German ergonomists. Eisen says U.S. 101. 5. Polarizing filters. They may reduce brightness and shorten tube life, 102. 1. There is a possibility, extra-slim, but still there, that 103. 2. More minor physical and mental problems from computers definitely do 104. 6. The possibility of a detached retina 105. 3. Guarding your electronic files 106. 1. Burden programmers and others with electronic versions of heavy 107. 2. Keep their computer systems easy to use—and vulnerable. (“Then you’re 108. 3. Compromise. (“You get half raped.”) 109. 1. How hard, exactly, would it be to puzzle out? Just how many 110. 2. How compatible is the program with your computer? If security is so 111. 3. Is the security program easy to use? If it’s too hard, it’ll be 112. 4. Are you certain the program won’t jeopardize the accuracy and 113. 5. Should you expand your system, will the security software be able to 114. 6. Do you want a =public key= encryption system? It works this way. You 115. 7. Will your code be based on the =Data Encryption Standard= (=DES=), 116. 1. See if your disk has a file at least 500 or 600 words long. If so, 117. 3. Erase A. 118. 1. Zealously enforce a no-drinking, no-eating policy around disks, at 119. 2. Remember the Rothman Dirt Domino Theory. Dirt, dust, and grease often 120. 3. Realize that floppies don’t always mix well with office materials 121. 4. Know about other natural enemies of floppies or at least of the data 122. 5. Don’t even let your floppies rest against your computer’s screen, 123. 6. Remember that the more information you can pack on a floppy, the more 124. 7. Clean your disk heads. Don’t use rubbing alcohol. “Try something like 125. 8. Have head alignment checked, to reduce disk errors. With heads out of 126. 9. Buy quality disks. Of course, the more you spend on disks, the more 127. 1. Every five minutes or so, type out the “KS” or an equivalent and dump 128. 2. Every half an hour make a printout of your recent work. With a fast 129. 3. Every day make your backup floppy. You might forget about the scratch 130. 1. Dumping to floppies. It’s cheap but slow. Then again, you can speed 131. 2. Transferring the Winchester’s contents to a special tape drive large 132. 3. Dumping to an ordinary videocassette recorder. Although slow, it’s 133. 1. How much time or money does it take to enter your data or set up your 134. 3. How much time or money do you have for copying, cleaning, 135. 1984. Many more companies might be. They might have kept quiet, however, 136. 1. The cottage keyers are paying more than $2,600 a year to rent their 137. 3. Likewise, the cottage keyers lack the normal fringe benefits. The 138. 4. The keyers may not be sharing the experiment’s rewards fifty-fifty. 139. 1. Ease and speed of use. You needn’t be a computer expert or wrestle 140. 2. Friendliness. A good system isn’t just easy to use; it’s also boy 141. 4. Confidentiality. Clerks aren’t privy to the same information as the 142. 1985. They’d be able to place mutual-fund orders for clients, conduct 143. 1. Lower phone bills. In a Midwestern office of the H. J. Heinz Company, 144. 2. Elimination of telephone tag. “We can type a memo at the end of our 145. 3. An end to garbled messages. Errors and misunderstandings decline when 146. 4. More efficient sharing of ideas. =Computer conferencing= is an 147. 1. How long a Kaypro took to sort dBASE II files electronically while 148. 3. How long a second Kaypro needed to sort the dBASE files in the first 149. 1. How extensive do you want your network’s file-sharing capabilities to 150. 2. Who’ll manage the network? Who’ll determine who can see what 151. 3. Do you want to assign special network-related duties to other people? 152. 4. Who will work at what =node=? That’s jargon for a location or =work 153. 5. Will some people share work stations? If so, you’d better decide 154. 7. How many printers and other gizmos will people share, and where will 155. 8. What kinds of computers are you planning to hook up? The WEB as of 156. chapter 11, but subject to court approval, would be bought by a Swedish 157. 1. If your computer messes up, remember the very last thing you did, 158. 2. See if that isn’t the answer to your problem. 159. 1. Know your prices. Study the want ads of the local papers. There’s 160. 2. Pay attention to the machine’s physical condition. A banged-up 161. 3. Find out how your pet programs run. If you don’t have any available 162. 5. Find out what generation of equipment it is. Does it include all 163. 6. Learn where you stand legally if you’re buying software with the 164. 7. Call up commercial auctioneers and find out if they’re holding any 165. 8. Obviously you’ll want to consider a maintenance agreement with a 166. 1. Another daisy wheel machine. The daisy wheel is plastic or metal and 167. 2. A =laser printer=. Typically, it works a bit like some copying 168. 3. A =thermal-transfer printer=. This uses patterns of heat to arrange 169. 4. An =ink-jet printer=. This kind literally squirts ink against the 170. 1. =Draft quality.= The letters are too dotty for anything but drafts 171. 2. =Correspondence quality.= It’ll do for a letter to a forgiving friend 172. 3. =Near-letter quality.= You can get away with it for book manuscripts, 173. 4. =Letter quality.= That’s typewriter quality. 174. 1. Does the printer offer them no matter what computer or program you 175. 3. For free, will the store modify your computer system to make the 176. 4. Will your desired combinations of features work simultaneously? 177. 2. If not, can the store make one up for you? At what cost? 178. 1. The general logic of the manual. The author should have written it 179. 2. The quality of the index. I’ll charitably assume it’s there to begin 180. 3. Simplicity of vocabulary and sentence structure. A manual shouldn’t 181. 1. The field may only contain certain numbers and/or letters—for 182. 2. The field will _enter itself_ based on your previous entries. For 183. 3. The field can be a constant. For example, if your data record 184. 4. The field can automatically shift cases for you. For example, you 185. 5. The field can insist that whatever you type in is identical two 186. 6. The field can be required—something that you _have_ to enter, or 187. 1. Does the program help you come up with pies, bars, or whatever kind 188. 2. Can it do so as quickly as possible? 189. 3. Does the program fit in well with your other software? 190. 4. How much memory space does the program—and the electronic files of 191. 5. What about the program’s color capabilities—both on screen and on 192. 6. Does the program coexist okay with the printer or plotter you own or 193. 7. How easy is the program to learn? What about the other general traits 194. 1. “Who?” Who from the contracting firm is doing the work? A junior 195. 2. “What?” Describe the task as clearly and precisely as possible. And 196. 3. “When?” Can you negotiate a penalty if the firm misses a deadline? 197. 4. “Where?” Will the consultants do the work in your office? Theirs? On 198. 5. “How much?” Obvious. 199. 1. Thinking small. Don’t bargain over the Who-How simply for the whole 200. 2. Making the consultant give you the source code of the new software. 201. 3. Insisting that any manuals for his software be complete and in plain 202. 4. Bargaining if possible for a software warranty. Then, if you discover 203. 5. Possibly requiring the consultant to give you a discount on 204. 6. Negotiating for full or part ownership of the software he may develop 205. 7. Forbidding the consultant from selling the new software to your 206. 8. Making the consultant pledge that he won’t violate any trade-secret 207. 9. Hammering out a confidentiality agreement, if necessary, to protect 208. 10. Making the consultant agree in writing that he is working as your 209. 11. Trying to write into the contract your right to a full explanation 210. 12. Remembering that there’s only so much protection the law can give, 211. 13. Choosing the right lawyer, if you can afford one, for the contract. 212. 1. Is the convenience worth the extra several hundred dollars you’ll be 213. 3. How do the windows look alongside each other? Do they =overlap=, just 214. 4. How about =data transfer=? If you move information from one 215. 5. What kind of graphics—=bit mapped= or =character based=? The bit 216. 6. Will the window program work with ordinary software or just products 217. 7. Will the windows at least slightly slow down some programs? A word 218. 8. Is the program picky about the computers it’ll work with? A window 219. 9. Does the program require a mouse—the gadget you roll on your disk to 220. 1. Communicate teletype-fashion with the other person. You can keep 221. 2. Call up electronic bulletin-board systems (BBSs) or plug into The 222. 3. Get copies of other programs that altruistic computer buffs have 223. 1. Start out with the other person’s modem set on ORIGINATE and yours on 224. 3. Hit your carriage-return key. 225. 6. Assuming you’re using a manual modem, flick the switch to “data.” 226. 3. Hit your return. 227. 1. From MODEM7’s main menu, you select =T= and again hit the return a 228. 2. Find out if the other person can read words you type. (Don’t worry if 229. 3. Tell him (or her) to set up his computer so that, on paper or on a 230. 4. Once the other person is ready—while you’re still in the =T= mode—hit 231. 5. Now you type =B:[name of file]=. Here and elsewhere don’t type the 232. 6. Next hit your return. The disk should start spinning, and both you 233. 2. Again, select your trusty =T= from the main menu. But don’t hit your 234. 4. Type =B:[the name of the file you’re creating on the data disk to 235. 6. Then hit the letter =Y= with your finger on the control key 236. 8. Then, to preserve the file, “writing” to your disk, you must type out 237. 2. From MODEM7’s main menu, type =S B:[name of the data disk file you 238. 3. Hit the return. 239. 3. Hit your return. 240. 2. Type the word TYPE, then a space, then the name of the file—preceded 241. 3. Then hit your return. 242. 4. Hit your return. 243. 3. Tap =Control-B=. 244. 4. Type the right number (300 for 300 baud, 1200 for 1,200; do not use 245. 5. Hit your return.

Reading Tips

Use arrow keys to navigate

Press 'N' for next chapter

Press 'P' for previous chapter