Questions we don’t ask

January 14, 2009 under curios, personalinthepubliceye

It’s not that John didn’t want to talk to his wife when he came home from work. It’s just that he didn’t feel… well, he just didn’t feel particularly talkative. He was sure that Sheila didn’t mean to be bothersome, but she sure picked some strange things to talk about.

Tonight’s victim of scrutiny was his colleague Bob, and the inquisition was severe. Poor absent Bob’s character, habits, and history were laid bare. John tried valiantly to keep up with the incessant demands for information and (he thought) he was actually doing pretty well.

Pretty well, that is, until the question that floored him.

“John… what colour are Bob’s eyes?”

“His eyes? 

“Umm…”

“You worked with the man for 20 years and you don’t know what colour his eyes are? You shared a bunk for a week during The Team 2000 challenge and never noticed?”

“I guess I never asked him. They’re a, kinda murky colour, I guess. Like a grey or a brown or a blue, I think.”

“John, what colour are my eyes?”

John looked up; she’d squared her back to him, arms crossed defiantly. He scanned the room desperately in the hopes of mirror,a window, a ridiculously shiny table-knife, anything!

John slept on the couch that night.

Sometimes we just don’t ask

Our world runs on assumed knowledge of all shapes and sizes.

If it’s life and death knowledge, you must know it, because otherwise you’d be dead.
If it’s important knowledge, (don’t ask her about her weight) you probably received immediate feedback and knew it the second time round.
If it’s popular trivia, you probably heard it somewhere.

Sometimes our assumptions of knowledge are wrong.  People arrive from different backgrounds, different cultures and shatter our ideas of what “everyone knows”.

There’s a more fundamental principle at play. If you don’t encounter something, you don’t know about it. If you don’t ask, you don’t know. Sometimes the (perceived) importance or prevalence of a thing means that we ask questions quickly.

What really got me thinking about this was that I was looking at the questions of a spiritual/emotional inventory worksheet. I was thinking, “Cheesy!” until I realized that it was full of questions I never ask. I wasn’t sure of the answers.

If I never ask the question, how will I ever know?

comments: 0 »

Crossword fun – Random thoughts

January 10, 2009 under tongueincheek

Crosswords are a great example of problem solving. If you want to build a framework for understanding problems, crosswords are a very good place to start.

Crosswords are problems we solve for fun. We may learn a little bit from them, but most of the benefit we derive comes from the experience of solving them. It feels good to solve a problem. People don’t usually have fun solving a problem which is too simple (boring) or to difficult (frustrating). It’s fun to tackle problems that push, but don’t exceed (if we’re willing to invest a little thought/effort) the scope of our ability. We generally call this range of difficulty “challenging.”

Crosswords are, generally speaking, fairly well specified problems. A crossword is heavily, but not completely constrained. The author has a specific solution in mind, and gives enough clues to describe that solution well.

A fun game

If you want to pose yourself a real challenge, try and solve a crossword multiple ways. Solve it, then try and find a different solution which still satisfies all the clues. Is there any portion of the grid for which the clues could possibly be satisfied by a different combination of words?

Probably you won’t be able to find another solution, but it really depends on the puzzle in question. Crosswords are written by people, and people aren’t perfect. If some of the clues are vague or ambiguous, you may be able to come up with a valid solution that they never imagined. English is an enormous language with many esoteric words that they might not have been thinking of ;-)

Particularly, if the crossword is loosely connected, you may be able to find a couple words you can swap out.

How else could you describe a crossword?

Most problems can be described in many different ways. You can describe any crossword without a grid, if you want to, by describing the constraints enforced by the grid in a different way. E.g.

Word 1:
Anger
4 letters
Letter 2 is the same as letter 4 in Word 7

Word 2
comfort or encouragement
6 letters
Letter 3 is the same as letter 1 in Word 4
Letter 6 is the same as letter 2 in Word 3

etc, etc, etc.

This description is more flexible than a grid. Any grid crossword could be described like this, but not every crossword that you could describe like this will fit in a grid. For example, the crossword with:

Word 1
Farewell!
3 letters
Letter 1 is the same as letter 2 in Word 4
Letter 2 is the same as letter 4 in Word 7
Letter 3 is the same as letter 4 in Word 6
Letter 3 is the same as letter 1 in Word 2

Letter 3 is constrained twice, which is not impossible (but it does mean that letter 4 in 6 and 1 in 2 must be the same letter, in this case, “e” for “Bye”) The puzzle is not logically inconsistent, but there’s no way to draw that configuration on a 2D grid. It could be drawn on a three way grid.

You could describe a crossword by focusing on the letters, giving each populated (letter) square a number:
E.g. a 10×10
Clue one: letters 1,2,,3,4
Clue two: letters 2,12,22,32

Again, this is more flexible than the grid.

If Software Engineering was a Crossword Puzzle

Another fun form of problem solving is software development and design. Let’s see how it compares with crosswords by imagining we solved crosswords the same way we design software packages shall we?

The newspaper would only have a portion of the crossword grid graphically displayed. Different clues of the crossword would be printed on different pages of the newspaper and you’d have to piece the crossword description together yourself.
Clues would look like:

4 Down: A few letters long. Should rhyme with orange. Postpone until Version 2.
7 Across: A synonym for hippopotamus.
10 Across: Talk to Bob in Accounting.
9 Down: This word should fill the 9 down slot.

Rather than the newspaper posting a solution, you would submit yours to them for approval/disapproval. You would include some notes, like,

“You said that 4 down should be postponed until version 2, but 8 across depends on 4 down, and you’ve marked it high priority.”
“Elephants and hippopotamuses are genetically very very similar.”

Sometimes you would add words to the puzzle that you thought were nifty words, on the off chance that the newspaper would adopt them as solutions.
The newspaper would respond to your solution and tell you which answers were incorrect. You would then resolve the puzzle based on their feedback. This back and forth would continue until you came up with something that they liked, or until they were too tired to argue about it.

comments: 1 » tags:

Freaky Far Out

January 7, 2009 under metablogging

…stuff happens at the freakonomics blog.

I’ve been reading it for a while but it’s only now going on my blogroll.

comments: 0 »

The way of the geek.

January 7, 2009 under curios

Sometimes, people call me names. I watch a group of people, huddled tightly, and I hear their furtive murmurs. They’re working up the courage to approach. Eventually, one of them does.

Excuse me, I don’t mean to intrude, but are you a…, what I mean to say is, that George said you were a…”

A computer person? Yes, I am. That is to say, people call me that.

Mind you, I don’t exactly understand why they call me that. On an average day, I often spend upwards of 14 hours away from a computer. You may as well call me a “sleep person”, “food person” or “ride the bus in the deathly silence of Canadian early-morning public transit person”.

After calling me names, people invariably ask me questions. Computers run slowly, programs run amok, and internet shenanigans sow chaos and confusion; these are all cinders to spark the flame of inquisition.

I never know the answers. Sure, I can figure out the answers, given access to a computer, but off-hand? No.

Every “computer person” has one answer to everything.  It’s the secret to their power. In the fairy tale, the giant, for safekeeping,  hid his heart in a stone in a box in the wilderness: and this was the source of his invulnerability.

Geeks have a similar tale of invulnerability, although our hidden heart lies not in a wilderness chest.

No, it’s called Google, and it’s hidden in plain sight. Samson, shorn, could never have been weaker than a geek without Google access.

This leads to interesting times when people ask questions of computer geeks. To the old phrase, “It never hurts to ask,” geeks counter with the adage, “Teach a man to fish”. Googling is something that anyone can do. It doesn’t take a computer person and geeks have turned this revelation into an art form.

For example, what if someone wants to know about passive-aggressive behaviour?

The Christmas Ham

January 6, 2009 under tongueincheek

…is a fine example of risk analysis.

Is it still okay after all that time in the fridge?

If it’s edible, I should be trying as hard as I can to finish it off before it spoils.

On the other hand, if it’s spoiled, the last thing I should be doing is consuming large quantities in a short period of time.

There’s no room for hedging; sometimes with questionable food, like project deliverables, ya just gotta make the call.

comments: 0 » tags: , ,

Authorship

January 5, 2009 under thehumancondition, theology

Computer programming is a funny activity; it’s not straightforward to describe. Programmers, bloggers and academics have spilled a lot of text in trying to best explain what goes on when you program a computer.

It has aspects of design; it has aspects of writing; it’s a creative process. You come up with the steps you want the computer to take, and then… you en-code it. You write it down, in a language that the computer can understand. Written source code is an expression of a program or an algorithm. There’s a mystical feel to it.

Code is authored. It’s author knows what was intended, knows what was encoded. Other people can read and understand what the written code actually does (sometimes better than the author), but they can’t always know what was running through the mind of the person writing it.

Just as a poem reflects the passion of a poet, or a novel reflects the imagination of the novelist, written source code reflects the mind of a programmer – “Here is my solution to the problem.” Like any other written text, code is a snapshot of something of the mind.  Often it’s a snapshot of something mundane, [woo hoo! A database connection! A bubblesort!] but then, we don’t always have the luxury of thinking about interesting things.

When we say that something is authored, it means that whatever it is, it was first conceived of. If a poem speaks of love, there was first a poet who loved. The novelist who wrote of danger may have never suffered a knife at his throat, but he certainly knew the concept. The humble programmer knows that he wants to connect to a database. Before the expression existed, the thing was known and understood.

Is God an author?

If God is an author, it means that I was known and understood before God created me. It means that he perfectly knows and understands (cause, effect, reality) my struggles and triumphs, my emotions and my spiritual head-bangings. If I feel it, then God first conceived of it.

He may not necessarily have desired it, but it is not outside the mind of God. If I want to call God an author, I acknowledge that I cannot tread on alien ground. It’s a comforting thought (yet I can also see how it might prove aggravating).

comments: 0 » tags:

Hide your shame

January 2, 2009 under thehumancondition, theology

Today I’m swiping links from Raymond Chen.

Las Vegas has a lot of shame to hide. Hiding shame is its tagline – “What happens in Vegas, stays in Vegas”

When I embrace something shameful as a rule of life, it has a drastic consequence: I are forced to abandon truth. It becomes impossible to hold onto the truth because the truth is awful. I’m faced with the choice of either abandoning the shameful thing or denying the truth and trying to bury the shame.

Of course, Vegas would never try to bury its shame.

In the wake of Hurricane Katrina, there were a some who declared that Katrina was God’s judgement on New Orleans. I maintain that it’s difficult to know for sure, because Katrina was a hurricane and New Orleans is a coastal area. When a hurricane hits Las Vegas, we’ll know.

comments: 0 » tags: ,

Living in the real world

January 1, 2009 under technical, theology

When does something become real to me?

It’s not when I hear about it or learn about it. Sometimes it’s not even when I see it or touch it. Something becomes real to me when I make decisions based on its nature. When I live a part of my life (however small) according to its existence and character is when it has crossed the threshold from head to heart, from knowledge to belief.

This is true of faith and this is true of more mundane technical matters. As an example, I know that unit testing saves time and trouble, but I don’t always believe it. The benefits of unit testing are not fully real to me.

I have read and accepted the truth that security problems are people problems, not technical ones. However, when a friend’s blog dies like this, it becomes a little more real.

comments: 0 » tags: ,