People in the high-tech industries don’t like to demonstrate knowledge of older technology. In some circles of the computer field such knowledge actually carries a stigma!

There are valid arguments for using NEW technology whenever possible. Older technology at whatever level is a mixture of elegance and crudeness, with old questions answered and new questions left unanswered, problems left unsolved. Newer technology answers some of those new questions, solves some of those problems, and so it makes sense to move on from there instead of living and working as though those questions were never answered. It just makes common sense to move beyond early stages of development when the opportunity is there, and especially if the marketplace demands it. Most young people (and a lot of old people, too) tend to take this view, and lace it with scorn for the old.

As a result, some people will avoid mention of older stuff except in a disparaging sentence.

How far should we carry this attitude? Is E = mc² (discovered about 80 years ago) out of date? Is c² = a² + b² (determined around 2,500 years ago) old-fashioned? Or are these timeless principles? Granted, these are abstractions (rather than technology), but so is Object-Oriented logic.

Campers sometimes use gaslights on their trips through woods. In a gaslight a piece of material is burned to an ash, and the ash glows brightly as gas burns in it. I saw streetlights on a historic street on Boston’s Beacon Hill that used gas in that way. I remember thinking, “Amazing! We can actually get that much light, without electricity!” I had to catch myself and realize that my thinking was strangely upside-down. A hundred years ago with the introduction of the incandescent bulb people were thinking, “Amazing! That light that can be produced without flame, without oil or gas!” This was considered progress. And I looked at it backwards, with the same sense of wonder!

Though I’d worked in computer programming for years for big companies, my first home computer was a crude second-hand laptop, and my first exposure to the Internet was at a very low baud rate with very limited resources. But I gained a pretty good reputation with some educated people on a few newsgroups because these people considered my postings to be well-reasoned, well-thought-out, and well-expressed. Given the overwhelming number of posts with bad spelling, bad grammar, bad ideas, and good ideas expressed in bad ways with poor communication, these people considered my writing to be a breath of fresh air (I just know that some of my flame-prone colleagues will take issue with that statement). I did what I could using limited resources. We don’t have to look far to see more examples of people doing just that. Old mainframe programs may contain “spaghetti code” and heavy use of language features now considered “verboten,” but the programs also contain creative coding that managed space and run-time economically back in days when those resources were scarce and expensive. Japanese in past generations built thin paper houses to stretch their extremely limited natural resources. When I see people with what I call “Starship” computers with tremendous resources — superfast processors, huge RAM, superhuge capacity hard drives, advanced and versatile programs, and wizardlike peripherals — yet lack basic communication skills, basic historical and cultural knowledge, the essential elements of a classical education, I’m appalled. I actually have more respect and admiration for someone who accomplishes great feats with knowledge, insights, and intuitive leaps using crude, limited resources than I have for semi-literate people with generous resources at their disposal.

To support older ideas, let’s note that Isaac Newton was asked how he’d made his discoveries and accomplishments; despite the nasty things Stephen Hawking says about him, he humbly answered, “I stood on the shoulders of giants.” Even though what he did surpassed the deeds of his predecessors, he regarded them with respect, realizing that he couldn’t have reached so high without their support.

While older technology is relatively crude, it does do the job for which it was designed. There are many long-standing software applications and systems that continue to do useful work. Information technology not as sophisticated as today’s state of the art made it possible for companies to do business on a mega scale unheard of previously. Computer data-gathering and interpreting years ago made it possible to map the ocean floor, produce chromosomal maps, and really primitive computers used in the paleolithic 1960s made it possible for men to go to the moon and come back alive with pieces of it.

In his book “Small is Beautiful,” E. F. Shumacher wrote about the limits of the world’s resources, that not everybody in the world could live like a “little American” because of those limits. He suggested that less developed nations could get along well on intermediate technologies. But Schumacher threw light on a kind of ignorance many of us have, a limiting premise that if a problem can’t be solved using the latest technology, it can’t be solved — it just seems to make common sense that earlier technologies cannot solve problems if later technologies can’t.

We tend to think of technological advancement as an ordinal progression, rather than an expansion in different directions. CD-R burner drives are preferred over zip disks in desktop computers as the compact disks have greater storage capacity, but that doesn’t mean that zip drives are a more primitive technology. (Actually, files can be stored more quickly on a zip disk than on a CD, no special software is required to write the files, and the zip disk is in a sturdy casing that protects it from damage unlike the CD.) Computer pioneers John Mauchley and J. Presper Eckert, inventors of the ENIAC (Electronic Numerical Integrator And Computer), had plans to produce concurrent computer processors, but serial processors took off and concurrent processors fell by the wayside; that doesn’t mean that concurrent processing is an old-fashioned, primitive, or inferior concept (ironically, serial or Von Neumann processor-based programs may PRETEND to be concurrent processors through use of semaphores, mutexes, critical sections, etc.).

At this writing, Visual Studio .NET is a rising technological advancement in increasing demand in companies. It automatically provides the interfaces for modules written in different languages so they can interact, an ability that could otherwise be provided only by COM (Component Object Modeling). It enables people to develop software more quickly than with previous development environments. Yet this wonderful “new” development seems to be based on language principles that have been around for more than three decades and which were introduced over 25 years ago in Digital Equipment Corporation’s VAX computer. Perhaps we ought to call it “primitive”?

And if you don’t mind my getting science-fictionish, an episode of classic “Star Trek” (notice that “classic” is the new euphemism for “old”?) had the Enterprise’s landing party go to an Earth colony where the inhabitants were dying of radiation-induced aging. The landing party too started to age, except for Ensign Pavel Chekov. Dr. Leonard “Bones” McCoy remembered that Chekov entered a building, saw an extremely aged dead body, and ran out in fright. McCoy made the connection that adrenaline shot through Chekov’s system and made him resistant to radiation. Dr. Janet Wallace said that another medicine, hironaline, was used in radiation treatment instead, but “Bones” said that adrenaline was used in earlier radiation treatment research. A serum containing adrenaline was given to the surviving agers and they were restored to their proper biological ages. A recommendation was made to the Federation scientific community to include adrenaline in further studies on radiation.

The point is that not all old ideas are useless, primitive, nor naïve, and not all new ideas are better. Sometimes an idea is abandoned because of economics (greater market share for an idea that’s not as good), and sometimes a good idea just doesn’t have the charm or allure of a lesser idea.

What is Information Architecture?

“Information architecture is basically about structuring and presenting the content to the target audience. It is the information architect’s job to ensure that information is well organized and presented in an easily accessible interface.”

“Information architecture is a combination of art and science to organize information into a functional and usable format,allowing end users to easily find the information they’re looking for.”

Creating Effective Information Architecture

Effective information architecture comes from understanding business objectives and constraints, the content, and the requirements of the users.

Users + Context + Content = IA

Users

Effective information architecture must reflect the way people think about the subject matter.

Business/Context

Understanding an organisations’ business objectives, politics, culture, technology, resources and constraints is essential before considering development of the information architecture.

Content

The most effective method for understanding the quantity and quality of content (i.e. functionality and information) proposed for a system is to conduct a content inventory.

Who are the Information Architects?

Increasingly companies are realizing the importance of information architecture and are employing specialist ‘information architects’ to perform this role.

Information Architecture is also defined by:
Intranet designers and managers

Website Designers and Managers

Visual Designers

Other people designing information systems

Programmers

Librarians

Technical Writers

Technical Writers as Information Architects

If IA is about “architecting” information on a professional level, technical writers architect information every day.

Technical Writers as Information Architects do the following tasks:
1.Information Classification

2.Information Search and Retrieval

Information Classification

Organizing information in the table of contents of an end user document is called information classification.

Information Classification involves three basic structure:

Sequences: The simplest way to organize information is to place it in a sequence. Sequential ordering may be chronological, a logical series of topics progressing from the general to the specific, or alphabetical, as in indexes, encyclopedias, and glossaries.

Hierarchies: Information hierarchies are the best way to organize most complex bodies of information. As sometimes documents are developed on a single point of agenda, hierarchical schemes becomes more suitable. Hierarchical diagrams are very easy to understand.

Web: Web like organizational structures pose few restrictions on the pattern of information use. In this structure the goal is often to mimic associative thought and the free flow of ideas, allowing users to follow their interests in a unique pattern.

Information Search and Retrieval
Identifying key-words or phrases that users might search for

Creating an index for efficient search and retrieval

Providing navigation aids or hyperlinks to the key text.

Focus on Content

Information Architects (IAs) sometimes get carried away with the visual design of sites and forget about one of the most important components of the work–i.e. content. (Neil Turner, London)
*Keep focus on the content, and don’t get carried away with the presentation. This is applicable to both documents and diagrams (wireframes, site maps, personas, etc.).

*A good looking document with poor content is as similar as a not-so-good looking document having good content.

Information Chunking

Why “Chunking Information” is required?
*Mostly end users are in hurry and ignore reading long passages of text on-screen.

*Discrete chunks of information lend the end users to Web links and find a specific unit of relevant information easily, not a book’s worth of general content.

*Chunking can help organize and present information in a uniform format.

*Concise chunks of information are better suited to the computer screen, which provides a limited view of long documents. Long Web pages tend to disorient users/readers as it requires the users to scroll long distances.

Content Architecture

Content Architecture is a specific subset of the Architecture and Design phase that focuses on:
*identifying the links and relationships among documents and content

*specifying consistent document requirements and attributes, and

*defining the structure of content in a content or document management system.

Five Steps for Organizing Information

There are five basic steps in organizing your information:
*Divide your content into logical units

*Establish a hierarchy of importance among the units

*Use the hierarchy to structure relations among units

*Build a site that closely follows your information structure

*Analyze the functional and aesthetic success of your system