Meet tomorrow's venture capitalists

- by Paul Murphy, -

Want to know why most business analysts and venture capitalists simply don't get it with respect to Unix? Take a look at the computer books they study from while working toward their MBA, financial analysis, or accounting designation, and you'll understand that their ignorance isn't entirely their fault.

Each of these professional qualifications is directly or indirectly controlled by some group which sets minimal educational standards, including things like "IT competency maps" - lists of things graduates are supposed to know about IT. Schools work to these standards, thus nearly every curriculum leading to a business designation of some kind features at least one, and usually several, introductory IT courses. This, of course, creates a market for textbooks. Among these, the eight listed below comprise about 4,031 pages of text and influence somewhere between half a million and eight hundred thousand students, and their instructors, each year.

  1. Steven Alter, Information Systems: The foundations of E-business (Prentice Hall, Saddle River, NJ, 4th ed. 2002);

  2. James O'Brien, Introduction to Information Systems: Essentials for the Internetworked E-business Enterprise (McGraw-Hill Irwin, Boston, 10th ed. 2001)

  3. Gordon and Gordon: Information Systems: A Management Approach, (Third Edition, John Wiley & Sons; Hoboken, NJ, 2004.).

  4. Haag, Cummings, et al, Management Information Systems (Mcgraw-Hill Ryerson, Toronto, 2nd Ed. 2004)

  5. L. Jessup and J. Valacich, Information Systems Today (Prentice Hall, Saddle River, NJ, 2003)

  6. K. Lauden and J. Lauden, Managment Information Systems (Prentice Hall, Saddle River, NJ, 10th Ed. 2004)

  7. James Senn, Information Technology; Principles, Practices, Opportunities (Pearson Prentice Ha ll, Saddle River NJ, 3ed Ed. 2004)

  8. Turban, McLean and Wetherbe: Information Technology for Management, (Third edition, John Wiley & Sons, Hoboken, NJ, 2002.)

The 587 page Alter book has three entries for Unix in its index, one for Linux. Three of these four point at a list headed "Examples of operating systems" where Unix and Linux are mentioned along with seven Microsoft products. The remaining entry points at this paragraph from page 494:

For example if vendor A's product runs on the UNIX operating system and vendor B's runs on Windows NT, vendor A may try to influence the company to view the UNIX platform as a requirement. Simualtaneously, vendor B might try to include features that are difficult to obtain through Unix.

From which our future MBA/CPA learns that Unix people are bigots and Windows offers more features.

O'Brien's book is only about 530 pages plus some appendices. Unix doesn't rate an index entry at all, but Linux gets three. Two of those point to an extract on page 153 from a Business Week article in which the authors have this to say about Linux:

Linux is good at serving up web pages, but it isn't as effective as Windows 2000 at handling more complex jobs.

The third entry, however, points to a full page mini case compiled from multiple Computerworld stories on the use of Linux in a computational grid at Amerada Hess. It says positive things about Linux on x86, although it perpetuates a Computerworld editorial standard by running down RISC/Unix.

Gordon & Gordon find room to mention both Linux and Unix once in the index to their 426 pages. These point to adjacent paragraphs on page 96 from which the student learns that:

"A variant of Unix called Linux became popular in the late 1990s. A Finnish graduate student named Linus Torvalds developed the software and purposely disclaimed any rights to it, leaving it in the public domain, with the condition that its code and all future versions developed from it remain open to view and change. Several companies, most notably Red Hat and Caldera, modified the software and then created versions having the same system calls and user interface to operate on many different types of computers."

Gnome? Gnu? GPL?, IBM/SuSe? KDE? Minix? Open Source? none of these exist; this bit of half digested Sunday Supplement paplum is what the future MBA or CPA needs to know about Linux.

Haag et al don't have any entries for Unix in their index, but have one entry for Linux, finding room on page 406 of their 524 page text to mention it in a list with four minor Microsoft OSes and MacOS.

Lauden et al have three index entries for Unix and three for Linux in their 534 pages plus appendices. In both cases the first entries point to mentions of Unix and Linux with five different Microsoft OSes in a list on page 195 and the second to two paragraph discussions on page 196 where they see no contradiction in telling students that:

"Unix also poses some security problems, because multiple users and jobs can access the same file simultaneously. Vendors have developed different verisons of Unix that are incompatible, thereby limiting software portability."

Kind of explains the horror and increduality with which new graduates greet Unix doesn't it?

On the other hand these authors do offer up two thirds of page 197 for a fairly positive mini-case on adopting Linux and offer the fairest description of Java I found in any of these books:

Java is a platform independent, object oriented programming lanaguage developed by Sun Microsystems. Java software is designed to run on any computer or computing device, regardless of the specific microprocessor or operating system it uses. A Macintosh PC, an IBM PC running Windows, a Sun server running Unix, or even a smart cellular phone or personal digital assistant can share the same Java application.(P. 200)

Jessup & Jessup find no room for Unix in the index to their 410 pages but do have one entry pointing to a mention of Linux on page 260. This turns out to be a mini-case constructed as an abstract of an approximately 1250 word original article on Somehow, however, they find room in their reduction of this to about 280 words to add the warning comment that "as long as proper testing has been conducted, and companies are aware of the downsides of Linux, this operating system can definitely become one of the most popular and cheapest systems software in the future."

And yes, the bad grammer is theirs -right along with the deep thought it reflects.

In 615 pages plus appendices Senn finds no cause to include Unix in the index, but does have a whopping six entries for Linux, all of which point to paragraphs where Unix is also mentioned. The first of these points to page 53 where Linux is listed, along with three Microsoft OSes as among "other popular operating systems." The next two point to similar lists, of OSes that run on the PowerPC and OSes that support Borland's Interbase, respectively.

The next two entries, however, point to a two page discussion of open systems starting on page 474, and the last one points to a couple of paragraphs of continuation on page 501. Unfortunately this contains such gems as this bit from the discussion on page 474 of inter-operability as a benefit of open systems:

One reason Microsoft's software is the de facto standard is because it is available to run on a variety of computer systems. Recognizing the desireability and benefits of inter-operability and software portability, Microsoft's Windows products are designed to be used on many computers besides desktop systems (servers, for example). This is not only a wish of Microsoft, but it is also the wish of many IT professionals responsible for developing and supporting enterprise systens.

As stunning insights go, that one's certainly worth the ninty-six dollars our future bosses, users, and investors are asked to pay for the book, right?

Turban et al have no entries for either Unix or Linux in the index to their 771 page text, however both Linux and Unix are included in lists of operating systems provided in the 60 pages or so of downloadable techguides that go with the book.

The index entries aren't exhaustive. Most of these books have unindexed mentions of Unix, but in total BSD, Gnu, Linux, Open source, Solaris and all of the rest of it warrant roughly one word per thousand among the two million in the books, and much of that negative.

Believe it or not, but there's an upside for the Unix community here. Simply try to remember, next time you run into users who think Microsoft invented computing, bosses who are surprised to learn that not all computers run Windows, or venture capitalists whose idea of "adult supervision" is to take your network computing idea to Windows, that they got those beliefs from their textbooks --meaning that they aren't necessarily as moronic as their opinions and that you can hope to re-educate at least some of them.

FYI: this rant is reflects a much longer and more serious piece I'm developing on problems with IT textbooks. If you could have something to contribute to that, please take a look at the draft paper and use the forum provided with it to give me your comments.

Paul Murphy wrote and published The Unix Guide to Defenestration. Murphy is a 20-year veteran of the IT consulting industry.