Archive for the ‘Reviews’ Category

Book Review: Crucial Confrontations

Sunday, January 17th, 2010

Crucial confrontations book coverMany of us would admit to failing to face up to people who have let us down. The authors of Crucial Confrontations provide numerous examples of this effect that have led to serious cost to companies, human relationships and even lives. However, observing the problem isn’t enough to solve the problem, because the problem lies in people’s ability to confront people. More specifically, it lies in their perceived ability: people think they won’t be able to have a productive confrontation, so they avoid doing it.

Luckily, as well as diagnosing an insidious problem this book provides clear and actionable advice that could be helpful to anyone, whatever their current level of communication skills. The authors blend well-observed general principles with specific examples from professional and personal contexts. They have done particularly well to reduce a potentially confusing topic to a single clear model that is simple enough to comprehend and general enough to be useful.

The scope of the book is both broad and narrow. It’s narrow in that it focuses almost exclusively on a single case: people who have violated an agreement or expectation. However, in a sense this still has great breadth since these situations occur in all walks of life. The examples in the book show how the principles apply equally well in work and at home.

I never feel like I’ve written a fair review unless I’ve picked a few holes in a book, and I’m struggling to do so here. The worst I can say is that this isn’t an instant classic, if for no other reason than its narrow scope. However, I can’t think of anyone who wouldn’t be well advised to give it a read.


First thoughts on the Kindle

Monday, December 28th, 2009

Being in the UK I’m obviously late to the Kindle party since they only became available here a few months ago. I got mine a few days ago (as a Christmas gift from my wonderful parents), and I’m excited enough to write about it here even if it’s all been said before.

I won’t say too much about the physical device itself, which functions very well. The e-paper screen is a pleasure to read from. The slightly reduced contrast means it’s tough in very dim light, but the trade-off of being able to read in bright sunlight is well worth it. The inclusion of a qwerty keyboard is a real marmite feature, but on balance I’m glad it’s there.

What really excites me about the devices is its potential to change the way I read. In the past I’ve left a trail of half-completed books in my wake, as I’ve never had the right one with me. Sooner or later I’d forget where I was in a book or even that I was reading it in the first place. If nothing else, the Kindle works well as a way of centralising my collection and tracking where I am with each one. Could I do the same with a few cheap bookmarks and a large sack to carry the books? Kind of, but the point is that I never did do that.

The built-in mobile phone circuitry that supports “whispernet” (global wireless delivery of books) looks on paper like massive over-engineering, since I purchase books far less frequently than I sit down at a computer. However, it changes the nature of the device from a portable book collection to a portable library, and that starts to feel like something out of a culture novel (the series of science fiction stories set in a high-technology utopia.)

Whispernet really comes into its own for newspapers and magazines, which benefit especially from arriving with you fast and effortlessly, and from old issues not taking up space. At the moment the catalogue of magazines is small and many suffer from the lack of graphics, but there are already some good titles that are very keenly priced. If I could transfer my subscription to The Economist to Kindle I might never read a paper magazine again.

One of the most overlooked things about newspaper and magazine delivery is its potential as a monetisation platform. Because it’s linked to your Amazon account, you can pay large or small amounts for content with ease. It may seem odd to say that I like having to pay for content, but he who pays the piper calls the tune. If I want something, I’d rather pay for it than hope that some advertiser values my eyeballs highly enough to pay for it on my behalf.

Using an electronic format essentially kills the second-hand market: since data doesn’t get worn out like a paper book does, resale of e-books by customers would compete unacceptably with new sales. Therefore Amazon has no choice but to prevent resale from happening. I don’t have a problem with this, provided that publishers recognise it and price their books accordingly. Second-hand sale of a book (whether for money or swapping in an informal economy) helps to defray the high cost of acquiring new books (at least part of which is in printing cost, and cross-subsidising printing of unsuccessful books).

In this sense, a Kindle book is less valuable than a brand-new hardback, since it has zero resale value. In the case of back-catalogue books it is also competing against virtually free copies of the dead-tree version from charity shops or Amazon Marketplace, which further lowers the price I’m prepared to pay. I suspect that the publishers who realise this and price accordingly will benefit.

One last thing about copyright: I don’t like the Digital Rights Management (DRM) of the Kindle. DRM is the technology that binds a copy of a book to a particular physical device, preventing you from lending the book to a friend or using it on an e-book reader not made by Amazon. It’s not unduly restrictive in everyday use, but the prospect of buying my entire collection again if Sony wins the format war is a bit of a downer.

However, I think the best way to ensure DRM goes away is to back up my voice with my wallet. DRM on music is on its way out, and this is not because of the people who forcibly broke DRM, but because the iTunes store proved that there was a market of people who were prepared to pay money and play by the rules. Adhering to the spirit of copyright when safeguards were in place gave the industry confidence in a way that arguing over the letter of the law never did.

Book Review: SQL and Relational Theory

Tuesday, December 1st, 2009
Front cover of the book "SQL and Relational Theory"

The first thing to know about SQL and Relational Theory is that it’s largely a retread of Chris Date’s previous excellent book Database in Depth. The latter is a favourite of mine: extremely readable, yet with enough theoretical clout to change the way I looked at databases forever. The new volume carries over large chunks of the text from the older one, with some minor tweaks. As the name suggests, it brings in substantial additional material to link relational theory in with SQL, the only practical implementation of the model in current use.

The front cover of "Database in Depth"

In the preface, Date explains that the motivation for the new book was the realisation that practitioners weren’t able to figure out for themselves how to apply his theoretical ideas within SQL. Clearing up this difficulty is an admirable goal, and illustrates well that Date’s approach is practical and not meant as ivory-tower theory, but I can’t help but wonder if one of the reasons he didn’t state was that books sell better with ‘SQL’ in the title.

The additional material has resulted in a book that is roughly twice as long. This isn’t a problem in itself, though it does spoil one of the things I loved about “In Depth”: that it could be read in a couple of evening’s work by a sufficiently motivated person. The importance of making a book light enough that you can sit and read it on the sofa without looking like a database nerd should not be understated.

The prose remains clear and readable, and strikes a nice balance that makes it approachable to relative beginners while avoiding ever sounding patronising. Date’s style is precise to a fault, and some people will find it needlessly pedantic; nevertheless, there isn’t any pointless pedantry here, and if you stick with it you’ll learn why subtle distinctions need to be made.

So how useful are the new insertions on SQL? I find it difficult to tell. On the one hand, it makes it much easier to relate the ideas in this book to discussions of theory that actually occur in the real world, since SQL is the lingua franca. In the old book, it was certainly annoying to have all the examples written in Tutorial D, without a real specification of how the language works. On the other hand, Date’s examples in this book are still in a mythical beast called “Standard SQL”, of which no practical implementation exists. What is good practice in standard SQL might be impossible in your chosen implementation, or there might be a better way to achieve the same thing.

It’s certainly worth buying one of the two books here, but the choice of which is not as obvious. If you already own “In Depth”, the updated version probably isn’t worth buying. If you don’t, then “SQL and Relational Theory” is the thing to buy, unless you’re after a lighter and more portable read.