codeless_code 0.1.2

data/data/the-codeless-code/en-qi/case-107.txt

@@ -0,0 +1,98 @@
+Date: 2013-08-23
+Title: Babel
+Number: 107
+Geekiness: 2
+Names: Kaimu
+Topics: languages, high-level languages, Perl, Python
+Credits: The topic was suggested by Xunie.
+Illus.0.par: 0
+Illus.0.src: Stranger-detail.jpg
+Illus.1.par: last
+Illus.1.src: Stranger.jpg
+Illus.1.align: centered
+
+
+A thin, bedraggled stranger came to the Temple one night and
+asked for master [[Kaimu]].  The master was roused and
+brought to the gate, whereupon the stranger said:
+
+"For years I have wandered this pitiless land, seeking the
+perfect programming language.  Name any one and I've given
+it a go, be it fast or slow, high-level or low, from Ada to
+Zeno.  But whatever the pluses there are minuses too, so I
+pack my things and hit the road again -- which in this case
+led me to your door."
+
+Kaimu asked the stranger to describe the language of
+his heart's desire.
+
+"It must be suitable enterprise-wide," the stranger replied,
+"client-side and server-side, in scripting, in shells
+and in spreadsheet cells.  I need it real-time,
+multi-threaded and optionally object-oriented; with garbage
+collection, deadlock detection, custom exceptions,
+auto-resizing arrays of things and regular expressions for
+matching strings.  I want the simplicity of BASIC, the
+purity of Smalltalk, the brevity of Haskell, the speed of
+C, the consistency of Lisp, the readability of Python, the
+flexibility of Perl, and the portability of... Java, I
+guess, but with native code bindings that aren't a mess."
+
+"Then tomorrow morning we shall assist you as best we can,"
+said Kaimu.  "But tonight you must spend in the carpenter's
+shed below the south wall."
+
+The stranger bowed and departed to make his bed amid sawdust
+and wood shavings.  As Kaimu left for his own chambers a
+monk asked, "What is your design for him?"
+
+"When dawn breaks," replied the master, "our guest will
+see that on the walls of that shed are arrayed ten thousand
+tools, each crafted to serve a unique purpose.  No one would
+mistake the hammer for the chisel, and no true
+carpenter would renounce one for the other."
+
+- - -
+
+At the sun's first light the stranger returned to the Temple
+gate, there to be greeted again by Kaimu and the monk.
+
+"Do you still seek your heart's desire?" asked Kaimu.
+
+"No!" replied the stranger.  "For in the shed I found a
+most marvelous dagger, no larger than my hand, whose hilt
+opened to reveal the most wonderous things: tweezers and
+toothpicks, pliers and drill-bits, wrenches and reamers and
+rulers and tiny blades too numerous to count!  Holding it I
+understood that my destiny is to fashion the thing I have
+sought for -- a language made of other languages, a tool to
+end the need for other tools!"
+
+And with that the stranger bowed and departed.
+
+The monk turned to Kaimu, whose jaw had gone somewhat
+slack.  "What do the annals say on the subject of
+the Misunderstood Lesson?"
+
+"That it too brings wisdom," said the master, "If only to
+the hapless teacher.  No doubt I would have been twice as
+effective had I been half as clever."
+
+"And what of the stranger?" asked the monk.  "Surely he will
+fail in his endeavor, for that knife he prizes holds neither
+hammer nor chisel.  And should he partly succeed then all
+the worse, for he will have added yet another language to a
+world that already drowns in confusion."
+
+"Let him try, and good fortune to him!" said Kaimu.  "If not
+for fools of his fashion, we would not have Perl or Python,
+Bourne shell or Tcl, and the world would be a poorer place.
+I only grieve that you and I are not such fools, for since
+we will never attempt the impossible, we can never hope to
+achieve it."
+
+Thus master and monk left the gate, and went in to the
+Temple together to greet the morning.
+
+
+

data/data/the-codeless-code/en-qi/case-108.txt

@@ -0,0 +1,75 @@
+Date: 2013-09-01
+Number: 108
+Title: Sweet Tooth
+Geekiness: 3
+Names: Djishin, Banzen, Satou
+Topics: refactoring, design, frameworks, partial solutions, YAGNI, reflection
+Illus.0.par: 1
+Illus.0.src: MrYuk.jpg
+Illus.0.title: I need a way to insert big fluorescent 'Mr. Yuk' icons into source code.
+
+The monk [[Djishin]] was tasked with creating a web page for
+querying the system's inventory table of rice bags.  Glumly
+contemplating the dull day's work that lay before him, the
+monk had a sudden inspiration:
+
+<i>I must produce a presentation-layer object to hold the
+parameters from the search form,</i> he thought, <i>as well
+as a service-layer object to represent each row returned by
+the search.  Yet these both would have the same attributes
+as the RiceBag object we currently use for creating new
+table rows.  Can I not simply reuse that database-layer
+object for these other two purposes?</i>
+
+With growing excitement, he thought: <i>If a database object
+were suitably annotated, I could develop a framework which
+would acquire the form input, validate it, convert it to
+SQL, query the table, and present the search results to the
+user in tabular format... all requiring the most minimal
+effort on the part of the framework's consumer!</i>
+
+The monk thus spent the next few days happily coding the framework,
+with the /RiceBag/ search page as its proof-of-concept.
+
+- - -
+
+At the end of the week Djishin proudly showed the fruits of
+his labor to master [[Banzen]].  The master studied the new
+framework, nodded, and ordered Djishin to convert seven
+existing search pages in the application to use it, starting
+with the Warrior page.
+
+After the monk ran off to comply, a nun who had been
+standing nearby approached Banzen.
+
+"Master," asked the nun, "The Warrior object has but a
+single Status value.  If the user's query is represented by
+a single Warrior, how could we ask for Warriors whose Status
+is either Missing, Retired, or Dead?"
+
+"We could not," said Banzen.
+
+"Furthermore," continued the nun, "The Warrior object
+contains only information stored in the Warrior
+table.  How could we find Warriors by the types of Weapons
+they use, or by the Regiments they have served in, since
+these require joining to child tables?"
+
+"We could not," said Banzen.
+
+The master took a small dark nugget from the jar he kept on
+his desk, giving it to the puzzled nun.  "There once was a
+monk who tired of rice.  One day he stumbled upon the art of
+making <i>kuro sato</i> -- black sugar candy.  For years
+he nibbled piece after piece throughout the day, gradually
+becoming flabby and pale and void of tooth.  What was his
+master's error?"
+
+"Failing to forbid the candy," said the nun.
+
+Banzen shook his head and pushed the heavy jar across the desk.
+
+"Finish that by tomorrow evening," commanded Banzen. "Then
+you will understand Djishin's correction."
+
+

data/data/the-codeless-code/en-qi/case-109.txt

@@ -0,0 +1,56 @@
+Date: 2013-09-03
+Number: 109
+Title: The Ties that Bind
+Geekiness: 3
+Names: Djishin, Banzen, Satou
+Topics: design, frameworks, partial solutions, complexity, configuration
+Illus.0.par: 0
+Illus.0.src: Chained.jpg
+Illus.0.title: He really shouldn't have had those three cans of Diet Coke an hour ago.
+
+The monk [[Djishin]] approached master [[Banzen]], troubled.
+
+"[[#108|The search framework I wrote]] is currently
+incapable of handling the tasks assigned to me,"
+said the monk.  "But I still believe it to have great
+virtue.  Will you allow me to develop it further so that
+these obstacles may be overcome?"
+
+"What is the great virtue of your framework?" asked Banzen
+absently as he gazed out the window.
+
+The monk replied, "If a database table's Value Object is
+annotated appropriately, an entire search form for that table
+may be created with little or no code!"
+
+"It is certain that the authorship of code is a burden on
+the Temple," said Banzen, his eyes following a black-headed
+finch as it darted to and fro.  "If we were not so busy
+coding, we would have far more time... for coding."
+
+"The code I would eliminate is only the tedious sort,"
+said Djishin.  "Consider that finch: how high it could
+fly if it did not have to hunt for insects in the mud!"
+
+The master turned to face the monk.
+
+"Your framework is suitable for simple problems only.  It
+fails when presented with the most minor of complexities --
+ones that a traditional implementation would easily overcome.
+How will you remedy this?"
+
+"By giving my framework numerous configuration options and
+customization hooks," said the monk.
+
+"Go then," said Banzen sharply, dismissing the monk with a
+wave of his hand.
+
+After the monk had departed, Banzen summoned the nun [[Satou]].
+She approached the master's desk nervously, keeping well
+away from the [[#108|jar]] upon it.
+
+"When that monk returns to his cubicle," said Banzen,
+"Shackle his feet to his desk and leave him there for a day.
+If tomorrow he complains, free his feet and shackle his
+hands to the desk instead, telling him that he can now run as fast as he
+pleases."

data/data/the-codeless-code/en-qi/case-11.txt

@@ -0,0 +1,41 @@
+Title: Cages
+Number: 11
+Date: 2010-11-11
+Geekiness: 2
+Topics: reuse, process
+Names: Elephant's Footprint Clan
+
+To prevent any further proliferations of redundant code, the
+abbot of the [[Elephant's Footprint Clan]] decreed that his
+monks were only to produce code which was
+application-specific.  Anything of a more general nature had
+to be proposed to a Software Reuse Subcommittee, which
+researched open source solutions, weighed the merits of the
+proposal against the needs of the various applications,
+amended the design as its members saw fit, and (if all signs
+were favorable) put the project on the implementation
+schedule.  The whole process, from inception to execution,
+took many weeks.
+
+When news of this policy reached him, the Java master sent
+for the abbot's two prized songbirds.  His letter promised
+that the birds would be returned the following week.  And so
+they were, in two separate bamboo cages of the Java master's
+devising.
+
+The bars of the first cage were a handspan apart; the bird
+had easily escaped during the journey.
+
+The bars of the second cage were so close that neither light
+nor air could pass through.  The bird inside was dead upon
+arrival.
+
+Tied to each cage was a poem in the master's hand:
+
+   Along the road //
+   from /air/ to /coffin/  //
+   lie the many houses of /cage/. //
+
+   The house of the thrush //
+   is not shared //
+   by the worm and the bull.

data/data/the-codeless-code/en-qi/case-110.txt

@@ -0,0 +1,93 @@
+Date: 2013-09-15
+Number: 110
+Title: The Trunk
+Geekiness: 2
+Names: Bawan, Spider Clan, Laughing Monkey Clan, Elephant's Footprint Clan
+Topics: complexity, efficiency, data transfer objects, YAGNI
+Illus.0.par: 3
+Illus.0.src: Trunk.jpg
+
+A certain monk was summoned to the presence of master [[Bawan]]:
+
+"This trunk holds something which must be brought to the
+[[Spider Clan]]," said Bawan, pointing to a great wooden box
+bound with iron straps.  "Carry it to the abbot unaided and
+he will reward you for your pains.  A letter of explanation is
+tucked under the latch."
+
+With great difficulty the monk hoisted the trunk upon
+his back and set out across the temple grounds to the
+domicile of the temple's web developers.  There he
+was received by the abbot, who perused the letter
+while the exhausted monk waited for his reward.
+
+"This trunk is none of my concern," said the abbot, stuffing
+the letter back in place.  "It must be brought to the abbess
+of [[Laughing Monkey Clan]].  Carry it there unaided and
+your compensation will be most enviable."
+
+The monk did as he was asked, panting with every step as
+he crossed the temple grounds to the domicile of the
+business logicians.  The abbess resided on the topmost floor.
+
+"This trunk is nothing to do with me," said the abbess, who
+refused to let the monk set his burden down.  "It must be
+brought to [[Elephant's Footprint Clan]] at once."
+
+"I think I see where this is going," grimaced the monk.  "Perhaps
+one of your own monks can carry it?"
+
+"No time, no time!" said the abbess, tucking the letter back
+under the latch as she shooed the monk out the door.  "Carry it
+there unaided and great riches will await you!"
+
+An hour later the monk staggered into the domicile of the temple's
+persistence-tier coders, collapsing in the main hallway with the
+trunk still on his back.  The white-haired abbot was summoned.
+
+"Wonderful!" said the old abbot after reading the letter.
+The semi-conscious monk heard him open the lid and close it
+again.  "Monk, wake up!  As reward for your service you may
+keep everything else in the trunk.  Now be off!"
+
+The monk crawled slowly out the door, like a turtle laboring
+under a great wooden shell.  It was nighttime when he
+reached his own quarters and tipped the trunk off his back.
+The top fell open and a hundred iron boxes spilled out.
+
+He opened them one by one. All were empty.
+
+Nothing else remained in the trunk but Bawan's
+letter, which the old abbot had tossed back inside.  The
+monk unfolded it and read:
+
+       To the abbots of the Three Clans --
+
+       In examining the performance problems of our shopping
+       cart system, I discovered that hundreds of actions
+       in the webtier are loading the very large and
+       complex CatalogInfo object tree from the database.
+
+       In examining the webtier, I discovered that these
+       actions are simply passing the unexamined CatalogInfo
+       into the sixteen service-tier methods which
+       happen to demand it.
+
+       In examining the service tier, I discovered that
+       these methods are simply passing the unexamined
+       CatalogInfo into four persistence-tier methods
+       which happen to demand it.
+
+       In examining the persistence tier, I discovered that
+       these methods are simply passing the unexamined
+       CatalogInfo into the one utility-tier method
+       which happens to demand it.
+
+       In examining that single method, I discovered that
+       it does nothing but check the CatalogInfo's
+       integer-valued Type property to ensure that it is
+       not negative.   I also discovered that this method
+       was authored by the young man bearing my trunk.
+
+       Please ensure that he receives my explanation
+       in a suitable manner.

data/data/the-codeless-code/en-qi/case-111.txt

@@ -0,0 +1,51 @@
+Number: 111
+Date: 2013-09-17
+Title: Labyrinth
+Geekiness: 1
+Names: Suku, Banzen
+Topics: requirements, design, complexity, elegance, neatness, compromise, code reviews, planning
+Illus.0.src: Stagger.jpg
+Illus.0.title: Breakin’ the build? That’s a paddlin’.  Swallowin’ exceptions? That’s a paddlin’.  Stealin’ my paddle?  That’s a whuppin’.
+
+Regarding how master [[Suku]] received her name, this much may be told:
+
+Many years ago, when Suku was still a novice at the Temple,
+she had been tasked with reviewing the code of a monk in her
+clan.  Wishing to impress the masters in the audience, the
+novice was merciless in her criticisms of the monk.  Chief
+among her complaints was the inelegance of his solution and
+its overly complex structure.
+
+After the meeting had concluded, master [[Banzen]] -- who was
+two decades her senior -- followed her outside the
+meeting hall and down the stone steps.  At the bottom he
+said, “Little nun!  Do you know the way to the Abbey of Iron
+Bones?”
+
+Suku pointed. “Straight across the courtyard.”
+
+Banzen said, “Walk it, then.”
+
+No sooner had Suku gone three paces when the master struck
+her left side with a large rice paddle, /thwock!/ sending her
+reeling into a plum tree.  Though surprised, the novice knew
+better than to question or complain.  Instead she dusted
+herself off and continued toward the abbey, only to find two
+gardeners blocking her path.  She sidestepped them and
+/thwock!/ the paddle came down upon her head.  Now dizzy, she
+splashed through a koi pond, stumbled into a shrine, tripped
+over a tree root, and /thwock!/ now her right side met master
+Banzen’s paddle and she found herself sprawled among the
+peonies.
+
+Eventually the bruised and winded nun arrived at the steps
+of the Abbey of Iron Bones, with Banzen right on her heels.
+
+<i>“Straight across the courtyard,”</i> echoed Banzen.  “Design.”
+
+The master then took Suku gently by the shoulders and turned
+her around to face the twisted path her steps had traced in
+the dust.  “Implementation,” said Banzen.
+
+As the novice considered this, Banzen handed her the paddle
+and said, “The World.”

data/data/the-codeless-code/en-qi/case-112.txt

@@ -0,0 +1,51 @@
+Date: 2013-09-21
+Number: 112
+Title: Speak to Me
+Geekiness: 2
+Topics: refactoring, complexity, communication, design, elegance, teamwork
+Names: Yíwen, Hwídah, Yishi-Shing
+Illus.0.src: Unicycle.jpg
+Illus.0.par: 1
+Illus.0.title: On the plus side, she gets three skeins to the kilometer and she can always find her way back home.
+
+The timid nun [[Yíwen]] opened several source files she had
+authored barely a year ago, only to find unrecognizable code
+within.  After inspecting their revision history she
+approached the cubicle of her longtime companion.
+
+"A thousand pardons, [[Hwídah]]," she began, "but it appears that
+you have completely rewritten my address-management service.
+Why did you find this necessary?"
+
+"The code was uncharacteristically complex and
+unintuitive," answered Hwídah gently.  "You created many more
+interfaces than necessary, nested value objects inside of
+other value objects, defined abstract classes which have
+only one concrete implementation, and performed database
+updates in two separate transactions where one would have
+sufficed.  I have simplified the structure."
+
+Yíwen bowed humbly, gave her thanks, and walked out.
+
+- - -
+
+The following morning Hwídah approached the cubicle of her
+longtime companion, bearing a beautiful steel
+contraption.  She dropped it noisily onto
+Yíwen's desk.
+
+"I found this waiting for me when I awoke this morning,"
+said Hwídah.  "Explain."
+
+"Your old spinning-wheel was uncharacteristically complex
+and unintuitive -- do you not agree?" asked Yíwen.  "You
+used many more gears than necessary, placed the fiber basket
+in a poor location, padded the stands but not the hand
+cranks, and used two separate flywheels where one would have
+sufficed.  I have simplified the mechanics."
+
+Hwídah bowed humbly, gave her thanks, and walked out.
+
+She then went straight away to master [[Yishi-Shing]], saying,
+"Regrettably, I will not be able to participate in your clan's
+weekly bicycle rides anytime soon."

data/data/the-codeless-code/en-qi/case-113.txt

@@ -0,0 +1,58 @@
+Number: 113
+Date: 2013-10-07
+Title: Black Sheep
+Geekiness: 2
+Names: Zjing, Laughing Monkey Clan
+Topics: mentoring, improvement, IDEs, copy-paste, code reviews, standards, sample code
+Illus.0.src: sheep.jpg
+Illus.0.par: 1
+Illus.0.title: ewe: Can't spawn child: insufficient RAM.
+
+
+A senior monk of the [[Laughing Monkey Clan]],
+exasperated by the poor quality of his team's code, was
+advised to seek the counsel of the nun [[Zjing]] who lived
+in the valley below.  He found her tending the Temple's
+sheep in the high pasture.
+
+"What have you tried?" asked the nun.
+
+"I have left copies of our Standards and Practices in
+every cubicle," said the monk.  "Each morning I send out
+links to pertinent software engineering articles, and each
+evening I review the day's code.  Still nothing changes.
+Each monk commits the same errors as he did the day before,
+and the codebase grows ever uglier."
+
+Zjing leaned on her staff and gazed absently into the
+distance.
+
+Finally she said: "The shepherd cannot move the flock; only
+the sheep can do that."
+
+The senior monk frowned.  "I do not see."
+
+Zjing picked up a small stone and hurled it at a black-faced
+ram which stood at the edge of the flock.  The stone struck
+the ram's ear, whereupon the animal bleated and trotted
+away.  Its neighbors promptly followed, then their
+neighbors, and so on, until the entire wooly herd flowed
+like sea-foam down the hillside.  Zjing walked with
+them.
+
+The senior monk folded his arms and remained on the hilltop,
+unconvinced.  "Even if I can correct one monk,
+why should the clan follow him if they do not follow me?"
+
+/"Wú,"/ said Zjing, throwing a stone at the fellow.  "It is
+not the monks you should be herding, but the code.  Some of
+it strides forward with purpose, but most simply follows
+what came before.  One monk's IDE generates a poor method
+skeleton, a second monk copies the finished method
+throughout the class, a third saves the class under a
+different name for his own purposes..."
+
+The nun found her way to the black-faced ram and stroked its
+bloodied ear.  "Your codebase is the errant sheep," she
+called back to the senior monk.  "Correct it, and the
+laziness of your monks will prove a great virtue."

data/data/the-codeless-code/en-qi/case-114.txt

@@ -0,0 +1,55 @@
+Number: 114
+Date: 2013-10-11
+Title: Character Assassination
+Geekiness: 1
+Names: Bawan, Zjing's Bridge
+Topics: Unicode, ASCII, internationalization
+Illus.0.par: 1
+Illus.0.src: Moped.jpg
+Illus.0.title: And those rocks down there don't look soft AT ALL.
+
+The Temple's systems were experiencing sporadic failures
+when interacting with a document-registration service in the
+Far West.  Java master [[Bawan]] chose to investigate.
+
+To assist him, a liaison for the Western temple was
+dispatched from the next province.  The liaison was an
+unkempt man with a noisy moped; his ability to
+translate technical language was his only redeeming quality.
+
+"I have found the problem," said Bawan to the liaison.  "If
+the document title contains a right-apostrophe, that
+character does not appear when we retrieve the record.
+Please tell the Western Monks of this defect."
+
+The liaison returned to his province and phoned Bawan the
+following day.
+
+"The monks assert that it is not a defect," said the liaison.
+"They say: we do not support special characters."
+
+Bawan nodded.  "Return to my temple tomorrow.  Together we
+can make them understand."
+
+The following day the liaison rode his rattling moped up the
+Dying Moon Road.  After passing a sign declaring /ZJING'S
+BRIDGE/ in large red letters, he found himself crossing a
+vast gorge on a span of rope and plank.  Directly ahead rose
+a magnificent stand of oaks and, beyond them, the towers of
+the temple.  He was so entranced by the sight that he failed
+to notice that the planks were missing in the middle ten
+yards of the bridge.  Thus the liaison found himself
+unexpectedly plummeting to the gorge below, moped and all.
+
+Watching from the upper balcony in the East Tower, master
+Bawan nodded and went inside.  He then summoned a junior
+monk from the cubicles downstairs.
+
+"Take these to the far side of [[Zjing's Bridge]]," he said,
+handing three pieces of wood to the monk.  They were painted
+red and carved in the shapes of large letters: an /O,/ a
+/U,/ and a /T./
+
+"What are these?" asked the monk.
+
+"Special characters," replied the master.

data/data/the-codeless-code/en-qi/case-115.txt

@@ -0,0 +1,47 @@
+Date: 2013-10-18
+Number: 115
+Title: Pain
+Geekiness: 3
+Names: Banzen
+Topics: error handling, exceptions, null, Java, primitives, data transfer objects, null pointer exception
+Illus.0.par: 2
+Illus.0.src: OnFire.jpg
+Illus.0.title: I don't know why anyone would voluntarily choose to be a hunk of burning love.
+
+Reports of corrupted data had reached the ears of Java
+master [[Banzen]].  After reviewing the code base
+he summoned a certain monk to his office.
+
+"You take great pains to avoid null-valued objects," said
+the master.  "You initialize all Strings to empty, and
+coerce nulls to empty when setting String-valued properties.
+Furthermore you store the properties of your Data Transfer
+Objects in primitives, causing null integer columns to be
+read as zeroes and null booleans to be read as false.
+Explain."
+
+The boy replied: "In my experience, our most common production
+error is the NullPointerException.  I seek to minimize the
+occurences of this."
+
+Banzen thought a moment, then tossed a brass coin into his
+fireplace and covered it deep with glowing coals.  "Fetch
+the coin with your bare fingers," he said.
+
+The monk attempted this feat three times, but each time
+he withdrew his empty, burned fingers in pain.
+
+Banzen then grabbed the boy's upper arm, sought a particular nerve,
+and pinched deeply.  The pain stopped.
+
+"Again," ordered Banzen, still pressing on the nerve.
+
+The monk repeated his efforts.  He was pleased to discover
+that he could toss aside the coals with ease, but his
+pleasure turned to horror when he smelled and heard his own
+flesh sizzling.  Quickly he withdrew his blistered, burned
+hand and dropped the coin onto the floor.
+
+Banzen released the monk's arm and left the room.  The monk
+required no further correction, except learning to type
+left-handed.

data/data/the-codeless-code/en-qi/case-116.txt

@@ -0,0 +1,36 @@
+Number: 116
+Date: 2013-10-24
+Title: Trust No One
+Geekiness: 1
+Topics: maintainability, APIs, communication, design, refactoring, rethinking
+Names: Laughing Monkey Clan, Taw-Jieh
+Skip: 0
+Illus.0.src: Calendar.jpg
+Illus.0.title: "At least my code isn't as bad as this ancient piece of garbage HERE, written by... uh... goddammit."
+
+Several monks of the [[Laughing Monkey Clan]] found their
+brother in a state of great anguish, typing frantically at
+his workstation.
+
+"What vexes you so?" they asked.
+
+Said the monk: "When new business rules are delivered next
+year, my code will need to be updated.  Today the abbot told
+me who will be assigned this task, and my heart sank.  He is
+an impatient fool who scorns documentation and breezes by
+comments, electing instead to guess the purpose of
+everything by name alone.  Thus I must idiot-proof every
+class and method."
+
+The monk pointed to his screen. "Here he will be tempted to
+modify this object's properties, so I must make it immutable
+to prevent disaster.  Here he will surely mistake the
+purpose of this parameter, so now I must check for an
+illegal argument wherever it is used."  The monk collapsed
+upon his keyboard.  <i>"Ten thousand curses upon that
+imbecile, Taw-Jieh!"</i> he wailed.  "That he of all people
+should be chosen to maintain my code!"
+
+The other monks looked at each other uncomfortably.
+
+"But /you/ are Taw-Jieh," said one.