Tabblo

Ned Batchelder recently announced the availability of Tabblo. It's a new photo-sharing site focused on telling stories. I think it's a great idea and the interface is very cool. Ned and his colleagues should be very proud.

Here's my first Tabblo. Best of luck to Ned and the whole Tabblo team.

Reduced Speed Ahead

Southern New Hampshire is in the midst of the worst flood since the 1930s. Here's a shot taken this morning. It shows the Souhegan River overflowing its banks in Amherst, New Hampshire.



By the way, there are some great New Hampshire Flood sets on Flickr here, here and here.
 

All Which Isn't Singing

all which isn't singing is mere talking
and all talking's talking to oneself
(whether that oneself be sought or seeking
master or disciple sheep or wolf)

gush to it as diety or devil
-toss in sobs and reasons threats and smiles
name it cruel fair or blessed evil-
it is you (ne i)nobody else

drive dumb mankind dizzy with haranguing
-you are deafened every mother's son-
all is merely talk which isn't singing
and all talking's to oneself alone

but the very song of(as mountains
feel and lovers)singing is silence

-- ee cummings
 

Home Improvement

Our 100-year-old house in Southern New Hampshire includes a twenty-year-young, two-story addition. The addition was built on top of six eight-by-eight wooden posts. The problem is some of the addition's main beams are sagging and the posts are slowly slipping off their footings. This is not imminently dangerous, but it will certainly make it difficult to sell the house when the time comes. (Why didn't our home inspector warn us when we bought the house? Good question, but I'm not going there.)

In any case, we are in the midst of a major home improvement project to fix the problem. Our contractor is going to replace the wooden posts with a solid concrete foundation. He'll dig, pour and frame above the foundation, one side at a time. The photo below shows the concrete forms on the interior wall.



A few friends and family members (probably very few) will be interested in more pictures like this, so I've started a photo journal of the project. It's called The Little Dig. If you are interested, you can even subscribe to this feed and watch the progress. Enjoy.
 

A Total Miracle

The Notes vs. Outlook meme comes and goes. Because I put in my two cents last January, I occasionally still get comments on the topic. I don't want to restart that conversation -- really I don't -- but I do want to highlight a comment I recently got from one Daron Lawing. Daron's comment is much broader than Notes vs. Outlook. It's a profound appreciation of the "pure thought-stuff" we call software:

I'm a Notes end user ... I get my email through Notes and I send email through Notes. What's the big deal? Outlook looks like [it] does the same thing. For me the fact that I hit this button, the machine in front of me comes to life, and images appear on the screen then I type on this keyboard and my brother in North Carolina can get a message from me in a matter of minutes is frankly a total miracle. [You] geeks need to lighten up and be in awe and wonder about both Outlook and Notes ;)

Indeed.

Thanks for the reminder, Daron.
 

Spell Checker Irony

The Blogger spell checker, when I remember to use it, saves me from posting entries chock full of misspelled words. It's great, but it has trouble with a few common words. "Blog" is one. It also has trouble with "Blogger" and "Google". Ha!
 

Advice for New Photographers

In 10 Tips for the New Digital SLR Photographer, Thomas Hawk gives some great advice to budding photographers. Although some of the tips apply only to single lens reflex (SLR) cameras, many of them make sense if you have a point-and-shoot camera like mine.

For example, "Join Flickr" (#5) and "Take lots and lots and lots of photos" (#9) are good tips for anyone. Even "ISO, ISO, ISO" (tip #1) applies if you have a point-and-shoot camera with an advanced mode.

If you want to get more serious about photography, the message is simple: Take more pictures, learn all about your equipment, and as often as possible, try something new like shooting in low light. By the way, Thomas Hawk is a master of capturing great pictures at night. Take a look at his "night" tagged photos for some samples.
 

Dual Ladder Delusion

There are two kinds of engineers -- those who prefer a career in management and those who prefer to climb the technical ladder. At least that's the conventional wisdom in many large companies. As the authors of a 1986 study concluded, it's really a cruel joke.

The study is called The Dual Ladder: Motivational Solution or Managerial Delusion?. It was authored by Thomas J. Allen and Ralph Katz, both associated with MIT's Sloan School of Management, and was originally published in R&D Management. I wish I could link to an electronic copy on the web, but I can't. A Google search results in many citations, but no copy of the article. *

The authors begin their article with a frank assessment of the dual ladder's effectiveness:

The problems underlying the dual ladder concept are several ... [One problem is] organizations tend, over time, to diverge from the initial design and intent of the system. For the first few years, the criteria for promotion to the technical ladder may well be followed rigorously, but they gradually become corrupted. The technical ladder often becomes a reward for organizational loyalty rather than technical contribution.

If the dual ladder is often implemented poorly, there must be a reason companies keep the system. Perhaps, if nothing else, it is an effective way to motivate technical talent. To test this theory, Allen and Katz surveyed managers and engineers in "nine major U.S. organizations". They asked:

To what extent would you like your career to be:

1. a progression up the technical professional ladder to a higher-level position?
    
2. a progression up the managerial ladder to a higher level position?
    
3. the opportunity to engage in those challenging and exciting research activities and projects with which you are most interested, irrespective of promotion?

The 2157 managers and engineers surveyed were asked to rate each of the above choices on a scale of 1 to 7. The results were 32.6% preferred "b", the management ladder, 21.6% preferred "a", the technical ladder, and 45.8% preferred "c" the opportunity to engage in challenging projects. In other words, twice as many engineers were motivated by challenging projects than by promotion up the technical ladder. Furthermore, this tendency toward a preference for challenging projects, irrespective of promotion, increased with age.

Although Allen and Katz did not study the software industry specifically, their conclusions are consistent with those of many seasoned software developers. That is: There is an inherent reward in doing interesting work. Even when there is a technical ladder available, many developers find more satisfaction in working on challenging projects than in climbing the ladder. The technical ladder is often the predominant rewards system for developers, but as you climb the ladder, you usually design and write less software. Therefore the dual ladder system is aligned neither with most developers' goals nor with the ultimate goal of the company -- to produce and make money on software.

What do you think? Is the dual ladder a good system that is just imperfectly implemented? Is it, like democracy, the worst system "except for all those others that have been tried"? Or is there a much better system out there?

* Update: Here's a copy of the article from MIT's on-line library. This version was published in 1985.
 

Camera Review: Canon PowerShot S2 IS

I recently bought a new digital camera. It's only the second digital camera I've owned. Although I am far from an expert on cameras, I want to record my first impressions. If you are searching for a camera, this might help, but to learn all about the Canon PowerShot S2 IS, please check out this review or one of the other excellent reviews on the web.

There are several things I love about the PowerShot S2 IS. The first three are Zoom, Zoom, Zoom. The S2 IS is a long zoom camera with a built-in 12x optical zoom lens. If you have been struggling to get close-up shots with a 3x zoom camera, you'll love this feature. For example, I took this picture of Rita Jeptoo, winner of the 2006 Boston Marathon, from 40-50 feet away. With my old 3x zoom camera, I'd have to be 10 feet away to get the same shot. Of course at 10 feet, I wouldn't have been able to take the picture at all. I would have been whisked away by the BAA security volunteers.

The IS in the camera's name stands for Image Stabilization. That is my next favorite feature. Even if you have steady hands, at 12x zoom, you will find it difficult to keep most cameras steady enough to get a good shot. Image stabilization compensates for shaky hands. You will still need a tripod for long exposures (for example, in low light), but image stabilization works great for well lit scenes.

This may sound funny, but another great feature of the S2 IS is the batteries. It runs on four standard AA batteries. I bought some rechargeable NiMH batteries for everyday use, but I keep four ordinary alkaline batteries close by just in case. I guess it is common for Cannon cameras to run on AA batteries, but the elegant simplicity of this idea is new to me. My old Sony camera runs on an expensive rechargeable cell. I could never justify the expense of buying a backup battery. More than once, I was snapping pictures when the battery lost its charge. This won't happen with the S2 IS.

Although I am convinced the S2 IS was a wise choice, is has two notable drawbacks. First, the LCD screen is small compared with some other cameras in its class. As an example, the Sony DSC-H1 has a much bigger screen. I don't like to admit it, but at my age, I sometimes have to strain to read the S2 IS display. As I get more familiar with the features, this problem may become less severe.

The other big drawback is the lack of a pre-set high-speed shutter mode. I take lots of pictures at road races. With my old Sony camera, I could easily select high-speed shutter mode for stop-action photos of runners in action. With the S2 IS, I have to tinker with Tv (shutter-speed priority) or Av (aperture priority) modes to get the same effect. I suppose this could be a blessing in disguise. With fewer pre-set modes, Canon is forcing me to learn about the more advanced features of the S2 IS. It never hurts to learn something new.
 

110th Boston Marathon

Robert Cheruiyot set a new course record (2:07:14) at yesterday's Boston Marathon. He shaved one second off the 1994 mark set by fellow Kenyan, Cosmos Ndeti. Rita Jeptoo (above), also from Kenya, won the woman's race in 2:23:38.

For more photos, see my 2006 Boston Marathon set on Flickr.
 

Google Calendar

Blog union rules require me to mention the launch of Google Calendar. Since tech.memeorandum is buzzing about the launch, I'll take the easy way out. Go there for all the coverage.

Most of the early reviews are positive, and I like it too. Little touches like event reminder buttons make all the difference. For example, this button adds an important reminder to your Google calendar:

Monday, April 17 is Tax Day!

Very nice.
 

San Francisco Earthquake

April 18 will be the 100th anniversary of the great San Francisco earthquake. The magnitude 7.8 earthquake devastated the city. The ensuing fire caused even more destruction.

Replace "earthquake" with "hurricane" and "fire" with "flood" and the story sounds a lot like New Orleans in 2005. Luckily New Orleans can learn from Frisco's mistakes. For example there is this word of caution in a U.S. News story about the quake:

As one civil engineer, John Debo Galloway, put it soon after the disaster: "The distant observer will ask why, with virgin ground before it, the city did not cut avenues, widen streets, and build nothing but incombustible buildings." For the business elite that ran the city after the disaster, such safety measures were not an option. "The city had suffered from the greatest fire in history," Galloway wrote. "What San Francisco needs is the cheapest building possible in which business can be done, to insure the community enough to eat. The other subjects can wait."

For more on the 1906 San Francisco earthquake and fire see:

• National Public Radio's ongoing coverage
  
• USNews.com coverage
  
• J.B. Monaco's period photos of the quake's aftermath

 

Three Years is Enough

April 6, 1864 -- A solemn anniversary is upon us. On April 12, it will be three years since the Confederates fired on Fort Sumter to begin this tragic war. We did not start the conflict (though one could argue the Republican administration provoked it) and it is true most Northerners originally supported the war. However, let us mark this anniversary with an inventory of our progress, and let us hope the President will do the same.

To be sure, there have been some successes. Last July, General Meade repelled a strong Confederate force at Gettysburg. It has been nine months since Robert E. Lee last ventured north of the Potomac. The day after the victory at Gettysburg, General Grant accepted the surrender of Vicksburg and gained control of the Big Mississippi. Last November, Grant routed the Army of Tennessee at Chattanooga. Now Grant has been promoted to lead the entire Union Army. He is the sixth man to lead the army in these three long years. Without a doubt he is the most capable.

However, we must also consider the costs. The number of killed, wounded or missing at Fort Donelson, Tennessee was close to 20,000. The casualties at Shiloh, Tennessee were over 23,000; at Stones River, Tennessee -- over 24,000; at Second Bull Run -- more than 25,000; at Antietam -- 26,000; at Chancellorsville -- 30,000; and at Chickamauga -- over 34,000. At Gettysburg, more than 51,000 Americans were killed, wounded or missing. Those are just the figures for the costliest battles so far. To force the South to surrender, we must now chase Robert E. Lee into Virginia. General Grant's army will no doubt suffer tens of thousands of casualties at the hands of a desperate Confederate defense.

And what of the Deep South? With Grant in Virginia, "Crazy Bill" Sherman is now in charge of the western offensive. Sherman lost his nerve after Shiloh. Can he lead his troops to victory in the Deep South? Many Northerners are deeply troubled by Sherman's appointment.

Of course, the quality of our military leaders is only part of the problem. What really concerns most Northerners is our confusing war aims. Two years ago, the President said:

My paramount object in this struggle is to save the Union, and is not either to save or to destroy slavery. If I could save the Union without freeing any slave I would do it...

But within a few months, Lincoln issued his Emancipation Proclamation. We have no great love for the institution of slavery, but freeing the slaves has reduced the chances of restoring the Union. How much more tenacious will the Confederate Army be now that they are defending, not just their homes, but their way of life? One can only conclude the President lied about his war aims. For Abraham Lincoln, this war has been about slavery all along.

Polls show only 30% of the North now supports the war and President Lincoln's approval rating is at an all time low. It is time Lincoln faced the facts. He cannot possibly win re-election in November and we cannot restore the Union. Let's bring our troops home and let the South go.
 

Book Review: The March

The March, by E.L. Doctorow is the best Civil War novel I've read in ages. It follows General William Tecumseh Sherman's march from Atlanta to Savannah, through South Carolina, and on to Raleigh, North Carolina. Sherman himself makes many appearances in the book, but it is not a biography of the general. Doctorow gives equal time to dozens of other characters including a pair of Confederate deserters, a displaced Southern debutante, a brilliant Union field surgeon, and perhaps the central character, a precocious freed slave named Pearl.

At times the novel wavers between existential despair and existential absurdity. Favorite characters are killed or otherwise left by the way side as the rest march relentlessly on. Other main characters don't appear until the journey is two-thirds complete. At first, Doctorow's apparently haphazard plotting drove me crazy, but he seems to be making a point. This is war. Don't get too attached to anyone.

What's constant throughout is Doctorow's beautiful prose, masterful strokes in character development, and attention to historical detail. Abraham Lincoln even makes a brief appearance. In the hands of another writer, the scene might have been corny or unconvincing. Doctorow's glimpse of Lincoln is hauntingly believable.
 

Boston Marathon Countdown

The 110th Boston Marathon is just over two weeks away. Race day is Monday, April 17. After months of training, most entrants are tapering. The hard work is done. Now it's time to cut back on the mileage, pray for good weather ("It can't be hot four years in a row."), keep a positive attitude, and try not to go stir-crazy. I've never run a marathon, so I've never experienced the mental stress of the marathon taper, but I know the signs. It can be a tough time for runners of all abilities. Hang in there, everyone.

Lots of people are excited about this year's elite field of runners. Hailu Negussie of Ethiopia will be back to defend his 2005 title. As usual, there will be a strong contingent of Kenyans. But the buzz is all about the American field. Alan Culpepper (fourth place in 2005) and Meb Keflezighi will lead the strongest American field in years. Could this be the year an American takes first in the men's race?

Luckily I'll have a front-row seat -- well, not a seat really. Just like last year, I'll be working the leader board with my brother and sisters. We just received confirmation of our assignment this week. I can't wait.
 

JavaScript Utility for Fixing URLs

Yesterday, I cancelled my dial-up ISP account. If you've been through the change-of-ISP experience, you know it can be tedious. I forwarded my email to a new account and I dutifully notified dozens of people and companies about my new email address. The last problem to solve was moving the many images stored on the web space provided by my old ISP. I've posted many Runtime Log entries that refer to those images. To avoid broken links in my blog's archives, I had to move the images to a new home.

Actually, the easy part was copying the image files to a new location on the web. The harder part was figuring out how to fix the references to those images in old posts. I could have edited each post by hand, but that would have been tedious and error prone. Even worse in my estimation is the edits would have caused Blogger to update my RSS feed. The old posts would look like they had been updated, when in fact I had just changed a URL or two.

I decided a better approach would be to leave the old posts alone and fix image URLs as each blog page is loaded into the browser. With help from a friend (thanks, Terry!), I wrote a few lines of JavaScript. The code is in a file called fixer.js.

To execute the code, I made two changes to my blog template. I added a <script> tag to the header:

<script type="text/javascript" src="http://mysite/fixer.js" />

Then I added an onload attribute to the <body> tag:

<body onload="fixImagesAndLinks('oldsite', 'mysite')">

Voila! The old URLs are now magically fixed. In a way, this is a kludge. I wouldn't recommend this approach for a production web application, but this is just a hobbyist-type blog. Sometimes a kludge is the right tool for the job.
 

Tenants Wanted, Apply within

Not Enough Enterprise

It's been a while since I tuned into The Daily WTF. (Warning: Regular readers of The Daily WTF may experience serious misgivings about the state of the art of software development.) It's probably not healthy keep up with all the insanity at WTF, but Bitten by the Enterprise Bug really made me laugh:

... their system wasn't the greatest, but it was fairly documented, easy to work with, and, most importantly, did the job. But one thing it lacked, so said upper management, was "enterprise." And that is something that no system should be with out.

Time to bring in the enterprise consultants!
 

You Are What You Post

Have you ever regretted a comment you posted to someone's blog? Do you wish you could erase your posts from that alt.anarchism discussion way back in 1992? According to You Are What You Post, you should be concerned:

... because today there are two of you. There's the analog, warm-blooded version ... Then there's the online you, your digital doppelganger; that's the one that is growing larger and more impossible to control every day.

And:

Googling people is also becoming a way for bosses and headhunters to do continuous and stealthy background checks on employees, no disclosure required.

This is a good reminder to be careful what you say on the Net and how you say it. I am not advocating self-censorship, but it's worth looking down the road before you post. Are you sure you won't regret your words five years from now?
 

The Evolution of Software Design

I think Software Development's Evolution toward Product Design* is an important essay. The author, Danc at Lost Garden, gets a lot of things right. His four distinct eras of software development sound about right to me. I don't quite remember "The Technocrat Era", but I lived through the "Early Business" and "Late Business" eras. I know first hand many products of those eras confounded users' expectations.

On the other hand, I think Danc is being unfair when he implies each product of those bygone eras was nothing more than "a pile of poo". His artist's rendition is very funny, but it's still unfair. Danc is also too sanguine about the glories of the "Product Design Era".

Danc seems to believe the key to successful software development is to involve people in berets (artists and designers) early in the project life cycle. He refers to a so called "Production Pipeline" in which the people in berets lay the ground work for pliant programmers. To be fair, Danc doesn't think this will be easy:

Unfortunately, many companies that attempt to adopt a product design philosophy will also fail, despite their best efforts. Cultural change is hard work. To adopt product design you must alter the most basic DNA of the company's values.

It's true we need cultural change and he's right it won't be easy, but inertia is not the only problem. In my opinion, the bigger problem is the people in berets don't have all the answers. They certainly don't always agree on the answer.

For example, many designers are orthodox User Centered Design (UCD) disciples. They design products for user personae and insist the software must always adapt to the user. They can cite chapter and verse from the high priests of UCD including Alan Cooper and Don Norman. But Don Norman himself recently broke ranks with UCD orthodoxy. In Human-Centered Design Considered Harmful, Norman dropped some bomb shells:

HCD asserts as a basic tenet that technology adapts to the person. In [Activity-Centered Design], we admit that much of human behavior can be thought of as an adaptation to the powers and limitations of technology. Everything, from the hours we sleep to the way we dress, eat, interact with one another, travel, learn, communicate, play, and relax. Not just the way we do these things, but with whom, when, and the way we are supposed to act, variously called mores, customs, and conventions.

People do adapt to technology. It changes social and family structure. It changes our lives. Activity-Centered Design not only understands this, but might very well exploit it.

And:

Now consider the method employed by the Human-Centered Design community. The emphasis is often upon the person, not the activity. Look at those detailed scenarios and personas: honestly, now, did they really inform your design? Did knowing that the persona is that of a 37 year old, single mother, studying for the MBA at night, really help lay out the control panel or determine the screen layout and, more importantly, to design the appropriate action sequence? Did user modeling, formal or informal, help determine just what technology should be employed?

I think Norman's Activity-Centered Design principles are much saner than strict UCD, but the art of user interaction design is still evolving. The people in berets don't have a silver bullet. It is unlikely they ever will. User interaction design, like software architecture, is hard work. It will be another era or two or three before we get it right even most of the time.

---

* via Ned