codeless_code 0.1.2

data/data/the-codeless-code/en-qi/applicant-4.txt

@@ -0,0 +1,162 @@
+Series: 1
+Number: 4
+Date: 2012-08-26
+Title: The Applicant
+Part: 4
+Geekiness: 1
+Subtitle: The Bundle
+Names: Aaradhya, Tarun, Bhupendra
+Skip: 0
+
+The old man's name was Bhupendra; his grandson was Tarun.
+
+They had no other relatives in the village.  The boy's
+father lived in a distant city, working long hours at a
+menial job and sending home a little money every week --
+although Bhupendra suspected that a good deal of his
+son-in-law's salary was wasted on palmyra wine and online
+gambling.  Other than a small hovel their chief possession
+appeared to be the dust-gray female donkey which the
+grandfather now loaded up with rice, bread, dried
+vegetables, jugs of water, knives, cook-pots (of various
+sizes), rope, kindling, a bolt of heavy cloth, and an
+ancient laptop too slow to run even the most stripped-down
+window manager.
+
+"Why are you packing so much?" asked Aaradhya, irritated
+that the day was fast slipping away.  "You will be in Reechee
+and back before half this food can be eaten."
+
+"Perhaps," said the old man, tying another pan to the
+immense bundle on the donkey's back.  "In my long life, I
+have often found that it is better to over-engineer than the
+opposite."
+
+"And the laptop?  The batteries alone are heavier than the
+kindling."
+
+"You will be teaching the boy.  You need a computer."
+
+"I doubt it can go a few hours without a charge, much less a
+few days."
+
+"Perhaps."
+
+Aaradhya fell silent.  How /was/ she to teach Tarun while
+they walked?  In her home town, when dust seized up the
+engines of the electrical plants (which happened frequently
+in summer, bringing down the power for hours at a time) her
+old master cheerfully distributed bundles of paper and pots
+of ink, lecturing to his apprentices by lamplight in front
+of a slate wall that he wrote upon with chalk.  The nun had
+only her voice, which would crack within minutes in the dry
+dirty air.  Only a fool travelled with an open mouth on
+rural roads.
+
+Yet that paled before a bigger problem.  Aaradhya had been
+the youngest of four children and the newest of seven
+apprentices.  She had never instructed anyone in anything.
+She had no idea where to start.  Beyond Anantha's Fountain
+her own lessons were a vague blur.
+
+Meanwhile, grandfather and grandson continued to tie
+ever more onto the back of the unprotesting donkey.
+It was almost evening before they were underway.
+
+- - -
+
+"Teach," said the old man.
+
+Aaradhya began with the little scraps she remembered
+learning at her grandmother's knee.  Stories of the earliest
+computers: towering mechanical contrivances of jointed
+sandalwood beams rotating on thick axles and strung together
+with miles of hemp.  Ivory-inlaid push-pegs drove creaking
+AND and NOT gates as big as a full-grown man and twice as
+heavy, with the gates in turn stacked in tiers a full
+four stories high just to implement a simple multi-bit
+adder.  Entire temples were built to house the precious
+workings, with a dozen monks perpetually clambering up and
+down ladders, oiling, tightening, tuning, repairing, and of
+course operating the gargantuan framework.
+
+Then she told of the wondrous Age of Brass, at the dawn of
+the Babaj Empire, where programming was done with clockwork
+clusters of gears that grew smaller with each passing
+generation.  Strange pale men came from the West to learn
+this art, augmenting it with their own arcane practices --
+such as the use of rubies in the mechanism to overcome
+friction-induced wear, and coiled springs to drive the
+crankshafts, and the ritual practice of imbibing
+stimulant-laced beverages before commencing with a day's
+work.
+
+Tarun's grandfather noted the absent expression on the
+boy's face.  Scowling, he drew alongside Aaradhya.
+
+"Teach," he repeated.  "Programming, not history."
+
+Aaradhya grimaced.  Her BASIC was out of date; Tarun
+probably knew more of the modern form than she did.  Logo?
+She had forgotten practically every bit of it.  Anyway the
+language could not be taught without the use of a specially
+trained turtle.  Her apprenticeship had been in C with a
+sprinkling of C++, but the boy was not ready to be thrown
+into a swamp teeming with Bus Errors and Segmentation
+Violations and special syntaxes for working with L-values.
+Java was foremost on her mind these days: it was, after all,
+the chosen path of the Temple of the Morning Brass Gong.
+Reiterating the fundamentals of the language would help
+gather her thoughts, soothe her nerves, prepare her for her
+interviews.  She should teach the boy Java.
+
+While walking in the dark?  Ridiculous.
+
+Not to mention that the incessant clanging of the pots on
+the donkey's back wasn't helping Aaradhya organize
+her thoughts.
+
+"The animal needs watering," said Aaradhya quickly.  "While
+we can still see the stream.  I'll begin when we're back on
+the road."
+
+This forced them to leave the moonlit road and pick their
+way down a treacherous weed-choked gully to the meager
+trickle flowing at the bottom.  On the climb back up the
+donkey put a foot down into an unexpected burrow-hole,
+throwing her off balance.  The huge bundle swayed too far to
+one side.  The beast brayed, the harness rolled, then the
+bundle went crashing onto the underbrush, pinning the
+animal.  By the time they had calmed the donkey the moon had
+set.  There was no sensible choice but to make camp for the
+night.
+
+Bhupendra sighed and settled his old bones against the
+fallen bundle as Aaradhya and Tarun gathered the various
+items that had rolled away from it.  Even by starlight
+Aaradhya could see the hard gleam in the old man's eye.
+
+"Teach," he commanded.  "No more delays."
+
+Aaradhya took a step towards the old man, about to argue for
+a fresh start by daylight, when she slipped on something
+smooth and landed fullsquare on a low thorny bush.  The next
+word that came out of her mouth was fortunately muffled by
+her twisted robes.  Feeling around in the blackness
+Aaradya's fingers closed on the handle of the offending
+object: an iron skillet that had come loose from the bundle.
+It was heavy.  That was when the idea came to her.
+
+The young nun brushed herself off.  Smiling, she advanced
+towards the old man and the boy.  They were both on the
+ground by the bundle; she loomed above them.  With a wide
+stroke Aaradhya brought the iron skillet up high, then down
+hard on her target.
+
+The rock was undamaged, but the skillet rang out like a
+gong.  Both her fellow travellers jumped in spite of
+themselves.  The donkey whined but was tied to a tree and
+could not bolt.
+
+"School is in session," said Aaradhya.  "We shall begin
+with Objects..."

data/data/the-codeless-code/en-qi/applicant-5.txt

@@ -0,0 +1,68 @@
+Series: 1
+Number: 5
+Date: 2012-09-23
+Title: The Applicant
+Part: 5
+Geekiness: 2
+Subtitle: The Iron Cookpot
+Names: Aaradhya, Tarun, Bhupendra
+Skip: 0
+
+The next day dawned bright and sticky-warm.  Bread was shared, the
+donkey was watered and re-laden, and the trio set out into
+a morning buzzing with insects.
+
+"Imagine," said Aaradhya, "that you have journeyed far from
+home and found yourself in a strange village of shopkeepers.
+It is evening, and you are hungry.  You learn that the cook
+will serve you stew but requires red lentils, curry leaves,
+and water in trade; the farmer will give you the lentils but
+requires seeds and the loan of an ox..."
+
+In Aaradhya's hypothetical village there were also merchants
+who controlled warehouses brimming with all manner of useful
+things, items produced by some shopkeepers and needed by
+others -- precious spices, planks of sturdy wood, fine saws,
+barrels of lamp oil.  The merchants belonged to a respected
+guild called the /DAO/.
+
+"Domestic Archive Overseers," explained Aaradhya.  "Their
+sole function is to store, manage, and retrieve Valuable
+Objects..."
+
+As she spoke Aaradhya untied various odds and ends from the
+bundle on the donkey's back, using them as props.  Tarun
+listened.  The grandfather walked ahead of them with his
+parasol, saying nothing, although sometimes he would nod or
+shake his head.
+
+When they stopped for a meal he pulled Aaradhya aside.
+
+"You teach by metaphor."
+
+"It is how my C++ master taught.  He used to say: <i>a
+software system is a civilization of objects.</i>"
+
+"Very pretty.  But when the boy interviews for an
+apprenticeship they will not ask him to recite proverbs.
+He must know how to build things."
+
+Aaradhya waved to the boy, who was feeding the donkey.
+/"Tarun,"/ she called.  "You are now the mayor of our little
+village.  Wealthy strangers will soon arrive in town to buy
+iron cookpots: which of our shopkeepers shall make them?
+The carpenter, who already makes pot-handles?  The jeweler,
+who already crafts with metal?  The potter, who already
+makes pots of clay?"
+
+"None of these, Madam," said Tarun.  "The village needs an
+ironmonger."
+
+"Please tell your grandfather why."
+
+"Because no one seeking an iron cookpot will think
+to ask a carpenter."
+
+Aaradhya turned to the grandfather, a satisfied smile
+playing at the corner of her mouth.  "Much of what he needs
+to know already lies within him.  The rest is just syntax."

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

@@ -0,0 +1,30 @@
+Date: 2010-11-03
+Title: The Small Stuff
+Number: 1
+Geekiness: 0
+Topics: perfection
+Illus.0.src: foot.jpg
+Illus.0.title: Asking the Java master why bare feet are prohibited in the temple usually results in the same answer.
+
+For three days and nights the Java master did not emerge
+from his cubicle.  On the fourth day the monks of the temple
+sent a novice to inquire after him.
+
+The novice found the master at his whiteboard, contemplating
+a single dataflow diagram.  The novice recognized it as a
+minor component of the vast system that the monks were
+contracted to maintain.  Politely, the novice asked what the
+master was working on.
+
+The master replied: "There is a defect, and I am considering
+the best way to repair it."
+
+The novice said, "You preach often about the importance of
+setting priorities.  How, then, can you obsess about
+something so tiny and unimportant?"
+
+Without saying a word, the master raised his staff and
+brought it down hard upon the bare left foot of the novice,
+breaking his smallest toe.  The novice screamed in pain and
+staggered from the cubicle.  In that moment, the novice was
+enlightened.

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

@@ -0,0 +1,65 @@
+Title: Pride
+Date: 2010-11-11
+Number: 10
+Geekiness: 1
+Topics: reuse, pride
+Names: Elephant's Footprint Clan
+
+After a cursory inspection, the Java master decreed that
+each monk in the [[Elephant's Footprint Clan]] would henceforth
+catch his own fish, harvest his own rice, sew his own robes,
+and cobble his own shoes.
+
+Within a month, the monks were half-naked and severely
+malnourished.  Deadlines began to slip.  The abbot implored
+the Java master to reconsider his decision.
+
+"Very well," said the Java master.  "Every Thursday, have
+them also burn their robes and shoes, and cast their rice
+and fish into the river."
+
+The abbot asked what transgression his clan had committed
+to merit such punishment.
+
+"Punishment?" said the Java master.  "I intended only to
+reward.  Do not the monks of the Elephant's Footprint relish
+their independence and self-sufficiency?  Their code tells
+me as much:
+
+"Each has authored essentially the same Data Access Objects
+and Value Objects as his neighbors.  Each has crafted his
+own String utilities and configuration file parsers.  Each
+has taken exquisite pains to design, implement, integrate,
+test, debug, repair, and extend that which he might merely
+have consumed from one of his brethren.
+
+"Shall I infer incompetence?  If so, then every last monk of
+the Elephant's Footprint must be cast out of the monastery.
+
+"Shall I infer willful ignorance?  If so, tradition demands
+that they blind themselves with nettles, and /then/ be cast
+out.
+
+"Shall I infer contempt for the preciousness of time?  If
+so, the dungeons await...
+
+"But no," concluded the Java master.  "I shall instead infer
+pride -- pride taken by each that his code is superior to
+that of his brethren.  Pride is one of the Four Seeds of
+Greatness, and must be encouraged.  Let the Elephant's
+Footprint hone its skills with shears and spears, with
+needles and sickles, until every monk may be likewise proud
+of his fine robes and the bounty on his plate!"
+
+"There will be little time left for coding," observed
+the abbot.  "And the Emperor is quite literal in his
+interpretation of the word /deadline/."
+
+The master nodded.  "The merchant, lately ruined, knows only
+the pangs of loss.  Whereas the old hermit extols the
+virtues of austerity, and will not change his state.  Yet
+are these not the same man, separated only by a gulf of
+years?"
+
+Thus was the Elephant's Footprint spared twice and
+corrected.

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

@@ -0,0 +1,28 @@
+Number: 100
+Title: Ten Thousand Mistakes
+Date: 2013-06-24
+Names: Banzen, Suku
+Topics: improvement, authority, perfection
+Geekiness: 0
+Illus.0.par: last
+Illus.0.src: Abacus.jpg
+Illus.0.title: There are now abacus apps for tablet computers, in case you want to use your state-of-the-art processor for performing manual calculations.  I find that strangely beautiful.
+Illus.0.align: centered
+
+
+A novice asked master [[Banzen]]: "What separates the monk from the master?"
+
+Banzen replied: "Ten thousand mistakes!"
+
+The novice, not understanding, sought to avoid all error.
+An abbot observed and brought the novice to Banzen for
+correction.
+
+Banzen explained: "I have made ten thousand mistakes; [[Suku]]
+has made ten thousand mistakes; the patriarchs of Open Source
+have each made ten thousand mistakes."
+
+Asked the novice: "What of the old monk who labors in the
+cubicle next to mine?  Surely he has made ten thousand mistakes."
+
+Banzen shook his head sadly.  "Ten mistakes, a thousand times each."

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

@@ -0,0 +1,55 @@
+Number: 101
+Title: Accountability
+Geekiness: 1
+Names: Yíwen, Hwídah
+Topics: accountability, production support, teamwork
+Date: 2013-07-05
+Illus.0.par: 2
+Illus.0.src: Door.jpg
+Illus.0.title: Five storeys under solid stone, made of four-inch thick reinforced oak beams clad in iron.  And it still doesn't keep out spam.
+
+
+One morning the Temple found itself flooded with calls from
+panicked users, claiming that they had received erroneous
+emails from a particular billing system.  The emails alleged
+that payments were now a year overdue, and regrettably the
+users' heads were forfeit.
+
+Temple abbots gathered in the courtyard, debating how best
+to locate the source of the problem before the Temple's entire customer
+base disappeared into the mountains to escape the executioner's axe.
+
+"There is no need," said the nun [[Hwídah]] from the edge of
+the courtyard.  "The shame is my own.  In our last
+maintenance build I carelessly modified a boolean expression
+in the accounting module, causing it to return false when the
+proper answer was true.  I have now corrected the defect,
+and the spurious emails have ceased."
+
+Hwídah was banished for two months to the dungeons below
+the Temple's deepest archives, where alone she would inspect
+mouldering printouts of old COBOL scripts for possible defects.
+
+After a week the nun [[Yíwen]] came to replenish the prisoner's
+allotment of cold rice.
+
+"Forgive my puzzlement, Hwídah," asked Yíwen as she pushed a
+tray under the cell door, "but why did you admit your fault
+after correcting the error?  Had you remained silent the
+cause would have escaped detection for many days, by which
+time the Temple would have turned its attention to more urgent
+matters.  Your involvement could have remained unknown forever."
+
+"Tell me, Yíwen," said the prisoner, "what chaos would ensue
+if /all/ the modules in our system occasionally returned
+false when the proper answer was true?  And when I say
+<i>[[#70|system]],</i> what picture does the word make in your
+mind?"
+
+Hwídah slid the empty tray back under the door.  "On that
+morning, when the horror of my error was revealed to me, so
+too was this understanding: we are all a part of the system.
+It is an extension of our desires, our efforts, and --
+lamentably -- our flaws.  If I were to let my fellows waste
+precious hours searching for a defect that I had secretly corrected,
+I would only have failed the system a second time."

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

@@ -0,0 +1,41 @@
+Number: 102
+Title: Paddle
+Geekiness: 1
+Names: Suku, Banzen
+Topics: maintainability
+Date: 2013-07-12
+Illus.0.src: Paddle.jpg
+Illus.0.title: It makes awesome rice, though... trust me.
+
+While it is seldom seen by novices, on occasion the masters will
+correct each other:
+
+Masters [[Banzen]] and [[Suku]] were planning the next
+release of a large and critical system.  Together they
+iterated through the list of requirements, allocating
+work to various monks in their charge.
+
+"Assign that task to me," said Banzen at one point,
+"for I wrote the original code, and it is somewhat complex
+and sensitive."
+
+He repeated the phrase for a number of other items.  This
+had been his habit for as long as Suku could remember; for
+Banzen toiled as hard as the monks half his age, and he took
+great pride in his work.
+
+Suku posted the list of assignments the following morning.
+Banzen happened to glance at it during breakfast, and
+discovered that the tasks he'd chosen for himself had
+instead been assigned to a handful of junior monks.
+
+Banzen confronted Suku at her table.
+
+"You have been at this temple for twenty years," he fumed.
+"When will you stop giving our precious rice to cooks who
+have barely learned how to hold a paddle?"
+
+Suku calmly placed her chopsticks across her bowl.
+"I cannot say," she replied.  "When will you stop
+fussing over your little rice pot and make simpler
+paddles for those cooks?"

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

@@ -0,0 +1,64 @@
+Number: 103
+Title: The Black Enamel Box
+Geekiness: 2
+Names: Bawan
+Topics: production support, logging, code rot
+Date: 2013-07-21
+Skip: 0
+
+
+Master [[Bawan]] posed this dilemma to the developers
+in his charge:
+
+"When investigating strange behavior in the production
+environment, our most powerful weapon has always been debug
+messages: the more numerous and detailed, the better.  Yet
+when used copiously, the formatting of such messages becomes
+expensive -- /needlessly/ expensive, for we exclude debug
+messages from our logs when we are not 
+investigating problems.  So which path is best?  Safe but
+slow, or heedless but fast?"
+
+<i>"Wú,"</i> said one of the nuns.  "Everything may be
+logged, with minimal expense.  Wrap every /debug/ call
+within an /if/ statement which verifies that debugging is on
+before bothering to format the message.  We will only be
+slow when we need to be safe."
+
+Bawan considered this, and seemed pleased.
+He bade the nun implement her approach in an application
+that was presently being designed.  As further reward for
+her cleverness he presented her with two enamel boxes.
+
+"Open the red box immediately," said Bawan, "but leave the
+black box shut tight.  In time it will serve you."
+
+Inside the red box the nun discovered a small bowl full of
+succulent kiwi fruit, lychee, and white pears, resting on a
+bed of goji berries.  These she enjoyed greatly that
+very evening.  Afterwards she placed both boxes on a high
+shelf, and eventually forgot about them.
+
+- - -
+
+Two years later, after the system had undergone several
+enhancements, a minor production problem appeared --
+the first in many releases.  The nun requested that the
+system be restarted in debug mode.
+
+Suddenly, stack traces from NullPointerExceptions appeared
+on the screens of every user.  The system had become completely
+unusable.  As the nun stood aghast amid the chaos,
+master Bawan sidled up to her and whispered, "Now fetch the
+black box."
+
+When the lid was lifted a foul odor issued forth.  Inside
+lay a small bowl filled with the mouldy, dessicated remains
+of what appeared to have once been kiwi fruit, lychee, pears and
+goji berries.
+
+The nun requested that debug mode be turned off
+and then closed the box, enlightened.
+
+
+

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

@@ -0,0 +1,52 @@
+Number: 104
+Title: Guardrails
+Geekiness: 2
+Names: Spider Clan, Laughing Monkey Clan, Suku
+Topics: APIs, type safety, documentation
+Date: 2013-07-28
+Skip: 0
+
+A certain monk of the [[Spider Clan]] was attempting to use
+an email client library written by [[Laughing Monkey Clan|Laughing Monkey]].
+The message he wished to send with it was simple, yet no matter how
+he tweaked his code the library either failed quietly or
+threw puzzling runtime exceptions.
+
+The monk arranged a meeting with the author, wherein he politely
+expressed his frustration.
+
+"Lamentably, the fault is your own," replied the author with
+a bow.  "Had you read the copious documentation I provided,
+you would have known that attachments should only be added
+/after/ setting the message body.  And while the /setMessageText/ method
+does accept an untyped Object,
+the Object you provide must either be an array
+of Strings, a DomNode, or a BufferedInputReader.  Also, you failed
+to note that certain destination addresses are silently ignored..."
+
+The author continued on in this fashion, showing how the monk
+could have avoided each pitfall.  Thus the monk returned to
+the Spider Clan's abbey, suitably chastened.
+
+Master [[Suku]] heard of this and summoned the author.
+
+"I have read your documentation," said Suku.  "It is indeed
+the very model of thoroughness, worthy of emulation.  Please
+take this hardcopy to the abbot, that others may learn from it."
+
+The author followed Suku down to the abbot's chamber and
+pushed against its heavy door with all his might.  When the
+door finally burst open the monk leaped backward in terror,
+for beyond it lay a sheer drop into blackness.  His startled
+cry echoed against stone walls; the sound of water could be
+heard lapping far below.
+
+"There is a ledge to your left, about as wide as your foot,"
+explained Suku.  "Edge carefully around until you come to
+the opposite side of the well.  There you will find
+iron rungs set into the wall, leading down to the waters
+where [[#67|the abbot's bones]] await you.  Take note:
+the ledge is slippery from damp, every third stone is set a
+few inches higher, every fifth is set lower, and every seventh
+is missing entirely.  But if you keep all that in mind,
+the way is quite straightforward."

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

@@ -0,0 +1,43 @@
+Number: 105
+Title: Navigation
+Date: 2013-08-03
+Geekiness: 1
+Names: Banzen
+Topics: design, documentation, planning
+Illus.0.src: Map.jpg
+Illus.0.title: Actually, he burned the maps because the Temple gave him a phone with GPS.  But you get the point.
+
+A young nun approached master [[Banzen]] and said:
+
+"When first presented with requirements I created a rough
+design document, as is our way.
+
+"When the rough design was approved I began a detailed
+design document, as is our way.  In so doing I realized that
+my rough design was ill-considered, and thus I discarded it.
+
+"When the detailed design was approved I began coding, as is
+our way.  In so doing I realized that my detailed design was
+ill-considered, and thus I discarded it.
+
+"My question is this:
+
+"Since we must refactor according to need, and since all
+needs are known only when implementation is underway,
+can we not simply write code and nothing else?  Why must we
+waste time creating design documents?"
+
+Banzen considered this.  Finally he nodded, saying:
+
+"There is no more virtue in the documents than in a handful
+of leaves: you may safely forgo producing either one.
+Before master Mugen crossed the Uncompiled Wasteland he made
+eight fine maps of the route he planned to take.  Yet when
+he arrived at the temple gates he burned them on the spot."
+
+The nun took her leave in high spirits, but as she reached
+the threshold Banzen barked: "Nun!"
+
+When the nun turned around, Banzen said:
+
+"Mugen was only able to burn the maps because he had arrived."

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

@@ -0,0 +1,49 @@
+Number: 106
+Title: The "I" In Team
+Date: 2013-08-15
+Geekiness: 0
+Names: Jinyu
+Topics: accountability, pride, encoding
+Illus.0.src: Jinyu.jpg
+Illus.0.title: Everyone at the Temple lives in dread of the day when she needs a wheelchair instead of a cane.  Getting hit with a wheelchair REALLY hurts.
+
+A certain monk was known throughout the Temple for his
+humility.  When discussing flaws in his clan's software he
+always took personal responsibility, yet when receiving praise
+for marvelous features crafted by him alone, he always gave
+credit to the entire team.  Eventually word of the monk came
+to old [[Jinyu]], Abbess Over All Clans And Concerns.
+
+"So," she said to her chief abbot, "this monk says <i>I failed</i>
+after the defeats of others, and <i>we triumphed</i> after his own
+victories?"
+
+"So it is said throughout the Temple," said the abbot.
+
+"Bring him to me," commanded Jinyu.
+
+When this was done, Jinyu surprised all in attendance by
+striking the monk with her cane and sentencing him to thirty
+days' hard labor in the data mines.  After the stunned monk
+had been taken away the abbot nervously approached Jinyu to
+inquire the reason.
+
+Jinyu struck the abbot.  "Fool!  Consider the monk's algorithm.
+When he says <i>I failed</i>, what is most probably the truth?"
+
+"That others have failed," said the abbot, flinching.
+
+Jinyu struck him again. "And when the monk says <i>we triumphed</i>,
+what does he most likely mean?"
+
+"That victory was his alone," said the abbot, wincing in pain.
+
+The ancient priestess twirled her cane overhead, so fast
+that the very air whined in anguish, until with a
+thunderclap she brought it down hard on the floor
+in front of the terrified abbot.  "The only thing
+praiseworthy about this boastful monk is that he has
+mastered the art of one-to-one mapping.  Meanwhile, what am
+I to do with the rest of you idiots?  You were
+deceived by a simple substitution cipher <i>that your brains
+had already decoded</i>."