codeless_code 0.1.2

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

@@ -0,0 +1,146 @@
+Number: 152
+Date: 2014-07-06
+Title: What Lies Beneath
+Geekiness: 3
+Names: Yíwen, Hwídah, Banzen, Satou, Djishin, Spider Clan, Clan of the Wolf's Bitter Breath, Elephant's Footprint Clan
+Topics: Java, JDBC, databases, autoboxing, APIs
+Illus.0.src: eavesdropping.jpg
+
+Though previously inseparable, the roommates [[Yíwen]] and
+[[Hwídah]] now only crossed paths occasionally, for Yíwen's
+spare hours were occupied with the making of a
+[[#151|peculiar scarf]].  So the restless Hwídah had taken
+to exploring those few parts of the Temple grounds still unknown
+to her.
+
+Her wanderings led her to the halls of the abbey where
+dwelled the [[Clan of the Wolf's Bitter Breath]], the
+black-robed monks who performed all Temple's integration
+testing.  Developers were forbidden to trespass in this
+place, though Hwídah had never been told why, and like all
+mysteries this one gnawed at her.  She lurked in the shadows
+outside doorways and below cubicle partitions, hoping to
+learn some shocking Temple secret, but all she ever
+overheard from the black-robed monks within were loud jests
+at the expense of those developers whose code was defective.
+Most of these developers were of the [[Spider Clan]],
+Hwídah's own.
+
+"It is most infuriating," she heard one Bitter Breath monk
+complaining.  "I have selected an Order Status of 'Unknown',
+submitted the form, and all appears well.  Yet when I return
+to the form there is a validation error complaining of
+an illegal Order Status.  And the developer swears that he
+has made no changes to this page!"
+
+"Thus is it always with the Spiders," sighed another voice.
+"If anything comes too near, they wrap it in eight
+layers of Javascript, cripple its responsiveness,
+suck out its usefulness, and declare that the
+twitching corpse is a job well done."
+
+Their laughter followed Hwídah as she crept towards the
+abbey door.  /This, I shall surely investigate,/ she thought, her
+fists clenched.
+
+- - -
+
+Later that day Hwídah approached Java master [[Banzen]],
+with the fire of righteous indignation in her eyes and a
+printout in her hands.
+
+"This defect was created by a monk of the
+[[Elephant's Footprint Clan]], not ours.  He rewrote the
+method which turns each database row into an object, and his
+new code contains this..."  Here she stabbed her finger at a
+line which read:
+
+<pre>
+    order.setStatusCode(rs.getInt(STATUS_CODE));
+</pre>
+
+"Ah," said Banzen.  "I have seen such errors many times
+before.  The /statusCode/ property is Integer-valued to allow
+it to hold a null.  But in the JDBC API, /getInt/ returns the
+primitive /int/ type and silently coerces a database NULL to a
+zero.  This zero is silently autoboxed by
+/setStatusCode/ and returned by /getStatusCode/
+when the form is populated.
+And since there is no Order Status of zero,
+a valid database row will appear to be invalid."
+
+"What correction for the monk of Elephant's Footprint?"
+asked Hwídah.
+
+"Nothing lethal," said Banzen.  "My usual punishment
+involves a boat which I keep in the south gorge for just
+such an occasion.  The monk will emerge bruised and damp,
+and in the future he will examine his oars and his
+APIs a little more critically before using them."
+
+Hwídah's face turned scarlet.  "But what of the honor of
+Spider Clan?  The monks of the Wolf's Bitter Breath
+mock us openly in their abbey because of this!"  Then she froze,
+realizing that she had revealed her trespass
+onto forbidden ground, but Banzen only sighed.
+
+"The true fault lies with the authors of the venerable JDBC
+API, and with every maintainer since," said the master.
+"They gave the monk a well-used rowboat, with sturdy oars
+already mounted in the oarlocks.  Shall we doom him merely
+for not noticing that the left oar was too short?  No... the
+dunking he receives when the boat spins in the rapids will
+suffice."
+
+Hwídah bit her lip, bowed respectfully, and turned to leave.
+
+"Little nun," said Banzen, raising his index finger to stop
+her.  "The defect is not mine, and I cannot prevent the
+errors it engenders.  Thus I use both defect and error to serve
+a greater purpose."
+
+- - -
+
+At the evening meal Yíwen was not to be found, but
+Hwídah spied Banzen's two young apprentices,
+[[Djishin]] and [[Satou]], sitting together.  The pair
+agreed to hear her complaints against their master.
+
+"Banzen seems determined to suffer this same error being
+made until the end of time!" concluded Hwídah in
+exasperation.  "We should give the Elephant's Footprint
+a better boat!"
+
+"Indeed!" said Satou. "When I learned of this error, I
+begged the master to switch to a popular ORM framework.  Yet
+refactoring has its costs, and every tool has its perils,
+so the low-level code remains."
+
+"Then we should provide a left oar of our own!" said Hwídah.
+
+"Indeed!" said Djishin. "When I learned of this error, I
+authored a suitable /getInteger/ utility method.  Yet
+developers will only seek out what they think they need, and
+what they know to look for, so the utility goes unused."
+
+Hwídah sank in despair.  "So the monk of Elephant's
+Footprint is barely corrected, and the monk of the Wolf's
+Bitter Breath is not corrected at all.  At least miserable
+Hwídah has been corrected, for now I understand why it is
+forbidden to enter the Wolf's Den, and that is to maintain
+harmony between our clans.  An insult can only become a
+grievance if it is overheard."
+
+Djishin said, "You perceive the shafts of the oars
+above the water, but your true course has been determined
+by what lies beneath."
+
+Satou continued, "Our master knows you violated the edict:
+this much he has told us freely.  But the edict is not his,
+and he cannot prevent it from being violated by the irrepressibly
+curious.  Thus he uses both the edict and its violations for
+a greater purpose."
+
+Satou put a companionable arm around Hwídah.  "Enjoy
+your meal, sister of the Spider Clan!  For I fear that
+Hwídah's correction is just beginning..."

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

@@ -0,0 +1,96 @@
+Date: 2014-07-13
+Number: 153
+Title: The Red Circle
+Geekiness: 0
+Names: Suku
+Topics: schedules, management, planning, yes-men
+Credits: Many thanks to Jay Carr for the idea!
+Illus.0.src: headestal.jpg
+Illus.0.title: How to get a head in business without really trying.
+
+Master [[Suku]] and her three novices had come to a temple
+where sixty red-eyed monks were toiling frantically at all
+hours of the day and night.
+
+"How came you to this state?" Suku asked a weary monk.
+
+The monk replied, "Time and again, the head abbot promises
+many things to the provincial governor.
+   <i>Very well,</i> we say,
+   <i>but we shall need more developers.</i>
+   And the abbot agrees.
+Yet always we find ourselves with one month given to complete our work
+where two are needed.
+We fear for our sanity."
+
+"I shall speak to the abbot," said Suku.
+
+- - -
+
+The head abbot's study was half-buried under schedules,
+timesheets, and status reports scribbled over in red
+ink.  The abbot was pacing nervously back and forth.
+
+"How came you to this state?" Suku asked the abbot.
+
+The abbot replied, "Time and again, my monks tell me they
+need more developers to meet our deadlines.
+   <i>Very well,</i> I say,
+   <i>but I must beg the provincial governor for the funds needed.</i>
+   And everyone agrees.
+Yet always we deliver one feature where two were contracted.
+I fear for my head."
+
+"I shall speak to the provincial governor," said Suku.
+
+- - -
+
+The governor and her treasurer were discussing the
+treasurer's complaints about the province's accounts being
+in the red.  Since the treasurer's head had just been
+separated from his body, the conversation was slightly
+one-sided.
+
+"How came you to this state?" Suku asked the treasurer's head.
+
+The governor replied, "Time and again, the abbot
+holds my software hostage unless I give him more money.
+   <i>Very well,</i> I say,
+   <i>but for double the coins I desire double the work.</i>
+   And the abbot agrees.
+Yet always I find twice as many defects as in the release before.
+I fear the monks are insufficiently motivated, and their abbot takes me
+for a wealthy fool."
+
+"I shall speak to my novices," said Suku.
+
+- - -
+
+The novices were waiting outside the temple when
+their master returned, her cheeks flushed red with frustration.
+
+"How came you to this state?" the novices asked Suku.
+
+Their master replied, "Time and again, it is the same story.
+If we do not intervene,
+next year there will be double the monks here,
+then double that again,
+and still the provincial governor will be unsatisfied.
+I fear the abbot's eagerness to placate her
+has had quite the opposite effect."
+
+"What now?" asked the novices.
+
+"You shall speak to the abbot," said Suku.
+"Tell him Suku has devised a solution to his problem and presented
+it to the governor, who was delighted with its simplicity and frugality.
+If he wishes to set it in motion,
+send him to the governor to speak his most treasured words,
+<i>I agree."</i>
+
+"What then?" asked the novices.
+
+"Bring back his cowardly head in this basket," said Suku.
+"For if it is to roll, the sooner the better for everyone else."
+
+

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

@@ -0,0 +1,98 @@
+Number: 154
+Title: A Bridge To Nowhere
+Date: 2014-07-20
+Names: Kaimu, Zjing's Bridge
+Topics: engineering, software engineering, architecture, pride, planning, change, waterfall model, flexibility
+Geekiness: 1
+Illus.0.src: blueprints.jpg
+Illus.0.title: The word "engineering" is from the Latin ingenium, meaning "cleverness" and ingeniare, meaning "to contrive or devise".  I'd say that the phrase "clever people who contrive or devise things" applies to most software developers.  Of course, it also applies to confidence tricksters and Bond supervillains.
+Illus.0.par: 1
+
+A bridge builder was completing his inspection
+of [[Zjing's Bridge]] when he spied master [[Kaimu]]
+standing nearby.
+
+The builder said to Kaimu: "I have heard your monks
+speak of themselves as 'software engineers.'  As a /true/
+engineer I find such talk absurd...
+
+"In my profession we analyze all aspects of our task
+before the first plank is cut.
+When our blueprints are done I can tell you exactly how much
+lumber we will need, how many nails and how much rope, how
+much weight the bridge will bear, and the very day it
+will be completed...
+
+"Your monks do no such things.  They churn out code before
+your customer has finished describing what is desired.  They
+improvise, reconsider, redesign, and rewrite a half-dozen times
+before delivery, and what they produce invariably crashes or
+proves vulnerable to attack.  If I were to work in such a
+fashion, no one would dare set foot upon this bridge!"
+
+Kaimu bowed and said: "There is much our monks could learn
+from you."
+
+The master then called out to three senior monks, to attend
+the example of the bridge builder, and to hear of the
+discipline of a true engineer.
+
+- - -
+
+After the builder had repeated his argument, the first monk
+asked: "When a bridge is half-finished and the client then
+commands it to be twice as wide and two miles downstream,
+how is this accomplished?"
+
+The builder said: "We simply do not allow such unreasonable changes."
+
+The second monk asked: "When you learn upon completion that
+your industry has moved from wood to stone and is now only
+training masons, how do you refashion the many structures in
+your care?"
+
+The builder said: "We simply do not perform such unnecessary maintenance."
+
+The third monk asked: "When the force of gravity suddenly
+changes direction, or the gods decree that wood shall become
+dust and rope shall weigh as much as lead, how do you
+keep travellers from plunging into the abyss?"
+
+The builder said: "We simply do not plan for such absurd possibilities."
+
+Kaimu thanked the bridge builder, gathered the monks, and
+crossed the bridge with them.
+
+- - -
+
+When they had reached the other side, Kaimu asked
+the first monk:  "What have you learned from the bridge-builder?"
+
+The first monk said: "The determination of a true engineer
+is an enviable thing.  But if we were to work in such an
+inflexible fashion, the Emperor would surely drown us
+in our own Waterfalls."
+
+Kaimu asked the second monk: "What have you learned from the bridge-builder?"
+
+The second monk said: "The frugality of a true engineer is
+an enviable thing.  But if we were to cling so hard to
+yesterday's technology, the Web would not exist for another
+thousand years."
+
+Kaimu asked the third monk: "What have you learned from the bridge-builder?"
+
+The third monk said: "The predictability of a true
+engineer's world is an enviable thing.  But ours is a world
+always in flux, where the laws of physics change weekly.  If
+we did not quickly adapt to the unforeseen, the only
+forseeable event would be our own destruction."
+
+The first monk asked: "Master... what has the bridge-builder
+learned from us?"
+
+Said Kaimu: "Nothing yet.  But when I touch a lit candle to
+the oil I sprinkled from my lantern during our crossing, he
+will learn the reason to plan for the absurd, the virtue of
+rebuilding in stone, and the wisdom of not insulting your
+customers."

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

@@ -0,0 +1,38 @@
+Number: 155
+Title: Don't Help
+Date: 2014-07-26
+Names: Suku
+Topics: naming, design patterns, decorator pattern, adapter pattern, utilities
+Geekiness: 3
+Illus.0.src: yum.jpg
+Illus.0.title: According to the box, its main ingredient is Fish Helper Helper.
+
+Master [[Suku]] was reviewing code in a distant temple when she
+asked a senior monk to take supper with her.
+
+"I am hoping that you can help me," said Suku as she stirred
+a pot hanging over the fire.  "In your clan's code I found
+the classes SubmissionEntity, SubmissionDatabase, and
+SubmissionClient.  Although /Entity/, /Database/, and
+/Client/ are not the naming conventions of my own temple,
+your monks use them consistently, and their purpose is
+clear.  Yet here and there I have also found classes like
+SubmissionEntityHelper, SubmissionDatabaseHelper, and
+SubmissionClientHelper.  What are these /Helpers/?"
+
+"Sometimes decorators, sometimes adapters, sometimes static
+utilities," said the monk.  "Sometimes all or none of these."
+
+Suku returned with two bowls, which she set before herself
+and the monk.  In her bowl was a beautifully grilled salmon
+on a bed of saffron rice, drizzled with honey-mirin sauce
+and garnished with toasted sesame seeds and curls of green
+onion.  In the monk's bowl was only a large pink blob the
+texture of toothpaste.  It quivered slightly.
+
+"What is it?" asked the monk, poking nervously at the blob
+with his spoon.
+
+"I found it in a tumbledown market on the ragged end of
+town," said Suku, pouring herself some tea.  "They call it
+/Fish Helper/."

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

@@ -0,0 +1,81 @@
+Number: 156
+Title: The Garden Path
+Date: 2014-08-03
+Names: Suku
+Topics: design patterns, complexity, maintainability, path of least resistance, coding standards
+Geekiness: 2
+Illus.0.src: Path.jpg
+Illus.0.par: 1
+Illus.0.title: Snakes are just nature's way of playing with space-filling curves.
+
+Master [[Suku]] and her novices had come to a town that Suku
+knew from her youth.  The day was hot, and all four
+travellers were parched.
+
+"Young monk", said Suku to one of her novices.  "Fetch us
+some water from the well at the foot of this hill, and I
+will tell you of my youth in this place."  When the monk had
+done this, and all four had drunk their fill, Suku said:
+
+"In this town I was prenticed in C to a good master.  Our
+shop followed the coding standards he set down, yet always I
+felt he allowed us too much creativity.  For freedom is like
+the /kama/{{1}}: with it the skilled can reap a whole field in a
+day, but the clumsy can cut your head off.
+
+"Over time I devised an elegant set of design patterns for
+my own use.  Ah, if I could but show you now the glorious
+code I wrote!  Every constant, type, function and variable
+was named according to its purpose.  Parameters were ordered
+from most complex type to least, and the fields of structs
+were prefixed to facilitate the use of special macros I'd
+invented.  Maintaining my own code became a true joy.
+
+"I refined this system until with great pride I was ready to
+show it to my master.  I begged him to add my coding
+standards to his own, that our whole shop would benefit.
+
+"My master declared to all that it was indeed the most
+complete design and implementation metholodology that he had
+ever seen, and if the whole shop followed my example we were
+certain to produce code of unparalleled beauty, clarity, and
+extensibility.
+
+"He gave me the name /Enro/{{2}} and rewarded me with the
+honor of laying a new path in our meditation
+garden.  He designed this path to resemble a great winding
+serpent, with its tail grazing his garden gate and its jaws
+closing around a well at the bottom of the grounds.  It
+took me a month to dig the bed, level the bottom with sand,
+lay the paving stones, and set them well with gravel and
+earth.
+
+"When I finished my master said that the path, like my code,
+was a thing of sublime beauty, and decreed that his shop
+would keep it forever."
+
+At this Suku fell silent for a long time.
+
+Eventually one of her novices asked: "Is the path still
+there?"
+
+"We are seated upon the tail right now," said Suku.  "See,
+right here is my old master's gate; his house lies just beyond.
+And the water we drank is from the well between the jaws.
+Note what is on the path, and what is not."
+
+The novices' eyes followed the wriggling path up from the well
+as it swept a great meandering arc around the
+hillside.  Its stones were green with moss and beset with
+weeds.  Where the path disappeared through the gate they
+noticed that it joined a second track of bare earth, where
+the grass appeared to have been trampled so often that it
+ceased to grow.  The dusty track ran straight from the gate
+to the well, marred only by a fresh set of sandal-prints
+that went down, and then up, and ended at the feet of the
+young monk who had fetched their water.
+
+
+{{1}} A farming implement like a scythe, also used as a weapon.
+{{2}} "Garden-path".
+

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

@@ -0,0 +1,75 @@
+Number: 157
+Title: Captive Audience
+Date: 2014-08-10
+Names: Qi, Bawan
+Topics: brevity, communication, design, design reviews, detail, documentation, excess, focus
+Geekiness: 2
+Illus.0.src: shackles.jpg
+Illus.0.par: 0
+Illus.0.title: Qi was going to use the same correction on master Kaimu, but it turns out Kaimu is really into that sort of thing.
+
+Master [[Bawan]] awoke one day to find his wrists shackled
+together, and likewise his ankles.  With great difficulty he
+struggled to his feet and began to hop to his door to seek
+aid, only to fall face-first onto his rug with a loud thud.
+Looking backwards he discovered that his shackles were
+themselves chained to his bedposts.
+
+The master only lay upon the floor and sighed; for he had
+lived at the Temple many years, and such odd awakenings did
+not surprise him anymore.
+
+It was then he noticed that a great wooden barrel had been
+placed at the foot of his bed.  Squirming over to it, he
+found it filled to the very top with thousands upon thousands
+of keys.
+
+Bawan had tried no more than a hundred when the
+old scribe [[Qi]] entered without knocking and seated himself
+besides the master.
+
+"That appears tedious," observed the scribe.
+
+"It was at first," agreed Bawan.  "Then it became
+irritating, then frustrating.  But as I awoke with a full
+bladder, it has now passed on to /urgent/."
+
+"Well, do not let me distract you," said the scribe,
+producing a thick sheaf of paper.  "I had only stopped by to
+discuss the design document you asked me to review.  I must
+commend you on your level of detail: every requirement is
+captured here, as is every database table, column, and
+constraint; every screen mockup, use case, test case, and
+error case; every package, class and method; the services
+provided and the third-party libraries consumed,
+right down to the configuration parameters and instructions
+for deployment.  Your table of contents alone is three
+pages long."
+
+"I strive to be thorough," said the master, tossing aside
+another key.
+
+"It is curious," said the scribe, flipping through the pages.
+"Every paragraph will undoubtedly be useful to someone, but
+though I pored over your text for many hours I could not
+glean the simple overview of the system that I needed.  Back
+and forth through the pages I went, unwilling to give up,
+for I was certain the fault lay with my own eyes.  I
+felt... how would one put it..."
+
+"Trapped?" suggested the master, pulling another key
+from the barrel.
+
+"An excellent choice of words," said Qi.
+
+"I will prepare a suitable high-level design document for
+you, no more than a few pages with simple diagrams," said
+Bawan, fighting the chains in an attempt to cross his legs
+as he jammed the next key into each of his locks without
+success.
+
+"When it is convenient," said the scribe with a bow.  "It appears
+you have more pressing matters to attend to.  And time,
+as always, is our enemy."
+
+With that the scribe went out.

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

@@ -0,0 +1,33 @@
+Number: 158
+Title: Monday, Monday
+Date: 2014-08-17
+Names: Kaimu, Eku, Mugen
+Topics: caching, stale data, efficiency hacks
+Geekiness: 2
+
+On Monday a monk was sent to master [[Kaimu]] to inquire,
+"What is the greatest peril of caching?"
+
+Kaimu answered, "Monday is my busiest day.  Ask again
+tomorrow and I will teach you all I know."
+
+On Tuesday the monk returned and asked the same question.
+
+Kaimu answered, "Monday is my busiest day.  Ask again
+tomorrow and I will teach you all I know."
+
+
+
+== Qi's commentary
+
+If the monk had asked a different question, he would have learned nothing.
+
+
+== Qi's poem
+
+Eku asked why Mugen was rude to the shopkeeper. //
+Mugen said: That shopkeeper once sold me a broken shovel. //
+Eku dumped a bucket of water on Mugen's head -- //
+She explained: Last year my house was on fire. //
+
+

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

@@ -0,0 +1,55 @@
+Number: 159
+Title: Blocks
+Date: 2014-08-25
+Names: Jinyu
+Topics: interviews, creativity, performance reviews, promotion, career
+Geekiness: 0
+Illus.0.src: blocks.jpg
+Illus.0.title: The following day, Jinyu discovered that one of the novices had stolen a dozen blocks.  When questioned, he insisted that he had brought them to the interview on his own.  Jinyu wrote: 'Patent Applications'.
+
+Venerable [[Jinyu]], the Abbess Over All Clans And Concerns,
+was always present when novices were given their performance
+reviews -- for these reviews would determine who would
+advance in the Temple hierarchy, and how they would serve.
+Each novice was made to wait alone in a conference room
+for the senior abbots to enter, so the Abbess always left a
+pile of wooden building blocks in the room for the novices to
+amuse themselves with.
+
+Jinyu's abbot-apprentice noticed that when the Abbess
+entered the room, she would immediately glance at the pile
+and write something in her notebook.  He resolved to
+learn her algorithm.
+
+On the following day, fourteen novices were interviewed.
+
+Seven novices did not touch the pile at all.  The
+abbot-apprentice noticed that for each of these, Jinyu
+wrote: /No Promotion./
+
+Four novices had drawn blocks from the pile to build simple,
+sturdy little structures: a pagoda with a stepped roof; a
+domed hut amid triangular pine trees; an ox-cart; a
+reclining man. For each, Jinyu wrote: /Developer./
+
+One novice arranged all the blocks neatly and compactly, by
+shape and size.  Jinyu wrote: /Configuration Manager./
+
+Another novice laid the blocks out tangram-style to make a
+beautiful mosaic of a swan.  Jinyu wrote: /Web Designer./
+
+The day's final novice had used all the blocks to construct
+an elaborate tower, the very picture of elegance and
+proportion.  The senior abbots gasped when they entered the
+room, yet Jinyu wrote nothing in her book.  Her apprentice
+wrote a small note in his own book and quietly slid it in
+front of Jinyu.  His note read: /Architect?/
+
+Jinyu did not respond.
+
+When the novice had answered all questions and was
+dismissed, Jinyu walked over to the tower and breathed
+gently on it.  The blocks swayed, tipped, and clattered to
+the table.
+
+Jinyu took out her notebook and wrote: /Sales./

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

@@ -0,0 +1,33 @@
+Date: 2010-11-15
+Title: Documentation
+Number: 16
+Geekiness: 0
+Names: Seven-Clawed Blind Eagle Clan
+Topics: documentation
+
+An abbot of the [[Seven-Clawed Blind Eagle Clan]] was tallying
+the deliverables of the temple monks, when he noticed that
+a monk of the [[Laughing Monkey Clan]] had produced no
+design documents.
+
+"What if a problem were discovered in our production
+system?" the abbot asked the monk. "How would the cause be
+understood by any besides yourself?"
+
+"The code itself should be examined," said the monk. "The
+Document is a sickly beast, easily subject to the Three
+Plagues of Error: omission, obfuscation, and obsolescence."
+
+The abbot reported this to the Java master, who said: "Have
+the monk balance on one foot with his staff outstretched,
+every day from dusk to midnight.  If he can say a word to
+please me I will revoke the punishment, but not otherwise."
+
+"Is there such a word?" asked the abbot.
+
+"It is difficult to be certain," reflected the master.
+"Yesterday I was pleased by the sound of a cricket chirping
+after the first three drops of rain.  The day before, the
+plashing of milk in a pail returned me to a pleasant memory
+of my youth.  Perhaps the answer lies in the fragrance of a
+white lotus that drifted once in the pond below my window."