James Gleick has written a very interesting book on the history of information called "The Information".

This is useful reading for anyone interested in computer/information science.

The book is available in PDF form via the Internet from a variety of sites.

Gleick, J. (2011). The Information: A History, a Theory, a Flood. Pantheon Books..

James Gleick (American author and historical scientist) has written a very interesting book on the field known as "chaos theory" - a sensitive dependency on initial conditions. The field was accidentally discovered by the young French mathematician Henri Poincaré while attempting to find an exact mathematical solution for the three body problem.

Lorentz, in the weather field, rediscovered this idea and provided a name for it. The analogy is that, due to round-off errors in computations, it is "as if" a butterfly flapped it's wings in California and a typhoon resulted in China.
Gleick, J. (1988). Chaos: making a new science. New York: Penguin Books..

t is not the amount of knowledge that makes a brain. It is not even the distribution of knowledge. It is the interconnectedness. James Gleick (American author and historical scientist)

You don’t see something until you have the right metaphor to let you perceive it. James Gleick (American author and historical scientist)

Everything we care about lies somewhere in the middle, where pattern and randomness interlace. James Gleick (American author and historical scientist)

The universe is computing its own destiny. James Gleick (American author and historical scientist)

Redundancy—inefficient by definition—serves as the antidote to confusion. James Gleick (American author and historical scientist)

Ideas that require people to reorganize their picture of the world provoke hostility. James Gleick (American author and historical scientist)

When information is cheap, attention becomes expensive. James Gleick (American author and historical scientist)

In computer programming, a bug is an error in software. However, Microsoft does not like to refer to bugs as bugs. Instead, the following terms have been used by their support staff when talking to customers.

• an issue, such as a known issue or an intermittent issue
• design side-effect
• undocumented behavior
• technical glitch
• anomaly

Avoiding using the word "bug" has been christened "Microspeak", at least by James Gleick. Gleick, J. (September 1997). "A bug by any other name...", in Visual Basic programmer's journal, Vol 7, No. 10, p. 128..