PhotoBox in many ways have the advantage. Not only were they working with the full resolution images, but they are also a completely UK-based organisation. Their offices are only on the other side of London which has to help delivery times!

Nevertheless, at the risk of giving away some of the results from the other two vendors, they were the last to send a “dispatch notice” email, on the 30th June.

Regular readers will know about my experience ordering a photo book from Apple using iPhoto 5 and cards using iPhoto 6. For my wedding I decided to get another book using the same pictures and, as far as possible, the same layout but order from three different suppliers: Apple, PhotoBox and MyPublisher. This is, therefore, going to be a four part article. This one is about the initial ordering process, then the next three will be posted when the books actually arrive.

I watch a lot of movies but I don’t usually review them. This makes “Irreversible” unusual. This word, in fact, describes much about the movie and my reaction to it.

The movie starts at the end, with a death that the blurb proudly describes as “one of the most violent murders ever portrayed on celluloid” and then works backwards detailing the motivations for it and the complex relationships between the various characters.

As you may have seen, I was generally quite impressed with the photo books that the previous version of iPhoto was able to generate. I was therefore quite keen to try the new cards that you can buy using iPhoto 6, the version included with the recently released iLife ’06. (Am I the only person that thinks that “iLife” is a really naff name? First that, then “MacBook Pro” rather than “Powerbook.” What next?!)

As many of you will already know, I recently came back from a trip to Vietnam. Some will even have seen the pictures. Others, however, do not like looking at pictures on a computer screen and always insist that I get prints. This time I decided to go one better and get a book.

Those still wallowing in the PC world may not be aware of a Macintosh application called iPhoto. It’s a bit like Adobe Photoshop Album if you’re familiar with that. It allows you to catalogue photos, categorise and label them and perform some minor edits such as red-eye removal, cropping and simple colour adjustment, although I normally use Photoshop for this kind of thing. I mention it here as one extra feature that I’ve never used before was its ability to make custom books. I normally use Photobox for my prints but this seemed like a much easier option.

Let’s cut to the chase: if you’ve read and enjoyed any of Joel Spolsky’s ramblings on the web you’ll like this book. Skip the rest of this review and just go buy it.

For the benefit of those that have not heard of him, who is this Joel chap and what is the book and his normal prose about? The “About the Author” section describes him as an industry veteran that writes an “anti-Dilbert manifesto” on his website. I can’t think of a better description, which is why I have shamelessly copied it rather than finding my own phrase…

The concept

I liked the blurb on the back:

“This title addresses all of the skills required to effectively design and develop complex applications, including planning, building and developing the application and coding defensively to prevent bugs.”

It suggests that it can bring you from the stage where you focus entirely on the code to the point where you can take in a whole project, make it all work and delight your customers. Mike Gunderloy has 25 years of commercial experience and so has a lot to say.

Introduction

At the moment I’m reading Steve McConnell’s excellent ‘Professional Software Engineering,’ in which he talks extensively about creating a genuine software engineering profession. I believe that this is a great aim and, although I disagree with him on some points, I think the basic premise is both a good idea and inevitable.

However, that is not the point that I want to talk about, although it is related. It’s the fact that, even though I work in a relatively professional organisation, almost no-one here reads computer science books. Sure, there are piles of guides to complex Oracle stuff, C++ this and XML that, but there are no books around on how the whole process should work.

Introduction

A tip: if you’re going to read this book, don’t flip through to the back and read the ‘Authors note.’ It doesn’t actually give away the story, but there are clues that you won’t want to know. I should know, that’s what I did.

Fortunately, although you can predict the tone of the end of the book, there are more than a few surprises in store.

But I’m getting ahead of myself.

Introduction

I work in the IT services industry. What this means is that I work for various clients using my technical skills to solve their problems.

One thing that no-one mentions while you’re at university, planning to go into this industry, is that most of the problems you come across are not technical in nature. Problems with computers are usually fairly tractable and can be solved, even if not elegantly, by anyone who is interested enough to have a go. It’s the other, people problems that are tricky.