Gavin’s Digital Diner

I think I was eight when I read my first “real” book — of course, that’s not counting comics, Willy Waddle, or books designed to be chewed. The book was Arthur Ransome’s Swallows and Amazons, a proper book; a marvelous story for a boy who spent his days poking at squiggly-wiggly things in the tide pools of Cadboro Bay. I’m sure I still have it somewhere.

I love books — the look and feel, even the smell. They’re almost perfect: relatively portable, random-access, and — treated properly — they’ll last a hell of a long time. If you get tired of them, you can give them away, sell them on eBay, take them to a used-book store, or burn them for kindling, al la Fahrenheit 451… They look grand on bookshelves. They’re almost perfect. The do have a few draw backs:

• Books (and paper) are heavy — especially those damn 4-inch thick computer books.
• Books are not very portable — small quantities are fine, but if you try to take ten or so on vacation with you, it’s a literal drag. Despite their catchy name, Few “Pocket Books” will actually fit in a pocket — or if they do, you look kind of stupid.
• Paper takes up a lot of space — especially those damn user guides, administrator guides, and installation manuals I print and bind in 3-ring notebooks.
• Printed materials tend to “expire” — Today’s newspaper is worth about a dollar, yesterday’s is suitable for wrapping fish. (Of course, tomorrow’s newspaper, if you had it today, would be worth a fortune.)
• Repurposing is difficult — Transmutation costs are outrageous, either lead to gold, or paper to digital. Screw OCR, it’s not good enough, ever.
• Paper is expensive — There a “tree-cost” and an environmental cost. The manufacture and bleaching of paper is horrendous. Stand downwind of a pulp mill and breath deep. You’ll know what I mean.
• The print publishing process is arcane — the economies discourage risk and tend to favor existing authors and large publishers, to the determent of the small publisher or aspiring writers.

In late 2007, Jeff Bezos introduced the Kindle. I’m not sure he’ll be remembered in the same breath as Herr Hoffmann Johannes Gensfleisch zur Laden zum Gutenberg (whew). At least his name is shorter. The Kindle is, nevertheless, revolutionary.

Life’s Little Ironies

I got mine in late January of 2008. I feel I’m standing at the edge of history. Despite the book’s drawbacks, it was with some concern for my eternal soul — and some trepidation about the future — that I ordered a Kindle. A classic conundrum, I was caught in a lovers triangle, torn between my love of books and my love of shiny new gadgets. I couldn’t resist. I did not get it simply because I had an extra 400 simoleons burning a hole in my pocket though. I had a real purpose in mind, really. But I do like gadgets.

Just so we’re straight: let me assure you, I am not anxious to herald the end of the 600-year reign of the book. More so, after watching what the iPod and digital music has done to the music industry; I fear for the future. Newspapers are already suffering — perhaps on their last legs — put out to pasture by something as innocent as Craig’s List. Information may want to be free, but writers (and journalists) also want to eat. I think they should. Nevertheless, I bought a Kindle – hoping to fill it with user manuals, installation guides, and 4-inch-thick computer books (and a little pulp SciFi for long airplane rides).

Ironically, my Kindle arrived just after I had spent untold hours building, drilling, cutting, measuring, cutting again, cursing, painting, staining, sanding, and trimming some 30-odd-feet of book shelves for some of my thousand-odd books. There was barely time to admire my work before it was time to ponder the future of books. Had it all been a waste of time? They’re awful purty, if I do say so myself.

The Difference Engine

The Kindle is different; it changes the rules of the game. First, it’s wired, in a wireless sort of way. It comes bundled with a lifetime, free wireless connection to the ‘net — an EVDO connection, no less, via Sprint.

That’s right, you heard me —free. Once you shell out the 400 clamasaurs, you can browse the web, surf to your heart’s content for not another plug nickel. You see, the connectivity is bundled as a cost of sales, book sales. Amazon is betting on making up that cost with the sale of content; figuratively giving away the razors and hoping to sell you a razorblade in the form of a $9.77 Kindle-ized copy of Sweeny Todd (the book, not the movie).

They’ve made the process so painless it’s scary. Gratification is instantaneous. Click a button on the beast, and the book arrives, wirelessly, painlessly, ruthlessly efficient. I worry it’s too painless. Now, when I finish the first book in a three-part trilogy, the next book in the series is just a click away. This could cause a clamasaur problem.

I admit, at first glance, the Kindle looks funny. I was disheartened by its design, seeing the initial press coverage. In the pictures it looked like it was designed for the DHARMA Initiative (right here in Ann Arbor), circa 1968. Up close, though it’s not that bad — kind of retro, kind of not.

It’s here that I think the wonky gadget geeks missed their marks, and missed them badly.

The pundits, previously spoiled by the elegant beauty of all-things iPod, almost universally panned the Kindle, complaining about pretty much everything. But they especially complained that it was impossible to hold and “funny looking” (a technical term meaning not an iPhone). Once I had mine in my hands, I knew where those grumpy geeks had gone wrong. They had been using the Kindle naked. I mean the Kindle was naked, not the gadget geeks. (Don’t go there.)

In the half-dozen reviews I saw or read, every Kindle was demoed without its leather case. It was a logical mistake on their part. They’re used to looking at iPhones, and iPods, and other iThings — we can blame bad iPoddy training. The iPod “case,” for example, is a worthless throwaway specifically designed to make you spend another couple of hundred dollars on iPod accessories.

Back to the point, the Kindle, sans the (included) cover, is awkward to hold. However, properly attired, dressed up in nice leather, it all flows, it all makes sense. This cover is integral. You need it.

A Properly Dressed Kindle

Easy to Hold | Easy to Read

Without its cover, there is no easy place to put your fingers, no logical place to grab it at all. In fact, everything you touch seems to toggle the pages, either forward or back.

Slip it in its cover, however, and suddenly all the weird angles make sense. The left edge sort of slips into two leather brackets, and the weird angles on the right side now provide purchase for your thumb on the cover— they’re cutbacks that let you easily hold the thing without mashing the (now handy) “Next Page” bar. There’s a little plastic tab that snaps into the rubberized underside of the beast that holds it all in place. (Pundits, apparently, don’t read manuals.)

With the cover on, I find myself holding it just like I would hold a hardback book; palms on the cover and thumbs on each edge. Nothing could be more natural. It “feels” like a book. Moreover, it reads like a book. I’ve even taken to taking it to bed, reading a few pages of a novel before The A Daily Show. Let me say that again: it reads like a book. The transition was painless. My luggage has just shed 10 lbs.

It has a couple of other features, some worth mentioning, some not. There’s a speaker, but it’s lousy. Given that, it will play music and audio books. Through headphones or ear-buds the sound’s great. I gave it the Amy Winehouse test, and it passed. But, I’m not giving up my iPod (which is filled with Audiobooks anyway). Besides, there’s no way I could easily wire it into my car without feeling real foolish. Of note, you can put it “to sleep” — locking the keyboard — and the music or audio books will continue to play. This is important; otherwise the cover clicks the mousy-roller thing, playing havoc.

The Weight of Water

Weight-wise, the Kindle is elegant. It weighs in at exactly one pound, cover included. At first, I thought: “a pound, damn, that’s kind of heavy for a book, ain’t it?” Turns out, it’s not. (And, quite frankly, the Kindle is smaller than it looks in any picture.)

Just for the fun, I decided to run its “comps” — to compare it to a few other books I had laying around on the nightstand.

As you can see in the pictures above, a typical paper-back “trade” book, as represented by The Hero with a Thousand Faces, weighs over a pound and is also slightly larger. A hardback (an embargoed copy of Chuck Lewis’s The Buying of Congress) is almost twice that. A paper-back, unabridged Mark Twain Reader is over 3 lbs. But, then again, Mark Twain is worth his weight in gold. Paperback pulp fiction, the kind I find in airports and carry from country to country, town to town, weighs in at about a pound.

Size-wise digital books on the Kindle average between 500K and 800K. Calculating liberally, that means that my beast, outfitted as it is with a 2GB SD card I found in a drawer, can hold over 2,000 books. With that kind of space, I am going to be well read, but broke.

Here’s the deal: Kindle books typically cost less. By my reckoning, I’ll save the purchase price within two years, on computer books alone. I am, on the other hand, worried about my local Borders, the Kindle’s gain, is their loss. I take solace in the fact that clicking the Kindle is no substitute for my weekly trip to the Border’s redoubt.

Books on the Kindle are cheaper than paper… Here’s a random comparison of titles and prices.

Depending on the book, savings run from nothing, up to about 26 percent of the print edition. Savings over hardback costs are greater still, but that comparison seems unjust, since the difference seems irrelevant.

[Borders, by the way, no doubt fearing the loss of my business, has opened a new concept store in town. It incorporates “digital media and internet features” — a concept they are calling the “media room.” I haven’t been yet — been too busy building bookcases and playing with my Kindle.]

The Future of Ideas

Finally, with the Kindle, I had two ideas I wanted to pursue — two ideas I used to justify the purchase to myself:

1. I use it as a “geek reference library” — loading it up with PDF copies of manuals, installation guides, administrator references, and all the other desiderata of CIO life (as well as books).
2. There were possible “enterprise” uses — could I, for example, use it for board materials? Would it effectively bridge the gap between things “printed” and things “digital,” serving that in-between no-man’s-land land where we still want paper, but despise it.

The Portable Geek

The first idea turned out to be easy. There are three easy ways to turn other documents, like PDFs, into things that can be read on the Kindle. It’s not perfect, but it works. It works best with text-heavy documents. Graphics can be a problem. They don’t scale well.

At issue here is the ability to scale — fonts and graphics — from “I can read it” to “I can read it across the room.” The text has to be able to “flow” — to adjust to the screen as you up the font size.

Amazon’s native format — a DRM’ed version of the MobiPocket eBook format — does this. Word documents and text documents do this. This makes Kindle conversion easier. PDF’s don’t flow all that well, especially if they’re graphic-heavy. To set the record straight: the Kindle supports Amazon’s DRM format (.AZW), as well as unprotected MobiPocket formats (.PRC and .MOBI) and Text documents. Other formats (like Word and HTML) must be converted

With all of them, Word, PDF, HTML, or Text, the conversion is easy. There are three ways. Two are free, and one costs $0.10 per document. The ten cents is for the wireless delivery.

1. Convert via Email (without wireless delivery) — simply email the file to a special Amazon email address, they’ll convert it for you, and they’ll email it back to you. You then drag it on to your Kindle from your PC.
2. Convert via Email (with wireless delivery) — simply email the file to Amazon to a (slightly) different email address, they’ll convert for you it and email it directly to your Kindle for a cost of ten cents. It arrives on the Kindle via the wireless connection.
3. Convert manually — simply download a (free) copy of the MobiPocket Reader software, and click the button to convert the file to the MobiPocket format. It takes a few seconds and stores it on your hard-drive. Once done, you just drag it into the Documents folder on the Kindle.

That’s it. With a little “conversion” work, I had a complete technical reference library on my Kindle. Moreover, it was searchable. Everything on the Kindle is searchable. That’s what the keyboard is for. Just a few (tiny) keystrokes and you get a KWIC listing of any term you enter. Idea number “One” was a success. I had my geek library, portable, searchable; I’d never suffer insomnia again.

Enterprise and Culture

The other idea, enterprise applications, is slightly problematic. The Kindle, like many of today’s gadgets, does not lend itself well to enterprise. DRM gets in the way, much as it gets in the way of using a Kindle within a library. That’s a problem that needs solving. In my mind, the solution is easy, the answer, simple: like a physical book; a digital book should only be in one place at a time. How this is done, is easy too, but I’ll save that idea for some other time.

DRM aside, there are a few uses where the Kindle has an enterprising chance — a chance to function as a wedge between the analog and the digital world.

Organizationally, for example, we produce and ship an amazing amount of paper, all for an internal audience. Non-profits in general do the same thing. I’m talking about all those board documents; updated policy manuals, bylaws, program plans, pandemic plans, and disaster recovery plans. In organizations today, documents fly through the email-aether. But, in the end, a surprising number end up on paper, in binders, and three-ring notebooks.

The reason is simple. Humans — especially those of longer tooth — don’t especially like to read lengthy documents on LCD. Even short-toothed people don’t like reading long documents on an LCD screen. Enter the Kindle.

My thought is to replace all those “reference-type materials” — Board materials for example — with a Kindle and digital copy. Even at $400 a pop we’d save on in-house publishing costs (not to mention the FedEx bills). Moreover, for the most part, these sorts of documents are not “interactive” they’re reference.

Nevertheless, they’re necessary. And, they’re heavy, awkward, and difficult to transport. They suffer the same liabilities as the “book.” Kindle-izing them would save time, save paper, keep everything centralized and up-to-date, and allow a 10-cent, near instantaneous delivery.

In the end, I am reminded again of Gutenberg. It turns out he only printed about 180 Bibles. He made his money running a press on the side, printing thousands of indulgencies for the Church. It’s an old story, innovation flows to demand. Plus ça change, plus c’est la même chose. Perhaps I’m indulging myself, but I suspect Gutenberg would approve.

Share This

A few days ago, a reader of this humble blog asked if I knew a way to embed “Skype Presence” in a SharePoint Web Part.

I didn’t. But, I was intrigued. (That’s a bad sign… as it usually means I’m going to stay up until the wee hours.)

It turns out to be pretty easy-breezy, with a few caveats. I’ll explain those below. It’s easy because lots of stuff today is “widgetized.” A few minutes on the Skype site turned up some Skype web-widgets—– basically HTML code one can embed on a blog or web page — that gave me what I needed: HTML that would display Skype “presence” by Skype name (what I call a SkypeID).

Realize, I’m no code slinger, but it looked to me that one could simply modify the HTML, adding in different Skype names, and then stack it up in a CEWP. So that’s what I did.

That’s it. Once again, the Content Editor Web Part (AKA: CEWP) is a wily rascal. It can do the most amazing things. The HTML itself is pretty simple. It consists of a small scriptlet, and some basic HTML. Here it is in a screen shot:

I’ve highlighted the areas you need to change – basically substituting the appropriate SKYPEID in the yellow areas, and/or the appropriate “friendly name” at the bottom. That’s the basics.

My first attempted yielded the result above — a webpart with my Skype status and name. If you click on the “I’m Online” graphic, it launches Skype and tries to make the call (via Skype, of course).

Silly Rabbit, Trix is for Kids

I tried it, but some wiseass at Skype designed it so you can’t call yourself. (Grumble – what fun is that!). Anyway, this all once again shows how truly neat the CEWP is.

Now I decided to get fancy — after all it was still early. I decided to set up a nice format, a table, light border, etc. Just because, I also decided to see how it handled multiple Skype accounts in the same part.

Not a problem, it turns out. I just had to cut-and-paste the code, changing the embedded SkypeID in two places, and inserting a “Friendly Name” so that it looked nice on the screen. It’s all pretty straight HTML. No muss, no fuss, and — no kitchen drudgery.

Here’s the final screen shot:

Schizophrenic Skype Status

The caveats and other bits:

1. You’ve gotta have a Skype account to use this. And, you have to have Skype loaded to use the button to call someone. If you don’t have Skype, you’ve wasted your time reading this anyway.
2. This is just stacking up the standard Skype “Skype Me” widgets. You can find other ones here: http://www.skype.com/intl/en/share/buttons/
3. I’ve not a clue what kind of demand this puts on SharePoint — but since this is all “client-side” code, it shouldn’t be a problem.
4. The trick here is the Content Editor Web Part. Make it your friend.
5. I did this originally in MOSS, and then duplicated it in WSS, just to make sure that it worked in both environments. It does.
6. This Skype status does NOT refresh unless you reload the page. Hence just leaving the page loaded might result in inaccurate “presence” information. [I looked at a few methods to automatically refresh, but nothing seemed elegant, and the easy answer would refresh the entire page.]
7. Use at your own risk.

I’ve appended the final code below, and I put an exported copy of the webpart up here. Feel free to download and abuse. You’ll need to edit the code and insert the desired SkypeIDs and dup the sections for additional IDs.

Finally — and I say this seriously — Caveat Emptor and all that jazz. I offer no guarantees. I distribute this free of all responsibility and liability, use and/or abuse at your own risk. It should give you no problems, but if it does, well… I’ve left town, and I’m living with the dogs on the Dalmatian coast.

Content Editor Web Part – Code for Skype Presence embedded on WSS site.

Note the areas you’ll need to edit and change. You must replace the text “SKYPE_IDn” and “Friendly_Name” with a real Skype IDs and really friendly name.

Share This

I woke up when I heard the snap, crackle, pop. A tree had fallen in the woods and I had heard it. Whatever the philosophical implications, the actual effect was that my power went out.

“Damn,” I muttered, shaking off a sense of déjà vu. It was early morning, Sunday, December 23. The winds were howling — gusts to 90 mph, or so the weather channel had predicted the evening before. Trees were snapping and cracking like Rice Krispies. “Damn,” I muttered, shaking off a sense of déjà vu. The earlier the hour, the more limited my vocabulary. “Damn,” I muttered.

I glanced at the clock. Now on battery — having achieved true cosmic Zen harmony with its VCR brethren — it was happily flashing 12:00, 12:00, 12:00. “Damn,” I muttered, switching my gaze to my backup alarm clock. It read 7:30 am.

It’s was a Sunday, the day before Christmas Eve, and I was without electricity. I thought to myself: “now, you couldn’t pick a better day to challenge the fading infrastructure of a once-great industrial state.” I then told myself to shut-up and stop being so pedantic — fading infrastructure, indeed. “Damn.”

Me and disasters, well, we’re on friendly terms. Part of my job is disaster planning, “Disasters R Us.” I get to ponder global pandemics, earthquakes, deep-fat-fried-Twinkies, extensive power outages, staff gone wild, management run amok, nuclear winter, printer jams, and printer jellies. It’s all part of the job. Since ICT is now central to people’s days, lives, and work, it’s my job to figure out what to do when things go pear-shaped.

Consequently, I try to have all the appropriate responses already lined up, ready to go. I was a Boy Scout; I am prepared. In the case of my Christmas Eve scenario I was ready to leap into appropriate action.

In this case, I pulled the covers over my head and tried to adjust the position of my patented personal heating unit (AKA Tanzy the Dog). Moving a sleeping dog is impossible, by the way. Dogs control space, time, and gravity. They can change their weight and size, at will. And, they’re also very fond of tennis balls. It was Sunday, for Pete’s sake, a holiday, during a holiday week, no less. I was going to sleep in whether I wanted to or not. Now that’s an entirely appropriate disaster response.

Experts have lots to say about disaster preparedness (pesky bastards); most of it is either unintelligible or shrouded in $10 words and $100 phrases that don’t mean squat. Personally, I have four simple elements: Avoidance, honest and realistic objectives, maximum flexibility, and clear communications. Let me explain:

1. Avoid the disaster in the first place — this is the most important rule and it’s the one that most people ignore. I prefer avoiding a disaster to living through one. Given a choice, spend your resources on avoidance. I like redundancy (hence the backup alarm clock). In this case, I should have bought that standby generator I lusted after when the world was going to end in 1999.
2. For those cases where avoidance fails you, at least be honest in your planning. Identify the processes and resources that are truly critical, and I mean truly. Having all your phones work is nice, having one that works is critical; having AC in the summer is nice, having heat in the Michigan winter is critical. Moreover, once identified, develop realistic and cost effective recovery objectives. Simply, that means figure out how you might easily resurrect the critical bits, cheaply, quickly, and without much fuss.
3. When you’re planning, admit you can’t know the future and don’t try. The objective is to give your future self maximum flexibility. Remember “Murphy’s Law of Combat” — No plan ever survives first contact intact. Designing a plan that tells you exactly what to do is stupid. Instead, design so you can roll with the punches. Be prepared — plan — to adapt, improvise, and overcome. Have options, have backups, have redundancy, and think on your feet. Worry only about the critical stuff (see item 2, above) and give yourself lots of lots of options.
4. Finally, plan on communicating. Plan to (and have systems that allow you to) talk to folks — your clients, your staff, your mother. Stress clear communications in your planning and in your responses. This is absolutely crucial and this is where most folks screw it up. All the planning in the world won’t do you a lick of good if nobody knows about it, or if nobody knows what to do. Have a backup communications plan, and have a backup of that.

Back to my wee disaster…That morning, Tanzy’s canine gravity control was in top form. She was immovable. I made due, wondering all the while how such a medium-sized dog could be such a huge dog, or is it the other way ’round? Nevertheless, she’s a great heater (dogs have a body temperature between 101°F and 102°F).

We get 4 or 5 major “outages” a year. Obviously, I’m on an alien flight path and the damn di-lithium crystals are playing havoc with the flux capacitors again. Perhaps, you say, I’ve been watching too much of the SciFi Channel? Maybe, it’s my karma. Nevertheless, we’re prepared. Batteries, flashlights, a small battery powered lantern, 10 or 20 gallons of bottled water. Duct Tape. We’re prepared, I like the process. I’m often tempted to put together the survival kit from “Dr. Strangelove”:

Survival kit contents check. In them you’ll find: one forty-five caliber automatic; two boxes of ammunition; four days’ concentrated emergency rations; one drug issue containing antibiotics, morphine, vitamin pills, pep pills, sleeping pills, tranquilizer pills; one miniature combination Russian phrase book and Bible; one hundred dollars in rubles; one hundred dollars in gold; nine packs of chewing gum; one issue of prophylactics; three lipsticks; three pair of nylon stockings. “Shoot, a fella’ could have a pretty good weekend in Vegas with all that stuff.”  (Slim Pickens speaking as Major T.J. “King” Kong from “Dr. Strangelove,” 1964).

Admittedly, my supplies are slightly different. (The Russian phrase book seemed superfluous and I couldn’t decide about the lipstick.) Nevertheless, we’re prepared. We’re prepared because when the power goes out, it’s not just the lights. We lose all niceties like water, phone, toilets, heat, internet, TV, garage door opener, and all my ‘puters. Prepared does not mean pleasant.

At 9:30 am I got up. The power was still off, and I started wishing again that I had succumbed to the siren call of Y2K and bought a standby generator. I made conscious decision to revisit that decision — avoidance is the best defense.

With great trepidation I realized it was time to brave Detroit-Edison’s (DTE) voice-mail-hell — the living example of how not to design your customer / disaster communications systems. So I woke my wife.

DTE’s integrated voice response (IVR) was designed by someone with the communications skills of an illiterate monkey. Perhaps, I’m insulting the monkey. It was designed to obfuscate, not communicate, to placate not to inform. Even that was done badly. During a disaster, you don’t want to trifle with people. You want a clear message, with clear instructions.

This particular IVR was not only irrelevant and condescending but inconsistent. Seemingly randomly, the option to press the keypad would disappear, and it would only accept a voice response. Moreover, its voice recognition system was lousy, only understanding if you mimicked it, imitating its lilting prosody, forcing my wife to sing “I don’t have one” when asked about a second contact number. After endless (and slightly chilly) minutes of punching buttons and singing into the phone, we heard a hopeful note: “please hold on while I transfer you to a customer service representative.”

If the journey was endless, the letdown was immediate. The system quickly interjected: “Actually, there are no customer service representatives available right now.” “Actually,” I thought? What strange phrasing. “Actually, I’m an idiot for actually getting my hopes up.”

“Please enter or say your telephone number and a customer representative will call you back,” said the IVR. To that, my wife sang a few more bars of “Yes,” “No,” and “I don’t have one,” it hung up. I went to gather firewood.

All in all, we must have called at least 20 times between Sunday morning and Monday morning, Christmas Eve. No one ever called back. Finally, on Christmas, we reached a human who told us our worries would be over by 5:30 pm, a repair crew was on its way. At 11:00 pm, still in the dark, I realized we’d been stood up again. I stoked the fire and vowed to get a generator. Two days later, the crew arrived.

I learned something. The DTE systems for both reporting problems and checking on the status of problems just did nothing except to force us to sing into the phone — Voicemail, the quickest way of telling your customers that frankly, you don’t give a damn. The web site (via laptop and blackberry) was designed solely with marketing in mind. It was also unusable via handheld.

Let me tell you, trying to navigate through buttons, icons, pictures, and swirly glossy things with a handheld does not make a good marketing impression. This struck me as another example of poor communications planning. Folks, pay attention, ’cause this is a lesson for me too:

In any sort of a disaster situation, most likely the tool you’ll have at hand is a cell phone. Moreover, the tool your customers, users, staff, or family will have is also a cell phone. Design your information systems, your communications systems, and your response systems with that simple fact in mind. Keep things simple and to the point, and communicate often.

This old dog learned from the experience. Girded by the experience, I decided that my various disaster recovery plans needed some rethinking. I needed some communications redundancy — and I needed to make things work via handheld and cell phone, the telephone is a simple and resilient communications resource, ubiquitous in its reach and adoption.

In the end, I went with a simple out-dial system, something that could be turned on or off at the flip of a switch, something off-site, third-party, and something that I didn’t have to maintain. In this case, a pre-programmable phone-tree service called “Call-em-All.” For next to nothing a year, it provides a turn-key automatic phone tree that can, at the drop of a hat (or crash of a tree limb), automatically call a preset list of folks and deliver a message. They even have nonprofit rates.

Be smart. When you plan for disasters, plan to communicate. Plan to communicate about its duration, impact, and consequences. People want to know what’s up, and they worry if they don’t know. Do that and you’ll weather it. Planning is easy; communications can be tough.

Note: Most of this was written in the dark, on a laptop. The laptop was charged using our hybrid Mercury Mariner (it is one giant battery after all) and the draft was uploaded using a wireless connection via my Blackberry (also charged off the hybrid).

Share This

I learned of the game the hard way. Sometimes it’s called “Follow the Lady” — you probably know it as “Three-card Monte.” It depends on the art of misdirection, distraction and illusion, and just a little sleight of hand. And now it seems, it’s played every night on the evening news. Even “The Daily Show” (or for now “A Daily Show”) seems to have been taken in by the artful dealer; fooled by the throw of the cards; fooled into casting the contests one by one, and ignoring the real story.

“What,” You say, “you don’t know the game?” Well, it’s easy… easy to play, easy to win. Step in a little closer…, trust me… Step right up, everyone’s a winner!

I learned the game when I worked a carnival one summer. Nope, I wasn’t “a carnie.” I was just a “greenie,” cheap summer labor. Being a carnie, well, that’s something you’re born too.

I was an innocent — called “a new” — maybe a half-step above the mooks and marks that meandered on the midway. Even now, I can sometimes catch a scent of that past, when the wind blows right. It’s scent that casts me back to those long days and thick summer nights, Kansas in late August.

They were nights where lightening-bugs punctuated the sky, and where every once in a while an elusive breeze would lift the scent of fresh-cut straw over the crowd, spiced with the burnt sugar scent of cotton candy, to fall lightly across my face as I barked the midway.

“Step right up and win a stuffed animal; everyone’s a winner,” I’d cry , as the crowd filled the midway, shuffling through the narrow lane formed by the “Ring Toss,”, “Shooting Gallery” and the rest of the joints that formed the main street of the carnival. I’d cry to the blue-eyed young women with straw colored hair, and to young men bedecked with tattered straw hats; all trailing a scent of the earth, Dove soap, and hard work.

Carnival life is no fun: I was either setting up a joint or tearing one down, or driving through the night, bound for the next small town. I worked my ass off and barely making enough to cover my tab at the concession stand. When I wasn’t working my ass off, my job was to bark on the midway, calling in the marks for a quick round of ring toss or to try their hand at knocking down a milk bottle with a baseball attached to a pendulum. The games aren’t gaffed, they aren’t rigged. Trust me, they’re straight. It’s just physics, sleight of hand, and misdirection. It’s the refined art of distraction that wins in the end.

Back to that great game, Three-Card Monte; it looks so easy. Just follow the lady. A good dealer can rope you in with a few easy wins. The shills entice and distract. I tried to learn the art of the throw and how to deal the cards; to artfully throw down one card while all the while looking like you’ve thrown the other. My hands were never good enough, my fingers never deft enough, my eyes were never shaded enough.

Today’s shills are working the media, on Fox, on NBC, and on CNN. They’re hyping the winners and losers, everyday. The news casts it continuously as a series of losers and winners — the art of misdirection.

In Iowa the surprise was Obama; in New Hampshire, Clinton was supposed to lose and lose big, only to surprise us all and win the stuffed elephant. (Or would that be a donkey?) Strangely, despite “losing,” Obama won more delegates.

But the story we hear: the pollsters are chagrined. It’s all the art of misdirection. Just between you and me, I take great pleasure in lying to the pollsters every chance I get. I advise you to do the same. Take great glee in knowing that they’re usually required to record faithfully everything you say. Imagine the possibilities.

All the while, there’s no game at all. In reality, it’s not the individual primaries that count. In fact, the media is just working the story they want to work. It’s a tie. As of this writing, neither is up, neither is down. It’s all the game of distraction.

They’re tied in a game that’s not played state by state; because it’s only the cumulative score that really matters. In Nevada Clinton added 14 to her score, while Obama added 14 to his. Obama has 38 delegates and Clinton has 36; film at 11:00. But there’s no news in that, is there? The game is called “Follow the Lady.” We’re distracted with the horserace, and we ignore the substance of the race. Step right up. Everyone’s a winner.

Share This

[The exciting sequel to “The Cuneiform Code“]

Having established the elements, theories, and principles, what I really wanted was pretty simple. I know what I wanted to keep (element one); I had a place to keep it (element two); and what I thought was a simple way to find it all again (element three).

Element One — Know what you want to keep:

What I wanted to keep were all the bits and pieces of information that are crucial to a sane IT operation. Here’s the dirty secret. There is a vast amount of stuff — facts, figures, incantations, mystical folklore, secret handshakes, twiddles and tweaks — that IT folks have to remember to keep tens or hundreds or thousands of computers happy and healthy. There’s even more to remember if you want to keep a vast army of squeaky users happy and healthy too. To most folks IT stuff is voodoo. I needed a simple system to remember all the voodoo, Papa Legba be dammed. What I wanted was a simple system to track all these assorted permutations, combinations, and incantations.

[My secret goal was to simply avoid the 11^th circle of IT hell — the hell where all bad programmers go, along with whoever invented the concept of “opt-out” email. (It should be “opt-in,” you bastard — no fruit baskets for you! Oops that slipped out.)

It’s a hell composed of forever clicking “Next” again and again and again, while simultaneously explaining how to print an envelope with Word. It’s a hell where all three heads of Cerberus nip gently at your heels while you un-jam a printer. It’s a hell where you are forced, again and again, to diagnose why “X” program doesn’t play nice-nice with “Y” program.]

So, I needed a knowledgebase. My knowledgebase will serve as a repository for a host of esoteric knowledge, making it easy find again, right at my proverbial fingertips, so it’s there, when memory fails — a shared repository of the critical yet esoteric. By the way, the sharing aspect is as crucial as the “keeping it simple” part. It does no good if I know it and others don’t. Those “others” must be able to find it too.

Element Two — Have an organized place to keep it:

Abraham Maslow once observed “When the only tool you own is a hammer, every problem resembles a nail.”

[My variant on Maslow is: “When all you have is a hammer, you’re bound to hit your thumb. So swing lightly.” My father’s variant on this was: “Nothing screws things up faster than a power tool.” With a power tool, you’re likely not just to hit your thumb, but cut it, and a portion of your arm, clean off. Beware the power tool. ]

It’s only natural I suppose, that when I wanted to build a knowledgebase, I turned to my preferred hammer, SharePoint. I’m sure there are other options. Maslow aside, SharePoint is well suited to the task. It’s perfect — really. It hits all the criteria. In fact, a couple of features in MOSS make this a cakewalk — specifically these new things called “email-enabled document libraries.” This feature, new to MOSS, eliminates a dozen headaches. Moreover, they make it easy to feed the beast. Email-enabled document libraries are also kind of smart. MOSS is a power tool, though, swing lightly.

First, using email-enabled document libraries, a knowledgebase is easy to feed. People already spend their days inside of Outlook; I figured I might as well capitalize on that. Second, MOSS’s document libraries are flexible. They’re flexible enough that they handle just about everything I’ve thrown — or emailed — at them, including multiple attachments, mixed attachments, weird attachments, and Buddhist email (no attachments).

Element Three: Have a Way to Find It Again

Finally, the “easy retrieval” requirement is well met by SharePoint, almost out of the box. Once you twiddle with it a bit, SharePoint’s indexing is terrific. It handles all “Office” documents, including (important for me) Visio drawings. I tend to think in pictures and flow charts drawn on napkins and, subsequently, translated to Visio. Other file types are a piece of cake too, as the search engine is extensible via add-ins called IFilters. There are IFilters available for PDFs, and JPGs, and MP3s, and all sorts of other stuff. Find a list here. There’s a filter for just about everything, from GIF’s, to TIF’s, through ZIP’s.

Creating and Feeding the Beast:

With SharePoint, feeding the beast is easy. You can send it an email message; you can send it attachments via email. SharePoint will magically convert the message to a file and put it in the document library. Along the way, it takes all the information it can from the email system and adds it as metadata, automatically. Everything — metadata, message and attachment(s) — are completely searchable.

Anything mailed to the library gets the following information automatically added as related metadata:

I added one additional field — a calculated field to store the concatenated value of the “Title” field and the “Subject” field. This is just so I have one field that contains either the “Title” or the “Subject,” instead of having to look at two separate fields. As such, if one or the other was blank, it didn’t matter.

Helpdesk Site Showing IS Knowledgebase View

When you email an item, SharePoint automatically detaches any attachments and saves them with the same metadata as the message (From, Subject, etc). As I mentioned, you can also feed the document library directly, dropping files directly into it, uploading, or by saving files to it from any Office application. You can even set it up as a mapped drive, should you want to. True to my needs, it handles just about anything, including images and Visio drawings, as well as Word documents, Excel spreadsheets, PDF documents, and the body of an email message.

Knowledgebase — View Showing Items Grouped in Folders by “From” Address

There is one nice option called “Group Attachments in Folder.” This option lets you decide to have MOSS automatically store things in folders based on the “Subject” or “From” field of the email message. I show a view of this above. I chose to group by “From” — neatly organizing the stuff by each contributor to the knowledgebase.

(Note: As you’ll notice in the above screen capture, I’ve once again mucked up the names and such. This is to protect the appropriately paranoid. I’ve left most of my info stand as is — it’s too late for me to be paranoid.)

If you turn on the “From” grouping option, items sent to the Knowledgebase are automatically sorted and filed into folders named for the originator’s email address. It creates the folder automagically. All the stuff I send goes into a folder named for me. Stuff from other people is automatically sorted into their own folders.

I should note that getting the mail-enabled features to work took some effort. I had to tweak it. In the end, I followed a guide from a site called “Combined Knowledge” verbatim. Here’s a link to the PDF.

(I emailed a copy to our Knowledgebase, by the way — illustrating the rule that you must use it to make it worthwhile. See it works!)

Knowledgebase — Standard View Showing Basic and Custom Metadata

In addition to the regular metadata fields, you can “roll your own,” adding as many fields and types and other crap as you might need. (So far we haven’t needed to add any. )The sky (and your imagination) is the limit. Beware, however, if you create the beast, you must feed the beast. Keep it simple.

In the end, I ended up with a simple, inexpensive system for managing information, something that met all my particular, curmudgeonly needs. A system that:

• Accepts any sort of information I can throw at it, including documents, pictures, diagrams, web pages, and just about anything else that can be digitized.
• Accepts that sort of stuff via all imaginable methods, including “drag and drop”, email, scanners, upload, and regular old file/folder access
• Automatically tracks the “who, what and when” in metadata (who put it there or who changed it, when they did it, and what it is).
• Is customizable and flexible (because, well, I’m going to customize it, like it or not);
• Is easy to search — a “Google-like” interface, except none of those annoying ads about linoleum, free cell phones, or timeshares in Essakane.

Nevertheless, the most important lesson in all this is clear: Never , unless, of course, you the and first. Everything else pales in comparison. Oh, and watch your thumbs.

Share This

In theory, knowledge management is easy. Then again, in theory, lots of things are easy. In practice, things are never quite as easy as they sound. Nevertheless, lightly armed, I set out to put a few of my theories into practice.

There are three essential theoretical elements to effective knowledge management. I call these “Gavin’s Three Essential Theoretical Elements To Effective Knowledge Management.” Unfortunately, “GTETETEKM” does not lend itself to a memorable mnemonic, so let’s just call these the “KM-3.”

As I said, in theory, Knowledge Management is easy. In practice, organizations usually ignore the first element (especially the garbage part), do a half-assed job on the second, and muck up the third totally.

Moreover, the whole thing gets usually gets derailed when someone brings up the dreaded “T-Word” — Taxonomy. When you hear that word, it’s time to run screaming from the room. It’s a sure sign that you’re going to spend the next year in meetings trying to figure out how to “accurately” classify socks, or rocks, or ethnicity, or nationality, or chumps. The trouble is the world does not fall easily into logical groupings. For example, is Russia part of Europe or Asia? [It’s a trick question. The answer is “yes.”]

If you must, when in doubt — if you need one — use an existing taxonomy. You’ll save yourself a truckload of heartache. Trust me here — I know trucks and I know heartache. In fact, be daring, live life on the edge and don’t use a taxonomy at all!

Wait. Stop… Before you beat me about the head and ears with a leather-bound copy of the Library of Congress Classification System (or worse, the National Taxonomy of Exempt Entities), let me explain:

You see, there’s been a war going on for the last 5,000 years, give or take a Tuesday or two. It probably started with the first scribes in Sumer, as they struggled to do something with their ever-multiplying cuneiform tablets. Some, no doubt, wanted to keep them all stacked on their desks, while others wanted to file them away, sorted and organized, all the stuff in one place, all the stuff in another, and all the other stuff in a third. Never mind that no one had invented file cabinets yet.

Anyway, thus was born the first controlled vocabulary, the first taxonomy. There was no doubt a memo stating, unequivocally, that all clay tablets should be filed either as , , or as, upon pain of death or promotion.

[There was also all the stuff , but, I suppose it’s best not to mention that, at least not in polite company.]

Thus began the war between those who file and these who pile — the filers and the pilers. I’ve been on the wrong side, it seems, since the beginning. I’m a filer, tried and true; a card-carrying member of Filer’s Anonymous. I even organize my paperbacks, first by genre and then by author. Nevertheless, my proclivities aside, the pilers have won; hands-down. So, ever pragmatic, I switched sides. No, I’ve not started just piling up my books, but I’ve embraced the “pile it on” approach. “Bring it on,” I say, “I’m no chump; Nuh-uh, not anymore.”

Technology [written language, clay tablets cuneiform, that kind of stuff] started the war, and now technology [fast full-text machine indexing, smart digital filing systems, and natural language query] has ended it. With today’s tools, you can just dump things into a nice digital pile o’stuff and let the machines sort it out. Our tools have ended the conflict, by ending the need for the conflict. As such, they’ve also eliminated much of the need for a formal, controlled vocabulary (the T-word). Instead, a simple one will do, if you need one at all.

How to Build a Simple Knowledgebase

Let me show you how I built a simple “knowledgebase” — using simple tools and a simplistic approach — what I call simple minded knowledge management (or is that knowledge management for the simple minded …).

It’s an approach that lets me just put things in piles. Moreover, there is no taxonomy — ok maybe a small one — but all the filing is done by the machine. It works; it’s easy to feed, stuff is easy to find, everybody’s happy. And, it’s out of sight, neatly self-organized, so it doesn’t irritate me at my core.

So, welcome to the machine — welcome to SharePoint’s “mail-enabled” document libraries — a world where the machine does all the heavy lifting, from submission, to organizing, to search and retrieval. It’s a piler’s dream, and a filer’s delight. One caveat: knowledge creation and synthesis still takes work. That’s an essential human process, one of creativity and editorial heavy lifting. Machines don’t do that.

First some rules. Remember “GTETETEKM”… err… the “KM-Three.” Remember those and you should ahead of the game; forget them and you’ll likely discover that “knowledge management” is an oxymoron. Moreover, you’ll probably end up either in management or looking for a new job, or [shudder] both. Rules in hand, let’s add a dash of required simplicity:

• Keep things simple. I like simple things, simple tools, and simple approaches. Tools that aren’t simple won’t be used. Simplicity wins, period. Complicated systems fail — usually because they’re too complicated. Complicated approaches fail for the same reasons. It must be easy to use and easy to find stuff again; easy, and I mean “Eee-Zee” with a capital EASY, else it’s a wasted exercise.
• Beware, you must feed the beast. Any knowledgebase must be fed. They live on a diet of — you guessed it — knowledge. If you create a beast, you must feed it. So, while you’re at it, don’t make the beast so impossibly complicated that you won’t, don’t or can’t feed it. It needs high quality chow, lest it bite your hand.

In summary: an effective knowledge management system starts with knowing what you want to keep, and knowing what you don’t want to keep. After that, it’s all about the tools, and your tools must: A) be simple in design, B) be some-what self-organizing, C) meet your security needs, D) be easy to feed, and F) easy to search.

[Don’t miss the exciting sequel: “Cracking the Cuneiform Code — The KM Supremacy” – coming soon to a blog near you.]

Share This

It was many years later that I was to remember that day in Seattle. How I had ended up where I was, standing next to who I was, was beyond me. But, there I was — I was at the “top of the WAC” – the Washington Athletic Club — staring out the windows at what seemed to me at the time to be a giant abstract tableau. It was the end of November 1999 and I was looking at Seattle, laid out like a giant game of “Go.” The WTO was about to go into full swing — in what was to be known as the “battle for Seattle.”

From those windows high atop the WAC, I could see the various pieces on the board, see the planned movements and strategies as the police set up barricades and as people in the streets ebbed and flowed in response. It was easy to imagine reaching down and flipping a white stone to black, and thus changing the game. The game of “Go” is that way — the placement of single piece — a single move — can change the outcome of the game.

Seattle holds many fond memories for me, but that day bordered on the surreal. That day, beside me were some of the major pieces in the game, including James Wolfensohn. All in all, in the room were more than a dozen representatives of Globalization, with a capital Gee. I felt like Zelig. I kept thinking to myself that, properly, I should be down in the streets, relishing the scent of teargas in the morning. We were talking about the synergies of philanthropy, technology, and collaboration; I was imagining teargas.

These are the thoughts that swirled about my head as I watched five rather amazing musicians take a stage last week in San Francisco. I was at a concert. In fact it was a week bookended by music. Tonight was Tinariwen. Yo-Yo Ma was next Saturday. In between, philanthropy, technology and collaboration; some themes don’t change it seems.

These five fellows, in flowing Boubou robes, covered head to foot, with turbans wrapped about their heads, were playing Fender electric guitars (now there’s a truly global export) singing a rap song with a distinct West African beat, in a mix of French and Arabic. As the klieg lights shone down on these troubadours, only their eyes showing, guitars flashing, I was struck by the true amazing fact that it was globalization that had put them there; it was globalization that put me there, as well.

And, there in the row in front of me — globalized — were five young quintessentially Californian women dancing and ululating like they had spent their formative years in the High Atlas rather than Marin County. I was struck by the contrasts, by the sense of living on an interconnected planet. I was struck by the facts of globalization; and once again, things are neither black nor white.

The five fellows were Tinariwen, an almost indescribable musical group of Touareg from the southern Sahara. The Tinariwen story sounds like fiction. Guns and guitars, Ghadaffi’s poet-soldiers, Stratocasters in one hand, and a Kalashnikov in the other; supposedly, together, they count 17 bullet wounds among them. These were the Touareg, the nomadic desert warriors, the blue men of the desert. Their songs are the soundtrack of the ishumar (from chômeur, French for “unemployed”). They are the Sahara’s Generation X; once Malian rebels, now full-time musicians. (They are not a Volkswagen, despite what you may have heard.)

On stage they’re an example of globalization beyond imagination, one of its consequences and one of its effects. It seems in music and the arts, where monolithic American culture has not run roughshod; we are experiencing a new renaissance. All hail rock and roll. All hail the magic mix of music that has me rocking to the Touareg one day, and gently enjoying Yo-Yo Ma the next. [This contrast and intersection is all the more poignant given Yo-Yo Ma’s involvement with the “Silk Road” project.]

All around me that evening were the signs, the positive and negative effects of globalization. I rode to the concert in a Japanese hybrid and parked next to a fleet of others; I dined on a meal of sweet potato fries, California greens, topped with seared Ahi tuna, dressed with sesame seed oil and Japanese rice wine vinegar. I had a glass of French Viognier. I was wearing French shoes, a pair of jeans “engineered” in Germany (whatever that means) and made in Romania, and a Canadian shirt. And, I listened to the sounds of the desert, the raw tale of the Touareg, played on electric guitars made famous first by 1950’s rock and roll. Sub-Saharan nomads ripped from their lands, made unemployed and made famous by globalization.

I listened to the sounds of the desert, the sounds of a nomadic people displaced by the 21^st century, and the sounds of a people who suffer the fate of nomadic peoples all over the world.

From the Tinariwen web site (just that statement is amazing, when you think of it):

“…Forget the myths, forget the ‘guns-and-guitars’ fantasies and tales of blue-men on their camels. The humanity, the wonder and the epic sweep of the real Tinariwen story doesn’t need any photoshopping or romantic embellishments. It is the raw tale of an everyman, who was cut off from history and embraced the modern world, who lost his home and found solace in the guitar, who through pain and exile invented a new style of music that could express who he is and where he’s going. Nothing mythical or exotic about that. You can find the same story the world over…”

At the risk of showing my naiveté, clearly the effects of globalization are not all bad. Some are, in fact, grand. But others are frightening, and I often fear what we will lose, for lose we will, I fear. More so, I fear what the world will lose.

Moreover, I am, in fact, truly embarrassed by our current list of mainstream “cultural” exports. It is in music, culture, and entertainment where the west and the north are the great winners. We get better than we give. We trade the “O’Reilly Factor,” in return we get a richness and depth unplumbed. It’s striking and sad that we add so little of value to the trade, yet nevertheless seem to monopolize the market. Take Geraldo. I’ll gladly trade you Disco, the entire 1980’s, and Geraldo, for the richness of Mbaqanga, the pure energy of Tinariwen, and the sultriness of just about any French piano bar.

In this new world, where content is king, where creativity is the true currency, we seem to be rather impoverished.

Meanwhile, as I drive my Ford-but-really-Swedish car north today, into the Great Lakes winter, Afro-French-Arabic rap blaring out of an IPod (made in China no doubt); my imagination drives south, from Timbuktu to Essakane; perchance to the Festival in the Desert, and I remember: the placement of a single piece can change the whole game.

Share This

The retail release of Windows Home Server (WHS) hit the web- shops in early October. My copy arrived as fast as a flying monkey. The retail price was, as promised, less than $200 ($179 from NewEgg to be exact — a sweet deal considering what you’re getting).

It’s an “OEM” version, by the way; there’s no “consumer” version. It seems that most folks are expected to buy it pre-installed on a preconfigured “home server.” The OEM version in my grubby mitts is supposedly for “system builders,” folks that are going to bundle it with some hardware and sell it as retail turn-key system. Sure… That’s me. I am now officially a system builder. Wahoo! (ahem)

So far, the only downside to all this is, according to the shrink-wrap license, I’m my own end-user support. Apparently, the “system builder” is responsible for end-user support.

I bought it, I built it, and I sold it to myself. I must say, it was a great sales experience. I was very attentive to my needs and I seemed to know just what I wanted. Then again, when and if it comes to needing some support, I suppose I could just put myself on hold for an hour or two, ask a bunch of incomprehensible questions, cop an attitude, and then blame it on the “drivers.” That’s easy enough. “Have you tried rebooting, sir?” I’ll ask myself.

Anyway… The software’s arrival in the post just happened to correspond with a hardware sale at the local Stuff-R-Us Mega-Discount Warehouse and Croissant Emporium. They were clearing out half-terabyte hard drives — decent speed and cache — for 99 bucks. I was there and back before my credit card knew what happened.

New hardware in hand, software ready, I decided to start with a clean slate. I decided that it was time to chase the happily humming beta version, my lovely Frankenstein, out of town, like an angry villager armed with pitchfork and fire. Yep, Frankenstein, err… Fronkensteen had to go, and in its place: Son of Fronkensteen!

[See my previous Frankenstein-related posts “Savory Soho Server Soup” and “Dancing with Abby Normal.” In those two posts I describe my adventures building a beta version of WHS, and then tweaking it a wee bit so that it would also run Windows SharePoint Services (WSS 3.0). ]

Sure, I could have gone the upgrade route, but I prefer a clean build. Windows, out of the box, is messy enough. Besides I had nice shiny new drives to work with. Besides, I wanted to do this right. In the next few weeks, we were going to build one of these for our London office — to provide an automated backup/shared file storage system — best to get off on the right foot.

I figured it was the perfect setup for an office of four people. Combined with (a soon-to-be-released WHS version of) JungleDisk, it would form the perfect disaster avoidance solution for a small office. WHS was brain-dead easy backup for local files and automated, off-site, secure backup (via JungleDisk and S3) of shared files. The remote access was gravy. And all for a great price.

• WHS would provide backup from local PCs to the WHS server.
• WHS would provide shared file storage between staff in the office.
• JungleDisk would automate the backup of the shared file storage to Amazon’s S3 service.
• When those folks travelled they could get remote access (via SSL) to their shared files.
• When and if we needed, my staff could get remote access to the local workstations via the built-in TS gateway service.

Building Son of Fronkensteen

So the process begins. With two new shiny drives in hand, I set out to build Fronkensteen Junior. First, I backed up everything on the Beta server – well, everything I wanted to save – on to a couple of USB drives.

Drives Akimbo

Then I tore Frankie (or is that Fronkie?) apart, removed all the existing drives, and shoved in the two new drives. I then added a dash of extra RAM I found lying around. Out of habit I checked the jumpers and cables, gave it a good vacuum, again checked the jumpers and cables; checked wallet, watch, testicles and spectacles, closed it up, and turned it on.

Everything worked and nothing hurt, so I booted from the WHS DVD and stared at the screen for about 45 minutes while drinking tea and playing with my dog, Tanzy. She likes this part of the process.

Seriously, that was it — stare at monitor, click “OK” once or twice, play with dog, and sip tea. Maybe I had to answer a couple of questions now and then, eventually, I had to type in the serial number. Other than that, it was just 45 minutes of daydreaming about Italy, Oaxaca, or dinner (I can’t remember which). After those 45 minutes — and after ignoring a variety of warnings about formatting drives, losing all your data, and possible nuclear meltdown — it was done. Fronkie Jr., was up and running.

Adding SharePoint

Tempting fate, I then followed my own instructions and installed Windows SharePoint Services on the server too — mucking about with the IIS ports and such. The second time around it was easy; in another 10 minutes it too, was done. It took three hours, start to finish, and that includes the vacuuming, daydreaming, several cups of tea, and some serious tennis ball tossing time with Tanzy.

[Tanzy would like me to note here that the tennis-ball-tossing is very serious work indeed, and she fails to understand why I waste my time with all these other trivial pursuits. “Ball,” says Tanzy, dropping it in my lap, “Ball!” Obviously, I’m fairly dense, and can only follow simple instructions.]

WHS with SharePoint

— Embedded YouTube Video Experiment —

You can see SharePoint (above). This particular screen shot shows one of my current experiments —displaying a YouTube video inside of a SharePoint web part. Turns out it’s a piece of cake. It took about 10 minutes and a little work with SharePoint Designer. The evidence, above, is a screen-shot of a low-budget video by The Silencers performing a traditional Scottish ballad called “Wild Mountain Thyme,” AKA: the “Braes o’Balquidder” or the “Hills of Balquidder” (that’s “bal-whither,” should you care to pronounce it).

Music choice aside, the web part is simple. It’s just an IFrame as a link target, with a list of links on the same page. Put the links you want in a SharePoint list, display the list on the page, click on an item, and the content shows in the web part hosting the IFrame. You can use the same trick to create a dynamic “form library” of PDF forms, for example. Here’s an example, below:

Dynamic PDF Form Library Viewer

I can see using the embedded video parts for “how-to” videos and screen movies, on a central “how-to” page on an Intranet, for example. With a little creativity, SharePoint can rock, really.

All in all after an investment of three hours and a couple of hundred bucks, I had not only a multi-terabyte home server, but a serviceable SharePoint server too. For me, the SharePoint bit comes in handy for testing ideas about how to manage information, develop prototype intranet parts, and for experimenting with various MS Office integrations, such as OneNote.

[Lately I had been using OneNote (2007) for a variety of things, and it happily uses WSS as a central storage repository. Since I was considering using OneNote to help keep track and store a wild jumble of investment information (email, documents, charts, graphs, contracts, etc.), it was nice to be able to put it through its paces — OneNote takes some getting used to, I’ll warn you now. But it basically will hold anything — and it likes to use SharePoint for its backend storage.]

Since it was all going well, I decided to customize things just a wee bit, modifying the wallpaper and the default remote web page (shown below) — paying homage to the original “Abby Normal” build, and getting rid of that irritating picture of a “family playing in the yard” that comes as the web site default. This is much more fitting.

Son of Fronkensteen. It’s alive, it’s alive!

Finally, I installed a couple of WHS Add-Ins: Avast for WHS  (beta 3 at this writing) and PhotoSync (beta 2 at this writing). Avast adds antivirus to the WHS server, and provides a management interface to any Avast clients installed on local PCs. It’s quite nice, and doesn’t seem as taxing to the system as, for example, Symantec’s AV products. Avast! for the home user is also free. That’s a great price. PhotoSync does what it says — it syncs photos. It automatically syncs designated WHS folders with a Flickr site. To add items to Flickr, you need only put them in a designated folder on the WSH shares. Filenames become picture titles on Flickr, and folder names become photo “sets” on Flickr — unfortunately there is no support for tagging, at least not yet.

WHS Console with Avast and PhotoSync

Fronkie Jr., is up and running, happily backing up my various PCs and laptops every night starting at 2:00 a.m., and busily syncing my photos with Flickr when I ask it to. It’s centrally managing Avast! Anti-virus across my home PC network, and has yet to terrorize any of the local villagers. What more could I ask?

Share This

Her name was Jane. We met, quite unexpectedly, at Zaventem Airport in Brussels. At the Avis counter. It was such a random thing, but when I saw her I knew — no hesitation — whatever the cost, I just knew. Some things are just meant to be. With Jane, it was meant to be. Jane. I can still hear her voice.

We travelled together, she and I, bisecting France; from Brussels to Aix-en-Provence and back again. In hindsight, I couldn’t of done it without her. How I ever planned to survive, travelling those weeks without her is beyond me. I’d have been lost without her, lost.

She was my constant companion, Jane. During the day, driving, she was there. In the evenings, she’d accompany me on walks — short or long. She was never at a loss for words; she always knew just what to say. I’d hang on every word. She was worldly in ways I can’t describe. We became close in those few days together; I could sometimes even anticipate what she’s going to say next. “Oh Jane,” I said. “Run away with me. Together we’ll see the ends of the earth.” Jane, always taciturn, would say: “Go to the end of the road and turn left.” Jane had a sultry way about her, teasing yet stern, with that lilting British accent. I’d smile, knowingly. “You have reached your destination,” she’d say firmly. Then, I’d reach up and - ever so gently - pluck her from her adhesive perch on the windscreen and tuck her into the glove box. Yet, in the end, I left her. I left her in Brussels, back at the Avis counter. I had to. It was either that or lose my deposit. Jane: the GPS lady.

GPS is a liberating technology. Jane — in the form of a TomTom GPS device — was amazing. To put it nicely: driving in a strange city can be, shall we say, flummoxing. To put it accurately, it can be frustrating, irritating, and downright dangerous — to you, the other traffic, innocent and not so innocent pedestrians, and/or your assorted travelling companions.

Driving in another country quadruples that frustration and danger. Not only are you perpetually lost, but the roads are wacky, some barely wide enough for a goat (and a skinny goat at that). The pace of traffic is fast and all the signs are in a different language. [To quote Steve Martin: Those French are amazing, they have a different word for everything!] Moreover, even if the road signs are roughly approximate to English, or you happen to speak the local lingo, everything is nevertheless somehow incomprehensible.

Now what were those “three laws of robotics” again?

I’ve wandered the world, driving here and there, always with some degree of angst, some lingering anxiety about the traffic, the other drivers, where I was going, or just where the hell I was. With Jane as my co-pilot that anxiety was gone. I could concentrate on driving, either at (very) high speeds on flawless French highways or feeling like James Bond as I curved around winding trails in search of coteaux and caveau, my (rented) Audi A4 Turbo Diesel purring, Amel Bent’s Nouveaux Français blasting on the Blaupunkt.

It’s odd. Technology was supposed to be enslaving, not liberating, the enemy of democracy, not its savior. We were headed for dystopia, an Orwellian future where technology was to be a black boot on the back of the neck. I watched the year 1984 creep closer and closer, big brother looming large. It came and went, with barely a whimper.

Now, don’t get me wrong: technology can (and has) been turned to evil ends. Much has already been said about the evil ends. The possibilities for more evil abound, even for a company who’s motto is “do no evil.” (It’s just a little to newspeak for my tastes.)

The Open Secrets Effect

But I want to talk about the other side. I want to talk about Jane, and things like Jane. I want to talk about something I call the “open secrets effect,” something that has the power to save one’s marriage from map-reading malevolence, and, perhaps, the power to save democracy from itself.

While it may seem a trivial one, GPS is a good example of the open secrets effect — that magical synergy you get when you mix disaggregate information with extraordinary computational power and deliver it in new ways. In the interest of honesty, I should say that I stole the name of the effect from Larry Makinson and OpenSecrets.org, a site published by the Center for Responsive Politics (CRP). That site is the brainchild of Larry and of Ellen Miller. Ellen is the former executive director of CRP. She’s now at the Sunlight Foundation. In the interest of full disclosure, I should also note that my wife was CRP’s long-time communications director, until the fates led her down a much more fun career path. She’s the reason I get to do these fun trips.

The site, OpenSecrets.org is about campaign finance. It’s also a prime example of the power of opening the kimono, of exposing information that has been shrouded in darkness and complexity.

The Open Secret Effect is what happens when you shine a bright light on data, making it not just available — there are lots of maps of France “available” after all — but accessible, understandable, and personal. When you do that, something magic happens.

For example, originally, Open Secrets was a book. It was published by the Center for Responsive Politics (CRP). It weighed in at probably 10 pounds and was a good four inches thick. But, when CRP took that information, mixed it with a dash of database and a smidgen of internet, suddenly they had an even more powerful agent of change.

That magic mix — data, database, and internet — made the information real and powerful. People could look up their “own” politician, and see just where the money came from. There’s a new twist today, by the way, an initiative called MapLight.org. It promises to take that information to the next level, marrying campaign contributions to voting records. So called “mashups” like MapLight — where two or more previously isolated sets of data are “mashed” together — potentiate the open secrets effect. “You have reached your destination,” says Jane.

That’s the power of the open secrets effect. The mere act of opening the kimono changes behavior and changes the balance of power. Now, more than ever, U.S. political campaigns (and politicians) are dominated by big-money interests. Those interests finance the campaigns and, through those dollars and donuts, pocket the politicians that shape the fabric of our lives. Hopefully, the jig is up. With the open secrets effect of MapLight and OpenSecrets, it should be much more difficult to be bought and sold, especially when everybody knows how cheap the price.

So too, the inherent “connectedness” of the Internet is also changing the relationship of money to power as well. Big money is still there (by the bucket-full in this particular election season) but it is being somewhat counterbalanced by so-called internet campaigns, campaigns that are using the ‘net’s ability to aggregate lots of small things, in this case small contributions.

For good or for bad, campaign contributions have been ruled as constituting “free speech.” As such, more people are speaking than ever before. [Sadly, over two-thirds of those dollars — regardless of source — just end up fueling the creation of traditional one-way TV spots, designed not to inform but to obscure, enrage, or distract. One-way media must perish from this earth.]

Nevertheless, today’s innovative (dare I say social) uses of technology have had a liberating effect. Instead of robbing us of rights, they have increased our participation, restoring power to the formerly powerless. It has strengthened our democracy, not undermined it. To paraphrase Al Gore in his (absolutely terrific) book, The Assault on Reason, “a connected citizenry” is our greatest hope. The new internet is all about connections and the open secret effect.

More and more secrets are being opened. It’s a revolution in knowledge, power, and influence. Suddenly the powerless are powerful, the disenfranchised are raised up. It is something that can change the course of history or something that can get you from village “A” to vineyard “B” (and back again). “Take the roundabout, second exit,” says Jane.

Opening this secret can of worms has the potential to turn power on its head — counterbalancing previously one-sided relationships or creating strength of numbers where there was none previously. It’s directly responsible for the new realization that “consumers” are not passive patsies but active participants. Nowhere is this truer than in the development of software, for example. Software publishing has become a dynamic, interactive process where the customers participate in the product’s development, even doing the product testing.

Previously top-down, one-sided relationships are being changed — for the better IMHO. For example, let’s look at some previously one-sided relationships: between the entrepreneur and the venture capitalist, between the Fourth Estate and the public, and between grantee and grantor. These are being turned on their heads — they’re feeling the open secrets effect. They are being forced to operate in an environment where the formerly obscure is now in public view, i.e., the open secrets effect is at work.

In one of my favorite examples of truly living the Open Secrets life, Southwest Airlines actually made a television show of their inner operations called “Airline,” with a tag line of “We all have our baggage!”

Meanwhile, a site called TheFunded has turned the tables on the world of the holy venture capitalist, dishing up a place that allows entrepreneurs to rate their would-be suitors. TheFunded has changed the equation by opening up the secrets that everybody “knew” but nobody shared. TheFunded has aggregated the voice of the powerless, and in so doing, become powerful. Now the VC’s are beginning to understand the real business they’re in and the nature of their relationship with their customers, the entrepreneur.

A more Web 2.0 example is being done by Google. Google is turning the one-way-medium called “the news” into a two-way conversation by introducing a way to give the subjects of news reports a way to comment on articles written about them. What was a one-way pipe is now a two-way conversation. It chips away at the Fourth Estate’s overwhelming power to set and control the agenda.

Finally, there is a little open secrets project I’m involved with. It’s called GrantsFire. [I don’t have much to show you yet about GrantsFire – but you can look at the hGrant microformat standard, if you want. Microformats are a way of marking up web pages to make them machine readable. Find information here.]

Clearly, grants are no secret, just as maps of France are easy to come by. However, GrantsFire is about seeing and presenting that information in new ways. GrantsFire is an initiative to both establish a standard for publishing machine-readable grants information on the web, and about encouraging foundations to publish such information. Once up and running, with a critical mass of participants, that information can be aggregated by one (or more) sites. People will be able to run the data through a data vegamatic, slicing and dicing by topic, type of support, geographic focus, foundation, dates, and dollars. Who knows what mashups might result. Pe