Translated by Geoffrey James<\/p>\n
Transcribed by Duke Hillard<\/p>\n
Transmitted by Anupam Trivedi, Sajitha Tampi, and Meghshyam Jagannath<\/p>\n
Re-html-ized and edited by Kragen Sittler<\/p>\n
Thus spake the master programmer:<\/p>\n
“When you have learned to snatch the error code from the trap frame, it
\nwill be time for you to leave.”<\/p>\n
Something mysterious is formed, born in the silent void. Waiting alone
\nand unmoving, it is at once still and yet in constant motion. It is
\nthe source of all programs. I do not know its name, so I will call it
\nthe Tao of Programming.<\/p>\n
If the Tao is great, then the operating system is great. If the
\noperating system is great, then the compiler is great. If the compiler
\nis great, then the application is great. The user is pleased and there
\nexists harmony in the world.<\/p>\n
The Tao of Programming flows far away and returns on the wind of morning.<\/p>\n
The Tao gave birth to machine language. Machine language gave birth to
\nthe assembler.<\/p>\n
The assembler gave birth to the compiler. Now there are ten thousand
\nlanguages.<\/p>\n
Each language has its purpose, however humble. Each language expresses
\nthe Yin and Yang of software. Each language has its place within the
\nTao.<\/p>\n
But do not program in COBOL<\/tt> if you can avoid it.<\/p>\n1.3<\/h3>\n
In the beginning was the Tao. The Tao gave birth to Space and Time.
\nTherefore Space and Time are Yin and Yang of programming.<\/p>\n
Programmers that do not comprehend the Tao are always running out of
\ntime and space for their programs. Programmers that comprehend the
\nTao always have enough time and space to accomplish their goals.<\/p>\n
How could it be otherwise?<\/p>\n
The wise programmer is told about Tao and follows it. The average
\nprogrammer is told about Tao and searches for it. The foolish
\nprogrammer is told about Tao and laughs at it.<\/p>\n
If it were not for laughter, there would be no Tao.<\/p>\n
The highest sounds are hardest to hear.<\/p>\n
Going forward is a way to retreat.<\/p>\n
Great talent shows itself late in life.<\/p>\n
Even a perfect program still has bugs.<\/p>\n
Thus spake the master programmer:<\/p>\n
“After three days without programming, life becomes meaningless.”<\/p>\n
The programmers of old were mysterious and profound. We cannot fathom
\ntheir thoughts, so all we do is describe their appearance.<\/p>\n
Aware, like a fox crossing the water. Alert, like a general on the
\nbattlefield. Kind, like a hostess greeting her guests. Simple, like
\nuncarved blocks of wood. Opaque, like black pools in darkened caves.<\/p>\n
Who can tell the secrets of their hearts and minds?<\/p>\n
The answer exists only in Tao.<\/p>\n
Grand Master Turing once dreamed that he was a machine. When he awoke
\nhe exclaimed:<\/p>\n
“I don’t know whether I am Turing dreaming that I am a machine,
\nor a machine dreaming that I am Turing!”<\/p><\/blockquote>\n2.3<\/h3>\n
A programmer from a very large computer company went to a software
\nconference and then returned to report to his manager, saying: “What
\nsort of programmers work for other companies? They behaved badly and
\nwere unconcerned with appearances. Their hair was long and unkempt
\nand their clothes were wrinkled and old. They crashed our hospitality
\nsuite and they made rude noises during my presentation.”<\/p>\nThe manager said: “I should have never sent you to the conference.
\nThose programmers live beyond the physical world. They consider life
\nabsurd, an accidental coincidence. They come and go without knowing
\nlimitations. Without a care, they live only for their programs. Why
\nshould they bother with social conventions?<\/p>\n“They are alive within the Tao.”<\/p>\n
2.4<\/h3>\n
A novice asked the Master: “Here is a programmer that never designs,
\ndocuments or tests his programs. Yet all who know him consider him
\none of the best programmers in the world. Why is this?”<\/p>\nThe Master replies: “That programmer has mastered the Tao. He has
\ngone beyond the need for design; he does not become angry when the
\nsystem crashes, but accepts the universe without concern. He has gone
\nbeyond the need for documentation; he no longer cares if anyone else
\nsees his code. He has gone beyond the need for testing; each of his
\nprograms are perfect within themselves, serene and elegant, their
\npurpose self-evident. Truly, he has entered the mystery of Tao.”<\/p>\n
\n<\/a> Book 3 – Design<\/h2>\n
Thus spake the master programmer:<\/p>\n
“When the program is being tested, it is too late to make design
\nchanges.”<\/p>\n3.1<\/h3>\n
There once was a man who went to a computer trade show. Each day as
\nhe entered, the man told the guard at the door:<\/p>\n“I am a great thief, renowned for my feats of shoplifting. Be
\nforewarned, for this trade show shall not escape unplundered.”<\/p><\/blockquote>\nThis speech disturbed the guard greatly, because there were millions
\nof dollars of computer equipment inside, so he watched the man
\ncarefully. But the man merely wandered from booth to booth, humming
\nquietly to himself.<\/p>\nWhen the man left, the guard took him aside and searched his clothes,
\nbut nothing was to be found.<\/p>\nOn the next day of the trade show, the man returned and chided the guard
\nsaying: “I escaped with a vast booty yesterday, but today will be even
\nbetter.” So the guard watched him ever more closely, but to no avail.<\/p>\nOn the final day of the trade show, the guard could restrain his curiosity
\nno longer. “Sir Thief,” he said, “I am so perplexed, I cannot live in
\npeace. Please enlighten me. What is it that you are stealing?”<\/p>\nThe man smiled. “I am stealing ideas,” he said.<\/p>\n
3.2<\/h3>\n
There once was a master programmer who wrote unstructured programs.
\nA novice programmer, seeking to imitate him, also began to write
\nunstructured programs. When the novice asked the master to evaluate
\nhis progress, the master criticized him for writing unstructured
\nprograms, saying, “What is appropriate for the master is not
\nappropriate for the novice. You must understand the Tao before
\ntranscending structure.”<\/p>\n3.3<\/h3>\n
There was once a programmer who was attached to the court of the
\nwarlord of Wu. The warlord asked the programmer: “Which is easier to
\ndesign: an accounting package or an operating system?”<\/p>\n“An operating system,” replied the programmer.<\/p>\n
The warlord uttered an exclamation of disbelief. “Surely an accounting
\npackage is trivial next to the complexity of an operating system,” he said.<\/p>\n“Not so,” said the programmer, “when designing an accounting package,
\nthe programmer operates as a mediator between people having different
\nideas: how it must operate, how its reports must appear, and how it
\nmust conform to the tax laws. By contrast, an operating system is not
\nlimited by outside appearances. When designing an operating system,
\nthe programmer seeks the simplest harmony between machine and ideas.
\nThis is why an operating system is easier to design.”<\/p>\nThe warlord of Wu nodded and smiled. “That is all good and well, but
\nwhich is easier to debug?”<\/p>\nThe programmer made no reply.<\/p>\n
3.4<\/h3>\n
A manager went to the master programmer and showed him the requirements
\ndocument for a new application. The manager asked the master: “How
\nlong will it take to design this system if I assign five programmers to it?”<\/p>\n“It will take one year,” said the master promptly.<\/p>\n
“But we need this system immediately or even sooner! How long will it
\ntake if I assign ten programmers to it?”<\/p>\nThe master programmer frowned. “In that case, it will take two years.”<\/p>\n
“And what if I assign a hundred programmers to it?”<\/p>\n
The master programmer shrugged. “Then the design will never be
\ncompleted,” he said.<\/p>\n
\n<\/a> Book 4 – Coding<\/h2>\n
Thus spake the master programmer:<\/p>\n
“A well-written program is its own heaven; a poorly-written program is its
\nown hell.”<\/p>\n4.1<\/h3>\n
A program should be light and agile, its subroutines connected like a
\nstring of pearls. The spirit and intent of the program should be
\nretained throughout. There should be neither too little or too much,
\nneither needless loops nor useless variables, neither lack of
\nstructure nor overwhelming rigidity.<\/p>\nA program should follow the `Law of Least Astonishment’. What is this
\nlaw? It is simply that the program should always respond to the user
\nin the way that astonishes him least.<\/p>\nA program, no matter how complex, should act as a single unit. The program
\nshould be directed by the logic within rather than by outward appearances.<\/p>\nIf the program fails in these requirements, it will be in a state of
\ndisorder and confusion. The only way to correct this is to rewrite
\nthe program.<\/p>\n4.2<\/h3>\n
A novice asked the master: “I have a program that sometime runs and
\nsometimes aborts. I have followed the rules of programming, yet I am
\ntotally baffled. What is the reason for this?”<\/p>\nThe master replied: “You are confused because you do not understand
\nTao. Only a fool expects rational behavior from his fellow humans.
\nWhy do you expect it from a machine that humans have constructed?
\nComputers simulate determinism; only Tao is perfect.<\/p>\n“The rules of programming are transitory; only Tao is eternal.
\nTherefore you must contemplate Tao before you receive enlightenment.”<\/p>\n“But how will I know when I have received enlightenment?” asked the
\nnovice.<\/p>\n“Your program will then run correctly,” replied the master.<\/p>\n
4.3<\/h3>\n
A master was explaining the nature of Tao of to one of his novices.
\n“The Tao is embodied in all software – regardless of how
\ninsignificant,” said the master.<\/p>\n“Is the Tao in a hand-held calculator?” asked the novice.<\/p>\n
“It is,” came the reply.<\/p>\n
“Is the Tao in a video game?” continued the novice.<\/p>\n
“It is even in a video game,” said the master.<\/p>\n
“And is the Tao in the DOS for a personal computer?”<\/p>\n
The master coughed and shifted his position slightly. “The lesson
\nis over for today,” he said.<\/p>\n4.4<\/h3>\n
Prince Wang’s programmer was coding software. His fingers danced upon
\nthe keyboard. The program compiled without an error message, and the
\nprogram ran like a gentle wind.<\/p>\n“Excellent!” the Prince exclaimed, “Your technique is faultless!”<\/p>\n
“Technique?” said the programmer turning from his terminal, “What I
\nfollow is Tao – beyond all techniques! When I first began to program
\nI would see before me the whole problem in one mass. After three
\nyears I no longer saw this mass. Instead, I used subroutines. But now
\nI see nothing. My whole being exists in a formless void. My senses
\nare idle. My spirit, free to work without plan, follows its own
\ninstinct. In short, my program writes itself. True, sometimes there
\nare difficult problems. I see them coming, I slow down, I watch
\nsilently. Then I change a single line of code and the difficulties
\nvanish like puffs of idle smoke. I then compile the program. I sit
\nstill and let the joy of the work fill my being. I close my eyes for
\na moment and then log off.”<\/p>\nPrince Wang said, “Would that all of my programmers were as wise!”<\/p>\n
\n<\/a>Book 5 – Maintenance<\/h2>\n
Thus spake the master programmer:<\/p>\n
“Though a program be but three lines long, someday it will have to be
\nmaintained.”<\/p>\n5.1<\/h3>\n
A well-used door needs no oil on its hinges.<\/p>\n
A swift-flowing stream does not grow stagnant.<\/p>\n
Neither sound nor thoughts can travel through a vacuum.<\/p>\n
Software rots if not used.<\/p>\n
These are great mysteries.<\/p>\n
5.2<\/h3>\n
A manager asked a programmer how long it would take him to finish
\nthe program on which he was working. “It will be finished tomorrow,”
\nthe programmer promptly replied.<\/p>\n“I think you are being unrealistic,” said the manager, “Truthfully,
\nhow long will it take?”<\/p>\nThe programmer thought for a moment. “I have some features that I
\nwish to add. This will take at least two weeks,” he finally said.<\/p>\n“Even that is too much to expect,” insisted the manager, “I will be
\nsatisfied if you simply tell me when the program is complete.”<\/p>\nThe programmer agreed to this.<\/p>\n
Several years later, the manager retired. On the way to his retirement
\nluncheon, he discovered the programmer asleep at his terminal. He had
\nbeen programming all night.<\/p>\n5.3<\/h3>\n
A novice programmer was once assigned to code a simple financial package.<\/p>\n
The novice worked furiously for many days, but when his master reviewed
\nhis program, he discovered that it contained a screen editor, a set of
\ngeneralized graphics routines, an artificial intelligence interface,
\nbut not the slightest mention of anything financial.<\/p>\nWhen the master asked about this, the novice became indignant. “Don’t
\nbe so impatient,” he said, “I’ll put in the financial stuff eventually.”<\/p>\n5.4<\/h3>\n
Does a good farmer neglect a crop he has planted?<\/p>\n
Does a good teacher overlook even the most humble student?<\/p>\n
Does a good father allow a single child to starve?<\/p>\n
Does a good programmer refuse to maintain his code?<\/p>\n
\n<\/a>Book 6 – Management<\/h2>\n
Thus spake the master programmer:<\/p>\n
“Let the programmers be many and the managers few – then all will be
\nproductive.”<\/p>\n6.1<\/h3>\n
When managers hold endless meetings, the programmers write games.
\nWhen accountants talk of quarterly profits, the development budget
\nis about to be cut. When senior scientists talk blue sky, the clouds
\nare about to roll in.<\/p>\nTruly, this is not the Tao of Programming.<\/p>\n
When managers make commitments, game programs are ignored. When
\naccountants make long-range plans, harmony and order are about to
\nbe restored. When senior scientists address the problems at hand,
\nthe problems will soon be solved.<\/p>\nTruly, this is the Tao of Programming.<\/p>\n
6.2<\/h3>\n
Why are programmers non-productive?<\/p>\n
Because their time is wasted in meetings.<\/p>\n
Why are programmers rebellious?<\/p>\n
Because the management interferes too much.<\/p>\n
Why are the programmers resigning one by one?<\/p>\n
Because they are burnt out.<\/p>\n
Having worked for poor management, they no longer value their jobs.<\/p>\n
6.3<\/h3>\n
A manager was about to be fired, but a programmer who worked for him
\ninvented a new program that became popular and sold well. As a result,
\nthe manager retained his job.<\/p>\nThe manager tried to give the programmer a bonus, but the programmer
\nrefused it, saying, “I wrote the program because I thought it was
\nan interesting concept, and thus I expect no reward.”<\/p>\nThe manager upon hearing this remarked, “This programmer, though he
\nholds a position of small esteem, understands well the proper duty
\nof an employee. Let us promote him to the exalted position of
\nmanagement consultant!”<\/p>\nBut when told this, the programmer once more refused, saying,
\n“I exist so that I can program. If I were promoted, I would do
\nnothing but waste everyone’s time. Can I go now? I have a program
\nthat I’m working on.”<\/p>\n6.4<\/h3>\n
A manager went to his programmers and told them: “As regards to
\nyour work hours: you are going to have to come in at nine in the
\nmorning and leave at five in the afternoon.” At this, all of them
\nbecame angry and several resigned on the spot.<\/p>\nSo the manager said: “All right, in that case you may set your own
\nworking hours, as long as you finish your projects on schedule.”
\nThe programmers, now satisfied, began to come in at noon and work
\nto the wee hours of the morning.<\/p>\n
\n<\/a>Book 7 – Corporate Wisdom<\/h2>\n
Thus spake the master programmer:<\/p>\n
“You can demonstrate a program for a corporate executive, but you can’t
\nmake him computer literate.”<\/p>\n7.1<\/h3>\n
A novice asked the master: “In the east there is a great
\ntree-structure that men call `Corporate Headquarters’. It is bloated
\nout of shape with vice presidents and accountants. It issues a
\nmultitude of memos, each saying `Go, Hence!’ or `Go, Hither!’ and
\nnobody knows what is meant. Every year new names are put onto the
\nbranches, but all to no avail. How can such an unnatural entity be?”<\/p>\nThe master replied: “You perceive this immense structure and are
\ndisturbed that it has no rational purpose. Can you not take
\namusement from its endless gyrations? Do you not enjoy the
\nuntroubled ease of programming beneath its sheltering branches?
\nWhy are you bothered by its uselessness?”<\/p>\n7.2<\/h3>\n
In the east there is a shark which is larger than all other fish. It
\nchanges into a bird whose wings are like clouds filling the sky. When
\nthis bird moves across the land, it brings a message from Corporate
\nHeadquarters. This message it drops into the midst of the programmers,
\nlike a seagull making its mark upon the beach. Then the bird mounts
\non the wind and, with the blue sky at its back, returns home.<\/p>\nThe novice programmer stares in wonder at the bird, for he understands
\nit not. The average programmer dreads the coming of the bird, for he
\nfears its message. The master programmer continues to work at his
\nterminal, for he does not know that the bird has come and gone.<\/p>\n7.3<\/h3>\n
The Magician of the Ivory Tower brought his latest invention for the
\nmaster programmer to examine. The magician wheeled a large black box
\ninto the master’s office while the master waited in silence.<\/p>\n“This is an integrated, distributed, general-purpose workstation,”
\nbegan the magician, “ergonomically designed with a proprietary
\noperating system, sixth generation languages, and multiple state of
\nthe art user interfaces. It took my assistants several hundred man
\nyears to construct. Is it not amazing?”<\/p>\nThe master raised his eyebrows slightly. “It is indeed amazing,” he said.<\/p>\n
“Corporate Headquarters has commanded,” continued the magician,
\n“that everyone use this workstation as a platform for new programs.
\nDo you agree to this?”<\/p>\n“Certainly,” replied the master, “I will have it transported to the
\ndata center immediately!” And the magician returned to his tower,
\nwell pleased.<\/p>\nSeveral days later, a novice wandered into the office of the master
\nprogrammer and said, “I cannot find the listing for my new program.
\nDo you know where it might be?”<\/p>\n“Yes,” replied the master, “the listings are stacked on the platform
\nin the data center.”<\/p>\n7.4<\/h3>\n
The master programmer moves from program to program without fear.
\nNo change in management can harm him. He will not be fired, even if
\nthe project is cancelled. Why is this? He is filled with Tao.<\/p>\n
\n<\/a>Book 8 – Hardware and Software<\/h2>\n
Thus spake the master programmer:<\/p>\n
“Without the wind, the grass does not move. Without software, hardware is
\nuseless.”<\/p>\n8.1<\/h3>\n
A novice asked the master: “I perceive that one computer company is
\nmuch larger than all others. It towers above its competition like a
\ngiant among dwarfs. Any one of its divisions could comprise an entire
\nbusiness. Why is this so?”<\/p>\nThe master replied, “Why do you ask such foolish questions? That
\ncompany is large because it is large. If it only made hardware,
\nnobody would buy it. If it only made software, nobody would use it.
\nIf it only maintained systems, people would treat it like a servant.
\nBut because it combines all of these things, people think it one of
\nthe gods! By not seeking to strive, it conquers without effort.”<\/p>\n8.2<\/h3>\n
A master programmer passed a novice programmer one day. The master
\nnoted the novice’s preoccupation with a hand-held computer game.
\n“Excuse me,” he said, “may I examine it?”<\/p>\nThe novice bolted to attention and handed the device to the master.
\n“I see that the device claims to have three levels of play: Easy,
\nMedium, and Hard,” said the master. “Yet every such device has
\nanother level of play, where the device seeks not to conquer the
\nhuman, nor to be conquered by the human.”<\/p>\n“Pray, great master,” implored the novice, “how does one find this
\nmysterious setting?”<\/p>\nThe master dropped the device to the ground and crushed it underfoot.
\nAnd suddenly the novice was enlightened.<\/p>\n8.3<\/h3>\n
There was once a programmer who worked upon microprocessors. “Look
\nat how well off I am here,” he said to a mainframe programmer who came
\nto visit, “I have my own operating system and file storage device.
\nI do not have to share my resources with anyone. The software is self-
\nconsistent and easy-to-use. Why do you not quit your present job and
\njoin me here?”<\/p>\nThe mainframe programmer then began to describe his system to his friend,
\nsaying “The mainframe sits like an ancient sage meditating in the midst
\nof the data center. Its disk drives lie end-to-end like a great ocean of
\nmachinery. The software is as multifaceted as a diamond, and as convoluted
\nas a primeval jungle. The programs, each unique, move through the system
\nlike a swift-flowing river. That is why I am happy where I am.”<\/p>\nThe microcomputer programmer, upon hearing this, fell silent. But the
\ntwo programmers remained friends until the end of their days.<\/p>\n8.4<\/h3>\n
Hardware met Software on the road to Changtse. Software said: “You
\nare Yin and I am Yang. If we travel together we will become famous
\nand earn vast sums of money.” And so the set forth together, thinking
\nto conquer the world.<\/p>\nPresently they met Firmware, who was dressed in tattered rags and
\nhobbled along propped on a thorny stick. Firmware said to them:
\n“The Tao lies beyond Yin and Yang. It is silent and still as a pool
\nof water. It does not seek fame, therefore nobody knows its presence.
\nIt does not seek fortune, for it is complete within itself. It exists
\nbeyond space and time.”<\/p>\nSoftware and Hardware, ashamed, returned to their homes.<\/p>\n
\n<\/a>Book 9 – Epilogue<\/h2>\n
Thus spake the master programmer:<\/p>\n
“It is time for you to leave.”<\/p>\n
\n<\/p>\n","protected":false},"excerpt":{"rendered":"
The Tao Of Programming Translated by Geoffrey James Transcribed by Duke Hillard Transmitted by Anupam Trivedi, Sajitha Tampi, and Meghshyam Jagannath Re-html-ized and edited by Kragen Sittler Table of Contents The Silent Void The Ancient Masters Design Coding Maintenance Management … Continue reading