The Orchard
(I sometimes write little fragments of writing like this. It's not really intended for anything other than a way for me to relax and practice writing. I usually write in a single sitting and then review for obvious grammatical or content issues. My thanks to my friend Terry, whose beautiful orchard was the inspiration for this little snippet.)
It was one of those spring evenings where you could smell the crocuses and the earthworms through warm and partly sunny rain showers failing aimlessly on the newly verdant hillside. The moss had fought a valiant fight this year to claim the yard, but as the days lengthened, the sun drenched the area in an unusually bright March, and the grass was victorious, ripping through the moss until in a period of only a few days, it was hard to remember the conflict that had engulfed the turf only weeks before. The frogs were confused as the weather had been too cold, then too warm, and was just now right. Despite the early hour, some frogs through the neighborhood were croaking in their hollow, wooden sounding rattle.
It was the time of year for baseball, for running in the grass, for daffodils picked by curious children and brought in to wither on a table. It was the time when there is some hope -- that winter will not last forever, the rain will eventually stop, and that the warm embrace of summer was rapidly approaching. It was a time for opening windows, and shaking out blankets, and deciding to roll a new coat of paint to cover the stains and dings from damage over-winter.
It was into this perfect paradise of the Pacific Northwest, this veritable garden of Eden, that Jack strode through that evening. He wore, comfortable denim with an unbuttoned flannel shirt that really looked more like fall than spring. He was out inspecting the orchard.
The orchard was not a professional venture. It was not planted or maintained for the purpose of financial benefit, but rather for the purpose of enjoyment, and leisure. An orchard can be hard work, but Jack worked the orchard because he enjoyed both the labor that he applied and the reward that he gleaned.
This lovely spring evening, it was still early. The plums had been blooming for almost 2 weeks now, but most of the other blossoms were merely peeking out from green, sticky, soft unfolding buds. Some of the apples would come much later. Some of the plants were healthier than others, and Jack stopped briefly to inspect a drooping 6 year old apple tree that was oozing sap. It might be possible to heal, but it seemed to make more sense to replace. Jack might be sentimental with his friends and family, but he was a little bit more matter-of-fact with his plants.
But despite seeming to ignore the helpless plight of the weeping young apple tree, Jack loved this orchard. It was a place of refuge. A place to till and to harvest. A place that he usually worked alone. A place that he shared with others, but only when it was ready. He was generous with his yearly crop. Certainly, he used a lot of it himself between the raw fruits themselves, and the jams, preserves, pies, wines, and ciders that he made. But there was always plenty left for others and there always seemed to be some that went to waste.
And that's what orchards provided. Solitude and fellowship, work and leisure, pruning and harvesting.
On Mountains and Software
Way up in the hinterlands, miles from any other humans, two men faced each other on a rocky ridge covered in lava flows and avalanche lilies.
"It was clearly a suboptimal algorithm!" the taller man yelled, with his arms outraised.
"Everyone knows that premature optimization is the root of all evil" the short, stouter man parried. "If we had known all the details of the operational environment at the time that we had implemented the original code, we might have made different decisions, but ultimately, it doesn't matter. The code worked and the solution was a good one -- at least for the first iteration."
"The first iteration?! What is with you and iterations of software releases? Why not spend the time to do it right on the first try. Now your code is out there and it's ridiculously slow -- the whole company looks bad when you deliver crap like this."
The short man leaned against a large basalt pillar that rose almost unnaturally out of the mountain, like an ancient stella, erected to point out the glory of this lofty pinnacle. "First, make sure it works, then make it fast." he said slowly. "Let me ask you this, do you think that the company would have looked better or worse if we had spent an extra 2 or 3 weeks on the initial release to make it faster but the whole thing had a fundamental logic error?"
The tall man writhed, "Why do you assume that we would have introduced logic errors? The code was pretty straightforward, the algorithm wasn't that unique or novel. It was probably new in some sense, but really just a collection of existing algos that were assembled in a new way. What makes you think it was such a hard problem to begin with?"
"Because humans are imperfect. I'm not even saying that there aren't any logic errors in the first iteration -- err, the initial release, or whatever you want to call what I just wrapped up. What I am saying is that we're building from a more structured base. We have good confidence that it works now due to the unit tests that we put in place. Sure, it's slow, but we can always work to improve that speed; then we can regress over the unit tests to ensure that the underlying foundation is solid."
The taller fellow shifted his feet on the hillside, lava rock crunching like broken glass under his boots. "I think those unit tests are a waste of time. Out of the two weeks you spent building the solution, you spent almost a full week on those. Some testing is great and all, but come on! You spent thousands of dollars on code our customer will never see!" He shifted again and this time a clatter of jagged rocks slid down the hillside and off the edge of a cliff about 30 feet below.
"Our customer doesn't see the code for the unit tests, but it's there for us to ensure that everything's working. Tell me this, Bob: how would you have shown the customer that the code worked as they expected?"
"I would have let them watch it run -- watch it digest data and then view the results! That seems kind of obvious… how else would they accept it. Sometimes I don't get you're thinking, Fred".
Fred kicked at the base of the column he was leaning against, flattening out a section of gritty soil, flecked with chunks of lichens that had fallen from the monument he now rested against.
"The tests are nothing more than the reflection of the requirements. The function that the customer described in their requirements is accomplished and realized by the collection of the algorithms and code segments that we built and assembled. If each of the blocks of code that we assembled works perfectly with regards to its own inputs and outputs, and if the code segments are assembled in a way that logically generates the expected output from the input to the entire routine, we can safely say that we've tested the whole thing when all unit tests are green. Sure, it won't take into account the details of how much they like it overall, the architectural "goodness" of the solution, or the way it looks, the fonts, the UI, or even the speed, as you're harping about. But if you remember, the customer never gave us any non-functional requirements like what I'm talking about. What they asked for was an algorithm and that's what we built."
Bob put his hands on his hips. "So you're saying that the customer isn't going to like what you delivered, and you anticipated that, but you still delivered it?"
Fred sighed. "No, but I am saying that the customer maybe doesn't know exactly what they wanted when we started the project."
"Oh, so now you're smarter than the customer? Sounds like typical engineer ego."
Fred squatted in the hollow that he had shovelled out with his foot and leaned back against the softer, mossy base of the rock, facing north. "I may be smarter or I may not be. That's not the issue. The issue is that my job is not just to give the customer exactly what they say or to try to tease every possible requirement out of them at the beginning. My objective is to make a customer delighted with the software that I've written for them. It should meet their business needs and it should be useful, and it should be pleasant to use. That's true of all software -- that's true of all products. What my customer wants is to solve problems, and that's why they agreed to pay me money.What I am saying is that right now, my customer has a piece of software in front of them that works. I haven't said I'm done, I haven't said that the software is perfect, I've merely presented them with a quick release and asked them to take a look and then talk with me about it."
Bob dropped his arms from his sides and attempted to squat on the hillside, resulting in more lava rocks tumbling down into the ravine below. He finally settled with one foot pointed down the hill, and the other uncomfortably folded under him and pressed up against some unpleasantly sharp looking chunks of obsidian. "I just don't get it. You want to talk with your customer about slow software that doesn't look pretty and only runs in an ugly console. Don't you think they'll be pissed with what they see?"
"It depends. We talked before I started work on the project. I explained what I was planning to do. I explained that I write software in iterations. They may not be used to doing business this way, but I think that their expectations are exactly in line with what I'm giving them. They may doubt in the approach I'm taking, but I didn't lie to them and I'm not delivering anything other than what I said I was planning to deliver. They know I'm a professional, and they expect me to do my job."
Bob raised his eyebrows. "So you think they'll be OK with this? Aren't they just going to add a whole bunch of those requirements that you were talking about? Speed? How it looks? How easy it is to use?"
"Probably," Fred shrugged. "It doesn't really matter if they add those things now. Like I said, we have a solid base. If they want a different user interface, we'll add that. If they want it faster, we'll optimize it. What I'm happy about is that the code that I've just delivered actually will work. If they wanted to, they could start using it now."
Bob started to raise a hand, but the whole swath of rocks below him began to slide. Fred grabbed a branch of a small and unhappy looking Douglas fir that had managed to sprout in the crack between the basalt column and the hillside, and hauled Bob up closer to him. "Watch your step there! That hillside isn't stable at all!"
Bob muttered a thank you under his breath and sat down as close to Fred as he could comfortable position himself. Both men sat for a while, staring at across the hillside and down into the seemingly endless valleys and terrain beyond. The sun was beginning to set, and off to the west the sky was lit up with a brilliant gradient of reds, oranges, and pinks.
"Did you know that sunsets are pretty mostly because of the pollutants in the air?" Bob asked. "If it wasn't for humans burning things, the sunsets wouldn't be nearly as dramatic. I've heard that it's the imperfections in the atmosphere that give sunsets like this so much colors and variance."
Fred nodded. "I've heard that too -- not sure if it's true, but it sounds reasonable."
The men fell silent again.
"It's like switchbacks" Fred said suddenly. Bob looked up, uncertainty on his face. "What I mean," continued Fred, "is that the iterative process I'm describing is like switchbacks on a mountain. You don't just charge up or down the mountain. It's too steep,. the footing isn't sure. Better to progress from east to west, then west to east, then back again as you slowly gain elevation like we did coming up. It's slower, but it's more steady. Plus, if you're talking about a path that you've never been on before, or that hasn't been blazed by someone in the past at all, the movement back and forth gives additional perspective. As you traverse back and forth you get a better idea of the mountain you're ascending. You can see whether your path is doomed to failure or if you can realistically reach the summit. Each switchback can feel slow and painful but you're safe and you're constantly able to see what the next steps are going to be. You're constantly analyzing and re-analyzing while still making progress towards the top."
Bob looked down. "I guess I can see something in what you're saying. So you're saying that in some ways, software engineers are like sherpas, leading their customers to the summit?"
"I like that," Fred smiled. "It's a lot like that. We know that our customers want a great experience, and we're the professionals that know about how to get there. We don't want to promise them a spectacular view only to find that they were hoping to see Mt. Rainier and we we're leading them up a slope to see across the Puget Sound. We could ask them a million questions about every last detail before they begin in a questionnaire. Things like 'do you like flora more than fauna?' or 'do you prefer trees to rocks?'. But for a lot of the people that climb these hills, they wouldn't even be sure what you mean. What types of flowers are there? What types of trees? They need to experience a part before they know what they want in full. Best to give them something good soon and then tailor the rest of the hike based off of how they react to what you've given them."
Bob laughed. "I never really thought of it like that. I guess I can buy that. What about all that stuff you were talking about unit tests in code? Does that have a parallel in your analogy?"
"Well, I guess all analogies are somewhat imperfect, but I see things like tests in this case to be the safety that you build in. You may end up crossing a particularly treacherous avalanche chute, like this one, you almost slipped down. It's better to spend a few minutes either picking a really good path and marking it with a cairn. Or maybe you're crossing a creek and you spend the time to stretch a rope across to make it a bit easier to pass through. You expect in all likelihood you'll be back on this path at some point and you want to be sure that the path is safe and trustworthy. Unit tests are like that in a way. It's not really wasted time. You end up safer the first time around, and also, you have more confidence when you return."
Bob sighed. "So you think the customer will be happy?"
Fred picked himself up off the edge of the dry, dusty basalt block and stretched. "I think so, I really do." A crepuscular pika poked his head out of a hole about 20 feet away for a few seconds, saw the men, and decided to call it a night. The sun was nearly down now and the two men had a bit of a trek back to their base camp in the valley below. "You never know though, some customers are never happy. Some people will never be content. Ultimately, you can't please everyone."
Bob scrambled up, brushing dirt and shards of rocks from his pants. "I guess not." he said.
Fred turned and starting walking back down the rocky path that they had come up. He paused, as they passed the first switchback on their trip down. "You know, Bob, even though hikes aren't always as much fun as I thought they might be, and even though you end up with blisters and scratches and maybe the mosquitoes are biting, I still enjoy them."
Bob just smiled.
Branding
A part of Carl Jung's contribution to the world of psychology, is his concept of "archetypes". From Wikipedia:
In Jungian psychology, archetypes are highly developed elements of the collective unconscious. Being unconscious, the existence of archetypes can only be deduced indirectly by examining behavior, images, art, myths, religions, or dreams. Carl Jung understood archetypes as universal, archaic patterns and images that derive from the collective unconscious and are the psychic counterpart of instinct. They are inherited potentials which are actualized when they enter consciousness as images or manifest in behavior on interaction with the outside world. They are autonomous and hidden forms which are transformed once they enter consciousness and are given particular expression by individuals and their cultures.
Strictly speaking, Jungian archetypes refer to unclear underlying forms or the archetypes-as-such from which emerge images and motifs such as the mother, the child, the trickster, and the flood among others. It is history, culture and personal context that shape these manifest representations thereby giving them their specific content. These images and motifs are more precisely called archetypal images.
I read an interesting article a while back that talked about "personal brands" from this Jungian archetypal perspective.
It's a very fascinating concept. These sorts of constructs are of course nothing more than categorizing or organizing observations into containers from which we generalize. However, I think it's interesting to observe how truly some of the archetypes in the linked article are similar.
Fun stuff.
Style trumps functionality
I'm finding myself a little disillusioned by how completely and totally consumers have been trained to value style over functionality. The trend has especially hit home for me in the technical world. A demo using the latest glitzy technology automatically wins simply because of the special affects. What the developing team admits that the data is all fake and the interfaces are non-existent, the user ignores this huge gap in development simply because it looks cool. Requirement documents are better if they're visual graphs, charts, arrows, and flows rather than any real meat.
It's a reflection of our culture I suppose. We're interested in all things new, all things beautiful, all things that tickle our emotions, our senses, and our desires. 3D TV is now the rage (or maybe it's fading now...?) -- imagine, seeing movies that are a little bit more like real life. Our culture is one of vicarious, disconnected participation. Why climb a mountain when you can see an IMAX movie that shows a pro doing it?
There's also such an amazing degree of shallowness... Our conversation becomes riddled with catch-phrases, idioms, and cliches until we're hardly more than advanced, random, modern culture speech generators. We're a culture that consumes and consumes with a focus on functionality that will let us consume more -- more efficiently, and faster. We no longer climb a hill to enjoy the beauty and reflect on the Creator but to post the pictures on Flickr in order to fill out our Facebook profile with more pictures. We still create, but we create to consume again.
Is our culture purposeless beyond the next consumption high? Do we strive to make the world a better place anymore for any reason other than fulfilling our own dreams and aspirations? Where are those who will sacrifice their own good, their family's good, for a Higher Cause? Our we really as narcissistic as we seem?
We have tools available to us in life. We can develop those tools-- sharpen and refine them. Many find satisfaction in their jobs, not necessarily because of what we're accomplishing, but because it makes us feel good. We fight wars, not because there is wrong to Right but because rising oil prices will impinge our nation's ability to consume. We give our money to aid foreign countries because in the long run, it could help us. We abort humans before they see the light of day because it's messing with our plans for parenthood. We give to the church because, in our pride, we want our sect to prosper and show the world they're wrong.
So what does all this have to do with style vs. functionality?
A requirements document for any project defines the objective. It's the purpose of the project. What does it do, how fast does it need to be, what sort of interfaces need it support. It's solving a problem-- answering a need. Our culture looks at problems and finds ways, not of accomplishing them, but of making them less painful and more appealing through some spiffy styling. We let the requirement slip for speed because it really would be nicer if there was more graphical display to the user. Yeah, it will slow things down, but imagine how much more fun it will be to use! At that moment, the objective is being redefined. Our own pleasure, longings, desires, and convenience are now the focus.
For some projects, perhaps this was an objective in the first place. An iPhone's driving purpose is not to fill a previously unmet need but to make accomplishing a wide range of tasks more enjoyable and easier. In this case, the initial functionality was focused intentionally at ourselves.
The obvious question is immediately raised: What on earth am I suggesting functionality should be focused on if not improving ourselves? So what if we create to consume again?
I think the answer has to do with precisely one thing: How does one define "good"? Is something good if it makes us happy? What if it makes us happy but it makes someone else equivalently unhappy? Are "good" things, things that make everyone happy? What if happiness incompatibilities exist? Imagine there are only two people left in the world. The only thing that will make either person happy is to kill the other person. Are they both "bad" even if they both want exactly the same thing?
I think a more plausible explanation is that "good" is what is Right. Not just "right" for you or "right" for the majority, but truly Right. An absolute Right implies the existence of some sort of ultimate Requirement Document. We can take action to bring our life into line with the spec. or we can attempt to creep the Requirements here and there to make our life more comfortable.
Augmented Reality
The following is a not terribly organized set of ramblings that I had regarding augmented reality.
Just for the sake of defining what I'm talking about, Wikipedia refers to augmented reality as:
Augmented reality (AR) is a live direct or indirect view of a physical, real-world environment whose elements are augmented (or supplemented) by computer-generated sensory input such as sound, video, graphics or GPS data. It is related to a more general concept called mediated reality, in which a view of reality is modified (possibly even diminished rather than augmented) by a computer. As a result, the technology functions by enhancing one’s current perception of reality. By contrast, virtual reality replaces the real world with a simulated one. Augmentation is conventionally in real-time and in semantic context with environmental elements, such as sports scores on TV during a match. With the help of advanced AR technology (e.g. adding computer vision and object recognition) the information about the surrounding real world of the user becomes interactive and digitally manipulable. Artificial information about the environment and its objects can be overlaid on the real world.
There are different types of augmented reality, for example, the interface that is used in the movie Minority Report is a sort of augmented reality interface. More recently, Google Glass was in the news quite a bit with it's interesting wearable augmented reality device. Google's product (and in general, all "wearable" augmented reality devices are more like what I'm thinking about in terms of this article today.
The odd thing is that although I like the idea of wearable "augmented reality" in many ways, it needs to be discrete enough that basically no one but me will know if I'm running it. Part of the issue with any of this tech is that it makes humans seem less human. People aren't comfortable with talking to someone who has a visible camera aperture pointed at them. In reality, I think most people are aware that with the pervasive use of video surveillance cameras and other recording devices are already recording us on a regular basis (almost continuous basis depending on where we are) it's not a whole lot different. There's something personal about it though.
Let's say I'm talking to a friend about how frustrated I am about another person. Maybe my boss, or my teacher, or a friend who I feel has wronged me or others. In these situations, we typically feel comfortable currently because we are in a private area and the discussion can't be recorded without making it obvious. As we move forward into the future, this is going to be less of a sure thing. We will have to trust people to either not record when we ask or to keep their recordings private. This is new for us in the realm of private, face-to-face conversations but it's not new elsewhere. I forward emails that complain or whine about other people and I assume that my friends will not forward it on. (Please note: I'm not justifying my whining about third-parties with other people. This is probably a bad habit that I should break. Regardless, I still do it sometimes.)
The example above that I gave is more about gossip than anything else, but the same could be said for pillow-talk (or "revenge porn" which is becoming a thing) or even things as mundane as business decisions in a company. In the near future, recording devices and other computing resources will be small enough as to be nearly undetectable. There has to be a cultural and technological etiquette established to deal with this properly. What I mean is that in some ways, this is about being polite and civil, as well as trusting and being trusted and at the same time it will likely mean the development of tech to disable, or at least detect, the presence of devices like this in situations where we don't necessarily trust. We already have a work area that we can't bring certain devices into. This works when it's relatively obvious if you're in violation. But I think we'll see new tech that allows an area like our workplace to be ENFORCED.
 If I was more of a hardware guy, I'd be looking at a startup to do DETECTION tech for new hardware like this. Let companies like Google and Apple develop our new high-tech augmented reality devices (I can just see Apple marketing it as the iBall!). We're going to need a way for companies and people alike to feel comfortable using it. It's boring technology. Most people would be intrigued by an invisible augmented reality device because it adds value to their life (or they believe that it will). But a device that detects this same technology is more of a necessary purchase to protect yourself than anything else.
There are downsides to creating devices that are intending to identify or disable recording. For example, police or others who are actively abusing their power or authority do no want to have their deeds or words recorded despite the fact that the public should be keeping them accountable. But I still think that there's some good money to be made in this market and I'm interested to see how it develops.
Stopping by the Medicine Cabinet on a Winter Night
“Whose Tylenol is this?†I say.
It isn't mine - ran out today
They will not care, nor even hear
I pop the top without delay
Â
My hoarse throat’s longing for a beer
There’s still a ringing in my ear
And on my face, burning with heat
There streams an undesired tear
Â
A chill runs from my head to feet
I scurry back to bed tout suite
The hot and oscillating sweep
Of bedside heater warms my sheet
Â
I try to rest -- try counting sheep
But all I want to do is weep
And still the coughs keep me from sleep,
And still the coughs keep me from sleep.
Top 10 Things We Should be Informed About
I saw some recent Quora posts about the "Top 10 things that we should be informed about". The responses were mostly depressing. There is some good content and information that could be gleaned from what was said, but most of it seemed either obvious or somewhat worthless.
Many of the items people mentioned sounded like the cryptic scribblings of a self-help guru:
- Happiness is a conscious choice
- Right here, right now. Mindfulness extends life infinitely
- Self-awareness is the lubricant to all social friction
- You both need and don't need other people
They were sometimes self-centered:
- Know how to talk to rich people
- If you cannot picture your life partner making you laugh 50 years from now, bail out
Some just seemed to be a sounding-board for chips on shoulders:
- The best way to judge any religion or sect is to observe countries that it has dominated for at least a century
- No matter what you do, you will never be able to fix your parent's problems
- If you don’t get into university or if it’s just that you don’t want to go, don’t sweat it
- Being Average is OK
Some lists were at least more focused on the conventional wisdom of the day and were trying to emphasize the importance of virtues of some sort at least in a humanistic framework:
- Your health, not just now but in the future is critical. Take care of it.
- Honesty, integrity, reliability, decency, kindness, and the like, should become givens in your life where others can easily see them.
- Understand the power of science
Here is my list. I realize that this list is somewhat arbitrary and could of course be different if I were to have written this 5 years ago, 5 years in the future or even next week:
- Seek wisdom, but understand that although knowledge is important, it is not the same as wisdom
- Do good, but realize that doing good does not make you or the world a better place by itself, but you should still do it
- Love people, but know that loving is not the same as agreeing with
- Pursue truth, but realize that although truth is objective, how one believes things to be true is interpreted individually
- Respect authority, but be willing to stand up to it when it is wrong
- Live for God's glory, but be aware that you will always be fighting the temptation to replace God with yourself
- Help others, but not because you ever expect them to help you
- Question your motives, but don't be paralyzed by your imperfections
- Defend the defenseless and stand up against injustice and evil, but realize that many who you join forces with are doing so for bad or selfish reasons
- Determining your own success should consider not just this life you live now but more importantly, eternity
The Bunker [writing snippet]
“But where does it end?†Asked the child patiently. He was a young boy -- somewhere between 6 and 7 years old and still full of wonder and curiosity.
“What if I told you it went on and on for ever?†I said.
“Well -- nothing can go on and on forever… It has to have an end somewhere.â€
“What about space?†I asked, “If you go in a spaceship away from the sun, will you eventually get to the edge of something?â€
The boy rolled his eyes, “But that’s different… This is just a tunnelâ€.
“Well, it’s a long tunnel but if you must know Derek, it ends about 3 kilometers from here in another chamber  much like this one.†The room we were standing in now was quite large -- maybe 40 to 50 feet tall and a little wider. From where we stood, it basically looked as long as it was wide. One side of the room was an iron gate through which we had just entered, and the other side of the room tapered down into a vestibule and a long corridor shot off straight north of our present location. It was this passage that Derek was staring down now. And it was a bit strange. The dimensions were perfect. From where we stood, with our flashlights in hand, it was a perfectly straight line down the tunnel. The light only carried so far and limited how far we could see, but the effect of the perfectly square cut walls of the channel resulted in an effect that seemed too real to be real. I guessed it was because I was used to thinking of underground tunnels like this in terms of sewers or ancient catacombs -- functional structures and ones made with imperfect tools. But this was no sewer or catacomb. We were currently standing in a service entry to one of the most extensive bunker complexes in the world.
“How long is a kilometer?†Derek piped in, interrupting my thoughts.
“Well, it’s like a mile, but shorter.â€
“Well if it’s like a mile, why not just say a mile?†asked the curious Derek.
“Mainly because the rest of the world has got used to using kilometers and is asking us why we don’t just use themâ€, I parried.
“Well, everyone knows how long a mile isâ€, he responded. “If I walked to school, I’d have to walk one and a half miles. A mile is long but you can walk that far if you need to.â€
“The main reason, actually, is because the units are hard to work with.†Derek just looked at me blankly. “The units that we use for a mile are hard to convert to other units. Do you know how many feet make a mile?†I asked.
“A lot -- over 5,000 I thinkâ€
“Right -- it’s actually 5,280 feet in each mile. And there are 12 inches in each foot.†Those are hard numbers to work with. With kilometers, they measure it to be exactly 1,000 meters. And 1 meter is exactly 100 centimeters, and each centimeter is exactly 10 millimeters. It’s easy because everything is divisible by tenâ€. I was starting to feel a little pedantic.
“But why is it harder to remember 5,280 instead of 1,000? They’re both just numbers and they’re both pretty big. Why is it easier just because everything has a ten in it?†asked Derek.
“I don’t know -- I guess our brains just can handle it more easily. So for example, it’s harder to multiple 5,280 by 12 compared to multiplying 1,000 by 10.†I said, somewhat unsure I wanted to into detail of why multiplication by the radix of any numeral system was inherently easier. I wondered suddenly if the ancient Babylonians with their base 60 system or perhaps the Mayans with their base 20 system would feel uncomfortable trying to multiply 100 by 100. It sounded weird that they would. Stupid Babylonians. It’s there fault we’re still stuck with 360 degrees in a circle and 60 minutes in an hour.
“I guess that makes sense.†Derek said, jolting me back to the present, “But it doesn’t really help me because I still don’t really know what a kilometer is†he said, somewhat sadly.
“You and 300 million Americans.†I said, glumly.
Just to the left of the long corridor, on the concrete wall was a very large painted number indicating “27â€. According to the map that I had been looking at all morning, that was good -- service entrance 27 was what we were trying to find and it had actually been fairly easy to get this far.
I was a little surprised by the lack of any sort of security features. There were no visible locks, or mechanisms to restrict entry, no electronics visible of any kind. The iron gate to enter had been shut, but it was held simply by a latch to prevent it from swinging in the wind and probably to keep debris and larger animals from getting in and making a mess. Everywhere I looked, all I saw visible was expertly finished concrete walls.
“Well we better get going. You lead the way Derek.â€
Derek already had his flashlight at the ready and he eagerly moved forward toward the corridor. “Let’s do some exploring!†he said with a big goofy smile.
GMO
I have a modest proposal for the state legislature: I think we should pass a law that requires doctors to wear a little badge on their shirt that says "Unclean" if they fail to wash their hands at least 12 times per day. Washing your hands is good! It's almost free! And any doctor who doesn't comply with the law is obviously evil for failing to meet our arbitrary standards. Doctors will probably object to this because it's silly and also because any doctor who doesn't meet the requirement (regardless of their reason) will look really bad with an "Unclean" badge on their shirt, but that's not really important because after all they're evil (see above). It's our right to have doctors with clean hands!
Polyphylla decemlineata
Polyphylla decemlineata or the Ten-lined June beetle is an interesting little beetle. Patrick saw one of these at school (and later one at home in the backyard) and was intrigued. After digging around on the Internet and searching through quite a few varieties of beetles, we finally identified it. The one we saw did not appear to have such large antennae as some of these specimens (or perhaps they just weren't unfurled). Ours looked a bit more like the picture on the left.
These things can get kind of large for a beetle and apparently they make a hissing sound if disturbed (although we didn't try).
Twitter Updates
StackOverflow
