Computer programming (often shortened to programming or coding) is the process of designing, writing, testing, debugging, and maintaining the source code of computer programs. This source code is written in one or more programming languages. The purpose of programming is to create a set of instructions that computers use to perform specific operations or to exhibit desired behaviors. The process of writing source code often requires expertise in many different subjects, including knowledge of the application domain, specialized algorithms and formal logic.

Overview[link]

Wikiversity has learning materials about programming

Within software engineering, programming (the implementation) is regarded as one phase in a software development process.

There is an ongoing debate on the extent to which the writing of programs is an art form, a craft or an engineering discipline.^[1] In general, good programming is considered to be the measured application of all three, with the goal of producing an efficient and evolvable software solution (the criteria for "efficient" and "evolvable" vary considerably). The discipline differs from many other technical professions in that programmers, in general, do not need to be licensed or pass any standardized (or governmentally regulated) certification tests in order to call themselves "programmers" or even "software engineers." Because the discipline covers many areas, which may or may not include critical applications, it is debatable whether licensing is required for the profession as a whole. In most cases, the discipline is self-governed by the entities which require the programming, and sometimes very strict environments are defined (e.g. United States Air Force use of AdaCore and security clearance). However, representing oneself as a "Professional Software Engineer" without a license from an accredited institution is illegal in many parts of the world.

Another ongoing debate is the extent to which the programming language used in writing computer programs affects the form that the final program takes. This debate is analogous to that surrounding the Sapir–Whorf hypothesis^[2] in linguistics and cognitive science, which postulates that a particular spoken language's nature influences the habitual thought of its speakers. Different language patterns yield different patterns of thought. This idea challenges the possibility of representing the world perfectly with language, because it acknowledges that the mechanisms of any language condition the thoughts of its speaker community.

History[link]

Wired control panel for an IBM 402 Accounting Machine.

The Antikythera mechanism from ancient Greece was a calculator utilizing gears of various sizes and configuration to determine its operation,^[3] which tracked the metonic cycle still used in lunar-to-solar calendars, and which is consistent for calculating the dates of the Olympiads.^[4] Al-Jazari built programmable Automata in 1206. One system employed in these devices was the use of pegs and cams placed into a wooden drum at specific locations, which would sequentially trigger levers that in turn operated percussion instruments. The output of this device was a small drummer playing various rhythms and drum patterns.^[5][6] The Jacquard Loom, which Joseph Marie Jacquard developed in 1801, uses a series of pasteboard cards with holes punched in them. The hole pattern represented the pattern that the loom had to follow in weaving cloth. The loom could produce entirely different weaves using different sets of cards. Charles Babbage adopted the use of punched cards around 1830 to control his Analytical Engine. The first computer program was written for the Analytical Engine by mathematician Ada Lovelace to calculate a sequence of Bernoulli Numbers.^[7] The synthesis of numerical calculation, predetermined operation and output, along with a way to organize and input instructions in a manner relatively easy for humans to conceive and produce, led to the modern development of computer programming. Development of computer programming accelerated through the Industrial Revolution.

In the late 1880s, Herman Hollerith invented the recording of data on a medium that could then be read by a machine. Prior uses of machine readable media, above, had been for control, not data. "After some initial trials with paper tape, he settled on punched cards..."^[8] To process these punched cards, first known as "Hollerith cards" he invented the tabulator, and the keypunch machines. These three inventions were the foundation of the modern information processing industry. In 1896 he founded the Tabulating Machine Company (which later became the core of IBM). The addition of a control panel (plugboard) to his 1906 Type I Tabulator allowed it to do different jobs without having to be physically rebuilt. By the late 1940s, there were a variety of control panel programmable machines, called unit record equipment, to perform data-processing tasks.

Data and instructions could be stored on external punched cards, which were kept in order and arranged in program decks.

The invention of the von Neumann architecture allowed computer programs to be stored in computer memory. Early programs had to be painstakingly crafted using the instructions (elementary operations) of the particular machine, often in binary notation. Every model of computer would likely use different instructions (machine language) to do the same task. Later, assembly languages were developed that let the programmer specify each instruction in a text format, entering abbreviations for each operation code instead of a number and specifying addresses in symbolic form (e.g., ADD X, TOTAL). Entering a program in assembly language is usually more convenient, faster, and less prone to human error than using machine language, but because an assembly language is little more than a different notation for a machine language, any two machines with different instruction sets also have different assembly languages.

In 1954, FORTRAN was invented; it was the first high level programming language to have a functional implementation, as opposed to just a design on paper.^[9][10] (A high-level language is, in very general terms, any programming language that allows the programmer to write programs in terms that are more abstract than assembly language instructions, i.e. at a level of abstraction "higher" than that of an assembly language.) It allowed programmers to specify calculations by entering a formula directly (e.g. Y = X*2 + 5*X + 9). The program text, or source, is converted into machine instructions using a special program called a compiler, which translates the FORTRAN program into machine language. In fact, the name FORTRAN stands for "Formula Translation". Many other languages were developed, including some for commercial programming, such as COBOL. Programs were mostly still entered using punched cards or paper tape. (See computer programming in the punch card era). By the late 1960s, data storage devices and computer terminals became inexpensive enough that programs could be created by typing directly into the computers. Text editors were developed that allowed changes and corrections to be made much more easily than with punched cards. (Usually, an error in punching a card meant that the card had to be discarded and a new one punched to replace it.)

As time has progressed, computers have made giant leaps in the area of processing power. This has brought about newer programming languages that are more abstracted from the underlying hardware. Although these high-level languages usually incur greater overhead, the increase in speed of modern computers has made the use of these languages much more practical than in the past. These increasingly abstracted languages typically are easier to learn and allow the programmer to develop applications much more efficiently and with less source code. However, high-level languages are still impractical for a few programs, such as those where low-level hardware control is necessary or where maximum processing speed is vital.

Throughout the second half of the twentieth century, programming was an attractive career in most developed countries. Some forms of programming have been increasingly subject to offshore outsourcing (importing software and services from other countries, usually at a lower wage), making programming career decisions in developed countries more complicated, while increasing economic opportunities in less developed areas. It is unclear how far this trend will continue and how deeply it will impact programmer wages and opportunities.^{[citation needed]}

Modern programming[link]

This section relies largely or entirely upon a single source. Please help improve this article by introducing citations to additional sources. Discussion about the problems with the sole source used may be found on the talk page. (August 2010)

Quality requirements[link]

Whatever the approach to software development may be, the final program must satisfy some fundamental properties. The following properties are among the most relevant:

• Reliability: how often the results of a program are correct. This depends on conceptual correctness of algorithms, and minimization of programming mistakes, such as mistakes in resource management (e.g., buffer overflows and race conditions) and logic errors (such as division by zero or off-by-one errors).
• Robustness: how well a program anticipates problems not due to programmer error. This includes situations such as incorrect, inappropriate or corrupt data, unavailability of needed resources such as memory, operating system services and network connections, and user error.
• Usability: the ergonomics of a program: the ease with which a person can use the program for its intended purpose, or in some cases even unanticipated purposes. Such issues can make or break its success even regardless of other issues. This involves a wide range of textual, graphical and sometimes hardware elements that improve the clarity, intuitiveness, cohesiveness and completeness of a program's user interface.
• Portability: the range of computer hardware and operating system platforms on which the source code of a program can be compiled/interpreted and run. This depends on differences in the programming facilities provided by the different platforms, including hardware and operating system resources, expected behaviour of the hardware and operating system, and availability of platform specific compilers (and sometimes libraries) for the language of the source code.
• Maintainability: the ease with which a program can be modified by its present or future developers in order to make improvements or customizations, fix bugs and security holes, or adapt it to new environments. Good practices during initial development make the difference in this regard. This quality may not be directly apparent to the end user but it can significantly affect the fate of a program over the long term.
• Efficiency/performance: the amount of system resources a program consumes (processor time, memory space, slow devices such as disks, network bandwidth and to some extent even user interaction): the less, the better. This also includes correct disposal of some resources, such as cleaning up temporary files and lack of memory leaks.

Readability of source code[link]

In computer programming, readability refers to the ease with which a human reader can comprehend the purpose, control flow, and operation of source code. It affects the aspects of quality above, including portability, usability and most importantly maintainability.

Readability is important because programmers spend the majority of their time reading, trying to understand and modifying existing source code, rather than writing new source code. Unreadable code often leads to bugs, inefficiencies, and duplicated code. A study^[11] found that a few simple readability transformations made code shorter and drastically reduced the time to understand it.

Following a consistent programming style often helps readability. However, readability is more than just programming style. Many factors, having little or nothing to do with the ability of the computer to efficiently compile and execute the code, contribute to readability.^[12] Some of these factors include:

• Different indentation styles (whitespace)
• Comments
• Decomposition
• Naming conventions for objects (such as variables, classes, procedures, etc.)

Algorithmic complexity[link]

The academic field and the engineering practice of computer programming are both largely concerned with discovering and implementing the most efficient algorithms for a given class of problem. For this purpose, algorithms are classified into orders using so-called Big O notation, which expresses resource use, such as execution time or memory consumption, in terms of the size of an input. Expert programmers are familiar with a variety of well-established algorithms and their respective complexities and use this knowledge to choose algorithms that are best suited to the circumstances.

Methodologies[link]

The first step in most formal software development processes is requirements analysis, followed by testing to determine value modeling, implementation, and failure elimination (debugging). There exist a lot of differing approaches for each of those tasks. One approach popular for requirements analysis is Use Case analysis. Nowadays many programmers use forms of Agile software development where the various stages of formal software development are more integrated together into short cycles that take a few weeks rather than years. There are many approaches to the Software development process.

Popular modeling techniques include Object-Oriented Analysis and Design (OOAD) and Model-Driven Architecture (MDA). The Unified Modeling Language (UML) is a notation used for both the OOAD and MDA.

A similar technique used for database design is Entity-Relationship Modeling (ER Modeling).

Implementation techniques include imperative languages (object-oriented or procedural), functional languages, and logic languages.

Measuring language usage[link]

It is very difficult to determine what are the most popular of modern programming languages. Some languages are very popular for particular kinds of applications (e.g., COBOL is still strong in the corporate data center^{[citation needed]}, often on large mainframes, FORTRAN in engineering applications, scripting languages in web development, and C in embedded applications), while some languages are regularly used to write many different kinds of applications. Also many applications use a mix of several languages in their construction and use. New languages are generally designed around the syntax of a previous language with new functionality added (for example C++ adds object-orientedness to C, and Java adds memory management and bytecode to C++).

Methods of measuring programming language popularity include: counting the number of job advertisements that mention the language,^[13] the number of books teaching the language that are sold (this overestimates the importance of newer languages), and estimates of the number of existing lines of code written in the language (this underestimates the number of users of business languages such as COBOL).

Debugging[link]

The bug from 1947 which is at the origin of a popular (but incorrect) etymology for the common term for a software defect.

Debugging is a very important task in the software development process, because an incorrect program can have significant consequences for its users. Some languages are more prone to some kinds of faults because their specification does not require compilers to perform as much checking as other languages. Use of a static code analysis tool can help detect some possible problems.

Debugging is often done with IDEs like Eclipse, Kdevelop, NetBeans, Code::Blocks, and Visual Studio. Standalone debuggers like gdb are also used, and these often provide less of a visual environment, usually using a command line.

Programming languages[link]

Different programming languages support different styles of programming (called programming paradigms). The choice of language used is subject to many considerations, such as company policy, suitability to task, availability of third-party packages, or individual preference. Ideally, the programming language best suited for the task at hand will be selected. Trade-offs from this ideal involve finding enough programmers who know the language to build a team, the availability of compilers for that language, and the efficiency with which programs written in a given language execute. Languages form an approximate spectrum from "low-level" to "high-level"; "low-level" languages are typically more machine-oriented and faster to execute, whereas "high-level" languages are more abstract and easier to use but execute less quickly. It is usually easier to code in "high-level" languages than in "low-level" ones.

Allen Downey, in his book How To Think Like A Computer Scientist, writes:

The details look different in different languages, but a few basic instructions appear in just about every language:

• input: Get data from the keyboard, a file, or some other device.
• output: Display data on the screen or send data to a file or other device.
• arithmetic: Perform basic arithmetical operations like addition and multiplication.
• conditional execution: Check for certain conditions and execute the appropriate sequence of statements.
• repetition: Perform some action repeatedly, usually with some variation.

Many computer languages provide a mechanism to call functions provided by libraries such as in a .so. Provided the functions in a library follow the appropriate run time conventions (e.g., method of passing arguments), then these functions may be written in any other language.

Programmers[link]

Computer programmers are those who write computer software. Their jobs usually involve:

See also[link]

	Book: Programming
Wikipedia books are collections of articles that can be downloaded or ordered in print.

	Computer Science portal
	Computing portal
	Computer networking portal
	Computer programming portal

• ACCU
• Association for Computing Machinery
• Computer networking
• Computer programming in the punch card era
• Computer science
• Computing
• Hello world program
• Programming paradigms
• Software engineering
• The Art of Computer Programming

References[link]

Further reading[link]

• A.K. Hartmann, Practical Guide to Computer Simulations, Singapore: World Scientific (2009)
• A. Hunt, D. Thomas, and W. Cunningham, The Pragmatic Programmer. From Journeyman to Master, Amsterdam: Addison-Wesley Longman (1999)
• Brian W. Kernighan, The Practice of Programming, Pearson (1999)
• Weinberg, Gerald M., The Psychology of Computer Programming, New York: Van Nostrand Reinhold (1971)

External links[link]

Wikibooks has a book on the topic of Computer Programming

Wikibooks has a book on the topic of Windows Programming

Wikiquote has a collection of quotations related to: Programming

• Software engineering at the Open Directory Project
• Programming Wikia
• How to Think Like a Computer Scientist - by Jeffrey Elkner, Allen B. Downey and Chris Meyers

This biographical article needs additional citations for verification. Please help by adding reliable sources. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately, especially if potentially libelous or harmful. (June 2011)

Larry Wall
Born	(1954-09-27) September 27, 1954 (age 57)
Nationality	American
Alma mater	Seattle Pacific University
Occupation	Programmer, Author
Known for	Perl
Religion	International Church of the Nazarene
Spouse	Gloria Wall
Children	4
Website
www.wall.org/~larry/

Larry Wall (born September 27, 1954) is a programmer and author, most widely known for his creation of the Perl programming language in 1987.

Education[link]

Wall grew up in south Los Angeles and then Bremerton, Washington before starting higher education at Seattle Pacific University in 1976, majoring in chemistry and music and later premed with a hiatus of several years working in the university's computing center before graduating with a self-styled bachelor's degree in Natural and Artificial Languages.^[1]

While in graduate school at UC Berkeley, Wall and his wife were studying linguistics with the intention afterwards of finding an unwritten language, perhaps in Africa, and creating a writing system for it. They would then use this new writing system to translate various texts into the language, among them the Bible. Due to health reasons these plans were cancelled, and they remained in the U.S., where Larry instead joined the NASA Jet Propulsion Laboratory after he finished graduate school.^[2]

Accomplishments[link]

Wall is the author of the rn Usenet client and the nearly universally-used patch program. He has won the International Obfuscated C Code Contest twice and was the recipient of the first Free Software Foundation Award for the Advancement of Free Software in 1998.

Beyond his technical skills, Wall has a reputation for his wit and for his often sarcastic sense of humour,^[3] which he displays in the comments to his source code or on Usenet. For example: "We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise"^[4] and:

For example, it's been several decades now since a certain set of Bible translations came out, and you'll notice a pattern: the New English Bible, the New American Standard Bible, and the New International Version, to name a few. It's really funny. I suspect we'll still be calling them "new this" and "new that" a hundred years from now. Much like New College at Oxford. Do you know when New College was founded? Any guesses? New College was new in 1379.^[3]

Wall developed the Perl interpreter and language while working for Unisys.^[5] He is the co-author of Programming Perl (often referred to as the Camel Book and published by O'Reilly), which is the definitive resource for Perl programmers; and edited the Perl Cookbook. He then became employed full time by O'Reilly Media to further develop Perl and write books on the subject.^[5]

Wall's training as a linguist is apparent in his books, interviews, and lectures. He often compares Perl to a natural language and explains his decisions in Perl's design with linguistic rationale. He also often uses linguistic terms for Perl language constructs, so instead of traditional terms such as "variable", "function", and "accessor" he sometimes says "noun", "verb", and "topicalizer".

Wall's Christian faith has influenced some of the terminology of Perl, such as the name itself, a biblical reference to the "pearl of great price" (Matthew 13:46).^[6] Similar references are the function name bless, and the organization of Perl 6 design documents with categories such as apocalypse and exegesis. Wall has also alluded to his faith when he has spoken at conferences, including a rather straightforward statement of his beliefs at the August, 1997 Perl Conference and a discussion of Pilgrim's Progress at the YAPC (Yet Another Perl Conference) in June, 2000^{[citation needed]}.

Wall continues to oversee further development of Perl and serves as the Benevolent Dictator for Life of the Perl project. His role in Perl is best conveyed by the so-called 2 Rules, taken from the official Perl documentation:

1. Larry is always by definition right about how Perl should behave. This means he has final veto power on the core functionality.
2. Larry is allowed to change his mind about any matter at a later date, regardless of whether he previously invoked Rule 1.

Got that? Larry is always right, even when he was wrong.^[7][8]

Virtues of a programmer[link]

In the second edition of Programming Perl, Wall (along with coauthors Randal L. Schwartz and Tom Christiansen) outlined the Three Virtues of a Programmer:

1. Laziness – The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer. Also hence, this book. See also impatience and hubris.
2. Impatience – The anger you feel when the computer is being lazy. This makes you write programs that don't just react to your needs, but actually anticipate them. Or at least pretend to. Hence, the second great virtue of a programmer. See also laziness and hubris.
3. Hubris – Excessive pride, the sort of thing Zeus zaps you for. Also the quality that makes you write (and maintain) programs that other people won't want to say bad things about. Hence, the third great virtue of a programmer. See also laziness and impatience.

See also[link]

Free software portal

• List of computer scientists
• List of programmers
• Perl

References[link]

External links[link]

Wikiquote has a collection of quotations related to: Larry Wall

Listen to this article (info/dl)

This audio file was created from a revision of the "Larry Wall" article dated 2006-06-27, and does not reflect subsequent edits to the article. (Audio help)

More spoken articles

• Larry Wall's personal home page
• Slightly Skeptical View on Larry Wall and Perl (Softpanorama Larry Wall's page)
• Authoritative list of Larry Wall quotes
• Perl, the first Postmodern Language
• State of the Onion keynotes: 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007

Please note that as the State of the Onion speeches are often primarily based on visual humour, the transcripts may seem confusing or nonsensical.

This article contains Japanese text. Without proper rendering support, you may see question marks, boxes, or other symbols instead of kanji and kana.

Michio Kaku (加来 道雄, Kaku Michio^?, born January 24, 1947) is an American theoretical physicist, the Henry Semat Professor of Theoretical Physics in the City College of New York of City University of New York, a co-founder of string field theory,^[1] a futurist, and a "communicator" and "popularizer" of science. He has written several books about physics and related topics; he has made frequent appearances on radio, television, and film; and he writes extensive online blogs and articles. He has written two New York Times best sellers, Physics of the Impossible (2008) and Physics of the Future (2011). He has hosted several TV specials for BBC-TV, the Discovery Channel, and the Science Channel.

Early life and education[link]

Kaku was born in San Jose, California to Japanese immigrant parents. His grandfather came to the United States to take part in the clean-up operation after the 1906 San Francisco Earthquake^{[citation needed]}. His father was born in California but was educated in Japan and spoke little English. Both his parents were put in the Tule Lake War Relocation Center, where they met and where his two brothers were born.

At Cubberley High School in Palo Alto, Kaku assembled an atom smasher in his parents' garage for a science fair project.^[2] At the National Science Fair in Albuquerque, New Mexico, he attracted the attention of physicist Edward Teller, who took Kaku as a protégé, awarding him the Hertz Engineering Scholarship. Kaku graduated summa cum laude from Harvard University in 1968 and was first in his physics class. He attended the Berkeley Radiation Laboratory at the University of California, Berkeley and received a Ph.D. in 1972, and in 1972 he held a lectureship at Princeton University.

During the Vietnam War, Kaku completed his U.S. Army basic training at Fort Benning, Georgia and his advanced individual training at Fort Lewis, Washington.^[3] However, the Vietnam War ended before he was deployed as an infantryman.

Academic career[link]

Kaku became a visiting professor at the Institute for Advanced Study in Princeton,^[4] and New York University.^[5] He currently holds the Henry Semat Chair and Professorship in theoretical physics at the City College of New York.^[6]

Kaku has had over 70 articles published in physics journals such as Physical Review, covering topics such as superstring theory, supergravity, supersymmetry, and hadronic physics.^[7] In 1974, along with Prof. Keiji Kikkawa of Osaka University, he authored the first papers describing string theory in a field form.^[8][9]

Kaku is the author of several textbooks on string theory and quantum field theory.

Popular science[link]

Kaku is most widely known as a popularizer of science.^[10] He has written books and appeared on many television programs as well as film. He also hosts a weekly radio program.

Books[link]

Kaku is the author of various popular science books.

• Hyperspace (1994)
• Beyond Einstein (with Jennifer Thompson) (1995)
• Visions: How Science Will Revolutionize the 21st Century^[11] (1998)
• Einstein's Cosmos (2004)
• Parallel Worlds (2004)
• Physics of the Impossible (2008)
• Physics of the Future (2011)

Hyperspace was a best-seller and was voted one of the best science books of the year by both The New York Times^[10] and The Washington Post. Parallel Worlds was a finalist for the Samuel Johnson Prize for non-fiction in the UK.^[12]

Radio[link]

Kaku is the host of the weekly, one-hour radio program Explorations, produced by the Pacifica Foundation's WBAI in New York. "Explorations" is syndicated to community and independent radio stations and makes previous broadcasts available on the program's website. Kaku defines the show as dealing with the general topics of science, war, peace, and the environment.

In April 2006, Kaku began broadcasting Science Fantastic on 90 commercial radio stations, the only nationally syndicated science program on commercial radio in the United States. It is syndicated by Talk Radio Network and now reaches 130 radio stations and America's Talk on XM. The program is formatted as a live listener call-in show, focusing on "futurology," which he defines as the future of science.^{[citation needed]} Featured guests include Nobel laureates and top researchers on the topics of string theory, time travel, black holes, gene therapy, aging, space travel, artificial intelligence, and SETI. When Kaku is busy filming for television, Science Fantastic goes on hiatus, sometimes for several months. Kaku is also a frequent guest on many programs, where he is outspoken in all areas and issues he considers of importance, such as the program Coast to Coast AM, where on 30 November 2007, he reaffirmed his belief that there is a 100% probability of extraterrestrial life in the universe.^[13]

Kaku has appeared on The Opie and Anthony Show a number of times, discussing popular fiction such as Back to The Future, Lost, and the theories behind time-travel that these and other fictional entertainment focus on.

Television and film[link]

Kaku has appeared in many forms of media and on many programs and networks, including Good Morning America, The Screen Savers, Larry King Live, 60 Minutes, Nightline, 20/20, Naked Science, CNN, ABC News, CBS News, NBC News, Al Jazeera English, Fox News Channel, The History Channel, Conan, The Science Channel, The Discovery Channel, TLC, Countdown with Keith Olbermann, The Colbert Report, The Art Bell Show and its successor, Coast To Coast AM, BBC World News America, The Opie & Anthony Show, The Covino & Rich Show, Head Rush, The Late Show with David Letterman, and Real Time with Bill Maher.

In 1999, Kaku was one of the scientists profiled in the feature-length film Me and Isaac Newton, directed by Michael Apted. It played theatrically in the United States, was later broadcast on national TV, and won several film awards.^{[citation needed]}

In 2005, Kaku appeared in the short documentary Obsessed & Scientific. The film is about the possibility of time travel and the people who dream about it. It screened at the Montreal World Film Festival and a feature film expansion is in development talks. Kaku also appeared in the ABC documentary UFOs: Seeing Is Believing, in which he suggested that while he believes it is extremely unlikely that extraterrestrials have ever actually visited Earth, we must keep our minds open to the possible existence of civilizations a million years ahead of us in technology, where entirely new avenues of physics open up. He also discussed the future of interstellar exploration and alien life in the Discovery Channel special Alien Planet as one of the multiple speakers who co-hosted the show, and Einstein's Theory of Relativity on The History Channel.

In February 2006, Kaku appeared as presenter in the BBC-TV four-part documentary Time which seeks to explore the mysterious nature of time. Part one of the series concerns personal time, and how we perceive and measure the passing of time. The second in the series deals with cheating time, exploring possibilities of extending the lifespan of organisms. The geological time covered in part three explores the ages of the earth and the sun. Part four covers the topics of cosmological time, the beginning of time and the events that occurred at the instant of the big bang.

On January 28, 2007, Kaku hosted the Discovery Channel series 2057. This three-hour program discussed how medicine, the city, and energy could change over the next 50 years.

In 2008, Kaku hosted the three-hour BBC-TV documentary Visions of the Future, on the future of computers, medicine, and quantum physics, and he appeared in several episodes of the History Channel's Universe series.

On December 1, 2009, he began hosting a 12-episode weekly TV series for the Science Channel at 10 pm, called Sci Fi Science: Physics of the Impossible, based on his best-selling book. Each 30-minute episode discusses the scientific basis behind imaginative schemes, such as time travel, parallel universes, warp drive, star ships, light sabers, force fields, teleportation, invisibility, death stars, and even superpowers and flying saucers. Each episode includes interviews with the world's top scientists working on prototypes of these technologies, interviews with science fiction fans, clips from science fiction movies, and special effects and computer graphics. Although these inventions are impossible today, the series discusses when these technologies might become feasible in the future.^[14]

In 2010, he began to appear in a series on the website Gametrailers.com called Science of Games, discussing the scientific aspects of various popular video games such as Mass Effect 2 and Star Wars: The Force Unleashed.

Kaku is popular in mainstream media because of his knowledge and his accessible approach to presenting complex subjects in science. While his technical writings are confined to theoretical physics, his public speaking and media appearances cover a broad range of topics, from the Kardashev scale to more esoteric subjects such as wormholes and time travel. In January 2007, Kaku visited Oman. While there, he talked at length to select members of that country's decision makers. In an interview with local media, Dr Kaku elaborated on his vision of mankind's future. Kaku considers climate change and terrorism as serious threats in man's evolution from a Type 0 civilization to Type 1.^[15]

He is pictured in Symphony of Science's newest song (as of September 6, 2011), 'The Quantum World.'

On October 11, 2010, Michio Kaku appeared in the BBC program "What Happened Before the Big Bang" (along with Laura Mersini-Houghton, Andrei Linde, Roger Penrose, Lee Smolin, Neil Turok, and other notable cosmologists and physicists), where he propounded his theory of the universe created out of nothing.^[16]

Social policy advocacy[link]

Kaku has publicly stated his concerns over matters including the anthropogenic cause of global warming, nuclear armament, nuclear power and the general misuse of science.^[17] He was critical of the Cassini–Huygens space probe because of the 72 pounds (33 kg) of plutonium contained in the craft for use by its radioisotope thermoelectric generator. Conscious of the possibility of casualties if the probe's fuel were dispersed into the environment during a malfunction and crash as the probe was making a 'sling-shot' maneuver around earth, Kaku publicly criticized NASA's risk assessment.^[18] He has also spoken on the dangers of space junk and called for more and better monitoring. Kaku is generally a vigorous supporter of the exploration of outer space, believing that the ultimate destiny of the human race may lie in extrasolar planets; but he is critical of some of the cost-ineffective missions and methods of NASA.

Kaku credits his anti-nuclear war position to programs he heard on the Pacifica Radio network, during his student years in California. It was during this period that he made the decision to turn away from a career developing the next generation of nuclear weapons in association with Edward Teller and focused on research, teaching, writing and media.^{[citation needed]} Kaku joined with others such as Helen Caldicott, Jonathan Schell, Peace Action and was instrumental in building a global anti-nuclear weapons movement that arose in the 1980s, during the administration of U.S. President Ronald Reagan.

Kaku was a board member of Peace Action and on the board of radio station WBAI-FM in New York City where he originated his long running program, Explorations, that focused on the issues of science, war, peace and the environment.

His remark from an interview in support of SETI, "We could be in the middle of an intergalactic conversation...and we wouldn't even know.", is used in the third Symphony of Science installment "Our Place in the Cosmos".

Personal life[link]

Kaku is married to Shizue Kaku and has two daughters.^[19]

Bibliography[link]

References[link]

External links[link]

Wikimedia Commons has media related to: Michio Kaku

Listen to this article (info/dl)

This audio file was created from a revision of the "Michio Kaku" article dated 2007-07-08, and does not reflect subsequent edits to the article. (Audio help)

More spoken articles

• Official website
• Michio Kaku on Twitter
• Getting Physical: Dr. Michio Kaku Explains Einstein's Genius
• Russia Takes Aim at Asteroids, op-ed on asteroid defense, Wall St. Journal, Jan. 5, 2010
• The Skeptics' Guide To The Universe interview
• Michio Kaku at the Internet Movie Database
• Michio Kaku on National Public Radio
• About Michio Kaku
• Video: Michio Kaku discusses Physics of the Future on March 23, 2011, on Forum Network.
• In Depth interview with Kaku, October 3, 2010