/home/dkramer

David Kramer’s high-entropy blog

Conflict Is Essential

I recently posted on how failure is essential. Along the same lines of failure being essential to learning, conflict is essential to innovation and change.  I’ve often felt this.  Not everyone feels this way, but I love a healthy debate. Rick Brenner recently published an article in his Chaco Canyon series on this topic, called Teamwork Myths: Conflict. At my last job (Atpima), one of the many wonderful projects I worked on was called TeamBuilder (my name was conveniently left out since I left the company).  You can follow that link to read all about it, but the relevant concept is when you’re building teams that need to work on hard problems that may require out-of-the-box solutions, conflict can lead to new solutions.  Or at least a thorough review of the pros and cons of the known options.  When a team has a well-defined problem and must act quickly, conflict can be bad.  Just like tools, you need different ones for different tasks.

Eating Your Own Semantic Web Dog Food

I was heavily involved in semantic web, ontologies, and natural language processing in my last company.  I was supposed to work on that in my current company. In other words, I’ve been following this stuff for a while.  The realization I came to is that, while it would be cool if everyone added all this metadata to their content on the Internet, and the cylons could take care of complex tasks for us automatically, like “Book me a room in a hotel near the Hynes Convention Center next Friday through Sunday with one queen size bed, bill it to my Visa card, and send the confirmation email to my Blackberry”, it’s not going to happen.  The simple truth is it’s a lot more work than most content creators think is worthwhile, and adding metadata to existing content is nigh impossible.  Just to save some businessman about an hour poking around the Internet for hotel recommendations and booking a room. Read on…

Site info