Steve Krause : Blog

Jason Roberts' "A Sense of the World"

In A Sense of the World, Jason Roberts makes the case that James Holman was the greatest traveler not just of his time, in the 1800s, but of all time before then. On his own funds and initiative, Holman covered at least 250,000 miles. If that was not remarkable enough, Holman was blind.

As Roberts sums up Holman's achievements:

He could claim a thorough acquaintance with every inhabited continent, and direct contact with at least two hundred distinctly separate cultures....Alone, sightless, with no prior command of native languages and with only a wisp of funds, he had forged a path equivalent to wandering to the moon.

Roberts reconstructs Holman's time and travels with a vivid narrative style. The hero makes Roberts' job easier by being continuously remarkable: learning to ride a horse by echolocation, playing politics with Queen Elizabeth, getting thrown out of Siberia by the Russian czar, and (literally) so on.

Along with drawing on Holman's own writings, Roberts deftly taps other original sources and literature for additional color, such as this comment from the time about Edinburgh's polluted air: "you might smoke bacon by hanging it out the window."

I liked the book a lot, but recognizing that the subject matter is well off the beaten path, I suggest you test-drive this short excerpt at the author's site. You will know quickly whether A Sense of the World is for you.

March 14, 2010 in Books | Permalink | Comments (0)

Job Opportunity in CNET's Intelligent Cross-Sell Group

My group at CNET Content Solutions is looking for a Senior Software Engineer. The job posting is below. If you are intrigued, and you have the quals, please apply!

Job Description

CNET Content Solutions is seeking a Senior Software Engineer for its Intelligent Cross-Sell group, located in San Francisco, CA. Intelligent Cross-Sell is a Web service for e-commerce sites that automates and optimizes product recommendations. It is in use by, among others, four of the top ten brands in the Internet Retailer 500 list of e-commerce sites.

The Senior Software Engineer will play a key, lead-developer role within the Intelligent Cross-Sell engineering team. The role combines overseeing other engineers' work, influencing architectural decisions, and owning the design and coding of specific functional areas in Intelligent Cross-Sell.

Required Skills/Experience

  • BS or MS in computer science or equivalent training and experience
  • 5 years' experience working in a team environment developing production-quality code
  • Experience as a team lead
  • Expert knowledge of Java, SQL, and Web applications
  • Exposure to all technical aspects of the product lifecycle: requirements gathering, design, implementation, quality assurance (automated and manual), documentation, support, maintenance
  • Desire to work in a fast paced, cutting edge environment
  • Effective verbal and written communicator: can write clear specs, explain complex ideas, and handle questions with credibility and authority
  • Enthusiasm to be a mentor to junior engineers
  • Can create and execute complicated schedules with interdependent deliverables and resources
  • Can design and conceptualize infrastructure, not just features; can evaluate among multiple solution paths

Desirables

Experience with:

  • Large-scale databases
  • Analytics
  • Data mining
  • Python
  • XML
  • MySQL
  • Apache
  • Web log-file processing
  • HTML/JavaScript/CSS

Must successfully pass a background check.

March 10, 2010 | Permalink | Comments (0)

Copy and Paste Provenance

In today's New York Times, Public Editor Clark Hoyt, wrote about a recent case of alleged plagiarism by a Times reporter. Here is the explanation of how the plagiarism happened:

[The reporter] said he would copy stories from wires, paste them into a file in the editing system, verify the information and then put the material in his own words. At least, he said, that is what he intended to do. When I asked him how he could fail to notice that he was copying someone else’s work, he added further explanation: He said the raw material in the computer files in which he assembled his stories included not only reports from other sources but also context and background from previous articles that he had written himself. When putting it all together, he said, he must have thought the words he copied were his own, earlier ones. "It was just my carelessness in trying to get it up quickly," he said.

It seems like those accused of plagiarism often have this explanation. Hoyt goes on to note...

The explanation was similar to one offered only days earlier by Gerald Posner, a reporter for The Daily Beast, who was caught by Jack Shafer of Slate cribbing sentences from The Miami Herald. Posner, who resigned after even more plagiarism was found, also said that he did not do it intentionally. He said he had poured all his research — interviews, public documents, published articles — into a master electronic file and then boiled it into an article under tight Web deadlines, a process that led to disaster.

This isn't just about reporters cranking out stories on deadline. You might also recall historian Doris Kearns Goodwin had a similar explanation for her appropriation, without quotes, of another author's verbiage in one of Goodwin's books.

In all these cases, the explanation is more believable than not. The benefit of copying was minimal yet the cost, upon detection, was high.

What these people needed was a special copy-and-paste mode that retains the provenance of the copied text. That is, every piece of copied text would automatically say what document or URL it came from. Especially for an organization like The Times, which apparently has its own dedicated "editing system," making such a feature available (or perhaps mandatory) seems like a good idea.

And for the rest of us who use Microsoft Word or Google Docs' word processor, maybe it's an option we will see someday too.

March 07, 2010 in Web/Tech | Permalink | Comments (3)

TypePad Sitemap Template with More Than 100 Entries

Sitemaps are a way to help search engines find pages on a Web site. This blog has its own Sitemap, which I noticed was limited to displaying the last 100 blog entries. That's bad, because I have more than 100 entries, and Google was losing track of some of the early ones.

A Sitemap can have up to 50,000 URLs, so I emailed the support desk of TypePad (the service that hosts this blog), asking what the problem was. The answer was, TypePad's suggested template for Sitemaps uses a template tag called MTEntries, which is limited to showing 100 entries. That's confusing because the relevant part of the suggested template says, as of March 6, 2010, <MTEntries lastn="1000">. Oh well. The person who answered my support question said TypePad was evaluating raising the limit.

It should be raised, or TypePad should provide some other means for directly communicating the presence of more than 100 blog entries. But in the meantime, I'll share a quick workaround I devised. It's ugly, but it works for this blog's 250-odd posts.

In the suggested Sitemap template, I duplicated the block of XML responsible for generating the list of blog-entry URLs. I set the first block's "lastn" parameter to 100. For the duplicate, I also set "lastn" to 100 but I added an "offset" parameter of 100. That means the first block gets the 100 most recent entries, and the second block gets the 100 next most-recent entries. Then I created another duplicate block, "lastn" of 100, "offset" of 200.

That's all I needed (for now). The resulting Sitemap had all 250 postings. I don't know how far this hack scales up, but I figured I'd share the idea. May it be useful for the hopefully short time between when this was written and when TypePad better supports Sitemaps.

FYI, this is the relevant block in the suggested Sitemap template (as of March 6, 2010):

<MTEntries lastn="1000">
<url>
<loc><$MTEntryPermalink encode_xml="1"$></loc>
<lastmod><$MTEntryDate format="%Y-%m-%d"$></lastmod>
<priority>0.8</priority>
</url>
</MTEntries>

Replace that block with the following three blocks:

<MTEntries lastn="100">
<url>
<loc><$MTEntryPermalink encode_xml="1"$></loc>
<lastmod><$MTEntryDate format="%Y-%m-%d"$></lastmod>
<priority>0.8</priority>
</url>
</MTEntries>

<MTEntries lastn="100" offset="100">
<url>
<loc><$MTEntryPermalink encode_xml="1"$></loc>
<lastmod><$MTEntryDate format="%Y-%m-%d"$></lastmod>
<priority>0.8</priority>
</url>
</MTEntries>

<MTEntries lastn="100" offset="200">
<url>
<loc><$MTEntryPermalink encode_xml="1"$></loc>
<lastmod><$MTEntryDate format="%Y-%m-%d"$></lastmod>
<priority>0.8</priority>
</url>
</MTEntries>

If you want to try more blocks, the pattern for doing so should be evident. The only thing you need to change is the "offset" in the first line of each additional block. Just increment it by 100.

One final note: The generated sitemap.xml document did not change after I saved the changes to my Sitemap template. This was apparently due to caching, which a template-save should have immediately overridden but did not. I confirmed this by copying the text of my changed template to a new template, sitemap2.xml, which generated the correct XML file. The next day, when I checked my sitemap.xml again, it had updated to the correct XML, so the cache apparently needs time to detect changed templates.

March 06, 2010 in Pseudorandom | Permalink | Comments (0)

Microattention for Secondary Screens

Think about a desk calendar, the kind that has a clever quote for every day of the year. Now replace it on your desk with a little screen. The little screen not only has the clever quotes, it rotates through other stuff: headlines, stock updates, Twitter, weather, and so on.

You ignore it most of the time, but it's great for the occasional glance when you'd otherwise be waiting for something to happen on your computer. Or when a conference call meanders. Or when you just have extra microattention, meaning you can keep doing what you're doing while sneaking a peek, like seeing a billboard as you drive.

Here is a real-world example: On my desk, away from my computer display, I have a Chumby One, a small WiFi device that I can configure via the Web to display various stuff. Across a few minutes, it will show the likes of:

Chumby_weather_channel

Chumby_onion

Chumby_cnet_news
 
Chumby_bbc 

Chumby_baycam

Chumby_techcrunch
 

These are widgets like those you've seen on computer desktops (Microsoft gadgets, MacOS Dashboard, and so on). I've also got Chumby widgets for Twitter, stock prices, and SmugMug's most popular pictures of the day.

Initially this all may seem like a big time-waster, a weapon of mass distraction. But from my experience, it can be a time-expander, allowing you to do more with the time you have. To understand why, go back to the analogy of seeing billboards on the highway. What if those billboards showed stuff you chose? You would be driving anyway, so anything useful the billboards communicated would be a bonus, if you felt like looking at them.

That last part—your discretion to look or not—is key. It's why widgets on a peripheral display like a Chumby are a different experience from widgets on your computer's normal display. If I had the equivalent of my Chumby's rotating widgets on my computer desktop, they would drive me crazy because they would not be fully ignorable; they would be too much in my field of view. Yet if I hid them—requiring a click or key-press to view them and then another to hide them again—they would not be as effortlessly glanceable as on a peripheral display.

So will Chumbies take over the world? Chumby is a quirky, early entrant in the "connected screens" market, and I wish it/them the best. But a bigger trend is afoot:

  • Small, external USB displays let you sequester desktop widgets to a peripheral screen.
  • Digital photo frames are evolving into connected screens, with content delivered by companies like FrameChannel.
  • Screenphones, while they sit in a dock on your desk or nightstand, are going the same way.
  • Dashboard screens in cars? They are going there too, if you don't end up using a dashboard-docked phone instead.
  • Next-generation remote controls for TVs will have screenphone-like screens, so count them in.
  • Idle TV screens on walls or, in the farther future, walls that are screens? Yep.

In other words, there will be no shortage of screen devices that can enable good use of your microattention. With ever-falling costs of flat screens, and greater use of microattention, expect to see second, peripheral screens where you already have a main screen, and other screens in what today would be unlikely places.

That said, it is interesting to ask what else screen devices could do to support microattentive uses. On one hand, interactivity is helpful if you want to get more info on something you see (the Chumby One has a touchscreen, and some widgets have touchable controls). On the other hand, interactivity will be an exceptional use case, like stopping the car to learn more about a billboard's content. In my case, if I see something on the Chumby that I want to know more about, I just Google it on my desktop rather than interacting with the Chumby.

More interesting to me would be a peripheral screen's having a video camera that can track when my eyes viewed the screen and what I viewed. For example, if a headlines widget eye-tracked the headlines I saw, it could show other headlines on subsequent rotations.

And to those who make the widgets and/or content in them, what new experiences can be had for an audience that consumes your media via a sequence of occasional glances?

My microattention and I will be eager to find out.

February 28, 2010 in Web/Tech | Permalink | Comments (0)

Cloud and Jaffe's "The Fourth Star"

The Fourth Star by David Cloud and Greg Jaffe is about the long struggle, and eventual victory, of an idea that is now the core of the U.S. strategy in Iraq and Afghanistan: that if the enemy isn't going to fight a conventional war, then we need to win by means other than just fighting. That idea is embodied by General David Petraeus, who took command of U.S. troops in Iraq from General George Casey Jr. in 2007.

The authors use that transition to summarize their larger theme:

Ever since [Vietnam], senior Army leaders had tried, and ultimately failed, to keep their force from becoming too deeply embroiled in messy political wars that defied standard military solutions. It was a pattern that had repeated itself in Haiti, Somalia, the Balkans, Afghanistan, and then Iraq, where generals often focused more on exit strategies than plans for victory. Petraeus wasn't interested in the drawdown plans often advanced by Casey. Instead he wanted to push U.S. troops into cities and leave them there. Only a heavy and sustained American presence could win the war, he believed.

Moreover, this heavy and sustained presence was not about engaging the enemy. Rather, it was primarily about protecting and policing the population, controlling sectarian violence, and turning the pragmatic majority against the insurgents.

Whereas U.S. forces previously concentrated themselves in highly fortified bases, they would now disperse among smaller posts within population centers. Whereas rebuilding Iraq was often about multiyear, multibillion-dollar reconstruction projects, it would now include immediate band-aids like getting the sewage out of the streets. Whereas conventional tactics were about applying overwhelming force to win the immediate battle, the new thinking included paradoxes such as "Sometimes, the more force is used, the less effective it is."

To tell the story of this paradigm shift, The Fourth Star follows the careers of Petraeus and three other generals in the Iraq war: Casey, John Abizaid, and Peter Chiarelli. The four biographies make clear that each man was an extraordinary soldier, yet Casey and Abizaid ended up being the last of the old guard; Petraeus and the lesser-known Chiarelli ended up the first of the new.

Abizaid is a particularly tragic figure. An Arabic speaker with a long history in the Middle East, he knew the region better than any senior soldier, not to mention his civilian superiors. Like Petraeus, he had long ago concluded that the military needed to get much better at winning the peace in addition to the war. Yet he took charge in Iraq in 2003, after the initial rout, in the "Mission Accomplished" era. Taking orders from the then-swaggering Bush/Rumsfeld political leadership, he and Casey became the executors of policies that initially were in denial about the insurgency—thus giving it time to build—and then tried to fight it with conventional means.

Conversely, Petraeus was in the right place and right time. As a regional commander in Iraq, he employed his signature counterinsurgency tactics to good effect, all the while working personal relationships with the press to document his rising star. By late 2006—after years of deteriorating conditions, the Republicans' loss of Congress, and Rumsfeld's resignation—Petraeus was the obvious choice for change. However, it's interesting to ask what would have happened if Petraeus was in Abizaid's role several years earlier, whether Petraeus would have been able to accelerate America's adaptiveness or whether he would have been cast aside by the civilian leadership, as was General Eric Shinseki when he requested too many troops for post-war Iraq operations.

While The Fourth Star invites such conceptual questions, it's first and foremost a storytelling book. It is especially strong conveying the stories of what actually was happening in Iraq behind the headlines, from the bureaucratic infighting to the real fighting on the battlefield to the twisted relationships among the U.S. and various Iraqi factions.

As an example of Cloud and Jaffe's eye for the telling detail, here is an aside about an Iraqi army unit being trained for self-sufficiency:

They couldn't feed themselves without U.S. help or repair broken equipment. When one of their soldiers was killed by insurgents, the unit wasn't even able to ship the body home. Instead the battalion commander ordered his men to put the decomposing corpse in a room with the air conditioning turned on full blast. In a scene reminiscent of a Faulkner novel, the Iraqis then passed a hat hoping to collect cab fare for the 500-mile trip to the dead soldier's family home in Basara. Eventually [the U.S. officer in charge] paid the fare.

As with this quote, the daunting nature of the American—and Iraqi—challenge in Iraq pervades the book, not in a polemic way, just as myriad matters of fact.

Before Petraeus' promotion in 2007, things were bad, going to worse. By embracing change, and investing in it with an additional troop surge, the momentum reversed. Three years later Iraq has seen progress, but a decisive win is a long-term proposition. Near-term success amounts to transitioning most of the military burden from the United States to native Iraqi forces, while maintaining political and economic stability—any aspect of which will strike a reader of The Fourth Star as a formidable task.

Yet amid the ongoing uncertainty in Iraq and Afghanistan, The Fourth Star makes the case that an important victory of ideas has already occurred. It took unusual leaders like Petraeus, who creatively bucked the system from within, and it took a trip to the edge of failure in Iraq, but the U.S. military learned and adapted. The Fourth Star is an engaging chronicle of that slow, hard path toward change.

[Here is the Amazon link to The Fourth Star.]

February 20, 2010 in Books | Permalink | Comments (0)

When Reporters Don't Want to Hear It

From an interview with robotics expert Noel Sharkey:

Isaac Asimov said that when he started writing about robots, the idea that robots were going to take over the world was the only story in town. Nobody wants to hear otherwise. I used to find when newspaper reporters called me and I said I didn't believe AI or robots would take over the world, they would say thank you very much, hang up and never report my comments.

This brought back a memory from my SRI days, when I was regularly interviewed by reporters. I remember a reporter called me on the day of some big news (I forget what it was), wanting my take.

The normal routine would be for me to provide a pithy quote, which the reporter would use as the voice of an independent expert. However, half-way through my commentary, his keyboard stopped clickety-clacking. "That doesn't get me where I need to go," he sulked, more to himself than me.

Reporters usually like contrarian views, but apparently the expert slot in this story was already tailored for a concurring opinion. He was on deadline, as most reporters are when they call. It was easier to find another expert than redo the story.

I'm not naming the reporter because this run-in was the exception, not the norm, with him. He was a quality reporter who later became the technology bureau chief for one of the biggest U.S. papers—which makes the point stronger: Even quality reporters can succumb to finding only the facts and opinions for the story they want to tell.

The good news is, in my experience with a wide range of reporters, this situation was rare. But then again, I wasn't daring to question whether robots would take over the world.

February 15, 2010 in Pseudorandom | Permalink | Comments (0)

Review: "A History of the World in 6 Glasses" by Tom Standage

In Tom Standage's A History of the World in 6 Glasses, civilization is what civilization drinks: "Just as archaeologists divide history into different periods based on the use of different materials—the stone age, the bronze age, the iron age, and so on—it is also possible to divide world history into periods dominated by different drinks."

Standage starts with beer, which was fundamental to early agricultural civilizations in Mesopotamia and Egypt. As the liquid form of plentiful grains, and safer than the local water to drink, beer was a staple of diets. It was also a popular form of payment and currency. By its ubiquity, beer became, and to a large extent still is, the drink of the everyday worker.

In contrast, wine was emblematic of Greek and Roman civilizations, which stratified wines by type and age. Everyone drank wine, but the elites had elite wine, the commoners had common wine, and so on in between. This association of wine with connoisseurship persists today, as does the Mediterranean region's cultural preference for wine as its main social drink.

The other four epochal drinks are distilled spirits (their bang-for-buck compactness made them a key trading currency in the Age of Exploration), coffee (the Age of Reason played out in coffeehouses), tea (British Empire), and Coca-Cola (the American Century and globalization).

Each drink gets a cultural biography that explores "the ramifications of who drank what, and why, and where they got it from." Standage covers that territory broadly, visiting the histories of agriculture, religion, philosophy, and commerce (among other topics) at opportune moments.

So, for those interested in an offbeat, eclectic take on history, A History of the World in 6 Glasses should slake thy thirst.

February 06, 2010 in Books | Permalink | Comments (0)

The Power of the Portfolio: VCs and Entrepreneurs

Kudos to the venture-capital (VC) firm First Round Capital for offering its entrepreneurs an exchange fund: If First Round invests in your startup, you can exchange a small percentage of your own company shares for shares in a fund tied to the total First Round portfolio's performance. As First Round's managing director Josh Kopelman said, "When I was an entrepreneur, I remember the feeling of having all my eggs in one basket -- and it is our hope that this fund will remove some of that stress." Assuming the details of the plan are consistent with its spirit, it will be a great option for entrepreneurs and a positive differentiator for First Round.

That said, beyond the normal VC role of facilitating relationships among portfolio companies, how else can VC firms leverage their portfolio-holder position on behalf of those in the portfolio? For example, could a VC firm share a health-care/benefits program across all its early-stage startups? Each startup would pay its own way, just as if the startup had its own program. However, a portfolio-wide program would have better terms due to its size, would eliminate the cost and hassle of each startup finding and establishing its own plan, and would offer COBRA for individuals at failed startups (who ordinarily would be out of luck, since COBRA is predicated on the continued existence of a company).

I am sure other examples exist, and I look forward to seeing them emerge for the benefit of entrepreneurs and VCs alike.

January 30, 2010 in Business | Permalink | Comments (0)

Coding for an Audience

In Peter Seibel's Coders at Work, I particularly enjoyed a story from Bernie Cosell, who was on the team that wrote the original routing software for the Internet. He was talking about a theme that occurs throughout the book, the idea that a good program is written not just for the computer but also for the humans who may need to understand the program or change it later—including the program's original author:

At some college they had a two-semester course from September right through May and they had you work on some fairly hard program at the beginning. What they didn't warn you was in April they were going to make you work on the program again, having now really run you through the hoops on other things. The idea was for you to be stunned at how hard it was to remember whatever it was you thought you understood perfectly clearly just six months ago.

This lesson is inevitable in any programmer's career: You must write code for an audience, at minimum for the future you. It's a well-known concept in software development, and is probably said often in various classes. But I suspect it's rarely learned until the student gets burned by his or her own code, and that's what the above does safely.

So, to whichever school did it, I thank you on behalf of the students and their future employers.

January 24, 2010 in Web/Tech, Weblogs | Permalink | Comments (1)

Next »
My Photo

Bio

VP Analytic Products, CNET Content Solutions (current); CEO and co-founder, ExactChoice; CTO and co-founder, Personify; researcher and co-founder, iVALS and Media Futures Program (both at SRI International); based in West Hartford, Connecticut, and San Francisco, California.

This is my personal blog. It speaks for me, not my employer.

Contact

email

Site Search

Feed

feed iconleft arrow What is this?

Twitter

    follow me on Twitter

    Recent Posts

    • Jason Roberts' "A Sense of the World"
    • Job Opportunity in CNET's Intelligent Cross-Sell Group
    • Copy and Paste Provenance
    • TypePad Sitemap Template with More Than 100 Entries
    • Microattention for Secondary Screens
    • Cloud and Jaffe's "The Fourth Star"
    • When Reporters Don't Want to Hear It
    • Review: "A History of the World in 6 Glasses" by Tom Standage
    • The Power of the Portfolio: VCs and Entrepreneurs
    • Coding for an Audience
    • "Coders at Work" by Peter Seibel
    • Recovering Energy from Shock Absorbers (Levant Power)
    • Book Review: Invictus by John Carlin
    • Klosterman's "Fargo Rock City"
    • "The Bloomberg of Wind" (Wind Pole Ventures)
    • Full-Circle Guitar
    • A Building to Behold: Yale's Beinecke Library
    • Blind Man's Bluff by Sontag and Drew

    Categories

    Analytics/Numeracy: 52
    Books: 29
    Business: 43
    Current Affairs: 2
    Design: 15
    Food and Drink: 1
    Music: 4
    Personal: 13
    Pseudorandom: 46
    Science: 3
    Web/Tech: 22
    Weblogs: 1
    Powered by TypePad
    This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 2.5 License.