Tag Archives: books

My delicious.com bookmarks for October 12th through October 16th

  • Palm Pre smartphone – "So you're after a smartphone, you've got money to burn and an obvious decision to make: this or the iPhone. No other touchscreen smartphone is even in the running. The Pre has some obvious advantages. It's a bit smaller than the iPhone and 'Synergy' works well, which could prove useful if you're more familiar with Facebook than the concept of Gmail or an Exchange server. But weigh it against the iPhone and it's hard to recommend."
  • The Hitchhiker’s Guide Turns 30 – Still one of my favourite books.
  • Cat registered as hypnotherapist – To be fair, cats do seem to convince people to pet them and feed them without any apparent pay-back. Maybe they do hypnotise them?

My delicious.com bookmarks for May 18th through May 26th

Eight Best Computer Books

It’s been over five years since I last told you about my favourite computer and programming related books (don’t believe the date on that article. It’s been edited lightly a couple of times since I first posted it).

Having said that, some things have not changed. The vast majority of books on the shelves of your local retailer are very specific. Publishers seem to eschew broad, generally useful texts in preference for yet another beginners guide to Microsoft Word or C++ (or, more likely, Visual C++ 2005 Special Easter Edition SP2). I do not understand this. Sure, there’s a genuine need for “how to” books for specific technologies but is it not more useful to learn how to solve problems in general rather than how to solve a particular problem with a particular product?

Worse, most are not even particularly well written. Deadlines are so strict that authors have to write quickly rather than accurately or well. Ultimately the drive to be the first publisher with the definitive guide on Word 2007 (August Edition) trumps all. One that galls me is that most programming language books assume that you are learning to program from scratch. Is C++ really likely to be your first language? I think not.

The other continuing trend is the size of them. Is it necessary for every book to be a thousand pages long and be stuffed with screen-shots? None of my favourites are like this.

As with the last list, I have not just focused on your typical “computer science” text, if anything I have shied away from them. Hopefully if you go pick up a copy of all these books you’ll find them all to be both useful and entertaining to read.

Additionally, I find most of them to be books that are worth returning to, if not as a reference guide then as something that increased experience make each read make more sense.

So, let’s get to the point. What are my favourite computer books, and why?

  1. Code Complete. If you’re writing or designing software you need this book. As I said last time, it ‘is one of those books that does the job so well it has no obvious competition. It describes the complete coding process right from low level design through to unit testing and, while most people would have been very prescriptive, McConnell outlines the pros and cons of each approach.’ Now on its second edition, it is still, as far as I know, without peer.
  2. The Mythical Man Month. People never seem to learn. Managers still seem to add more staff to already late projects. Brookes said all this, and a lot more, in this book way back in the seventies.
  3. Accidental Empires. Robert X Cringely’s history of the early PC industry is a fascinating and entertainingly written anecdote-fest. He claims neither to be complete nor objective, yet seems to cover all the bases. Since most people these days deal predominantly with x86 architecture machines I think everyone should know the heritage and how we got from Bletchley Park to an iMac. (But without the iMac as it was written years before Apple returned to form.)
  4. Professional Software Development. When I first bought this I was a little annoyed. It’s actually the second edition of McConnell’s ‘After the Goldrush,’ just coming with a different name! I’m not sure that I would have bought it had I known, but I would have missed out. This is the only book of the eight here that talks about the industry as a whole, and how we should move away from the typical, and surprisingly common, “code and fix” development. He talks about certifications; architects; heavyweight methodologies; personality types; and a whole lot more. I can’t say that I agree with every last sentence, but it’s well worth reading just to get a perspective.
  5. Peopleware. It’s amazing to think that it took until the 1980’s before the human elements of writing software were seriously considered. Even now most Computer Science seems to concentrate on the more technical aspects. This book was probably the first to discuss the “human factors” of software development and is still the best that I’ve read.
  6. Programming Perl ((This link is to the third edition. I currently only have the second.)). I include this book at least partially because I wanted to show that it was possible to have a densely technical book that was also well thought out and entertaining. The structure is superb and I can’t think of any other programming tomes that have made me laugh out loud.
  7. In the beginning was the command line… ((You can also download it from Neal Stephenson’s website.)) I think that this is an interesting book for two reasons. Firstly it describes the reason why Unix is as it is better than any other. Secondly, it explains the various major operating systems (and some minor or — now — non-existent ones) in approachable analogies rather than dense jargon.
  8. Conceptual Blockbusting. There are few other professions where your output is almost entirely brainpower. A computer program is really little more than a slightly less ephemeral rendition of pure thought. So if you can’t think your way out of a particular problem you’re in trouble! This book makes you more aware of your own intellectual processes and outlines different ways of approaching problems. Invaluable.

As you may have noticed, many of these books are the same as last time! Does this indicate that I’ve been reading less? A little perhaps, but I’d like to think that it’s because by picking books not related to specific versions of particular technologies I’m increasing my odds of finding the classics.

What do you think? Any other good choices that I missed?

My del.icio.us bookmarks for May 14th through May 17th

The Perfect Thing

My first reaction was to hate it.

Actually, no. My first reaction was what a cute, almost-square book. My second was to hate it. It’s only a few pages into it and Levy is already discussing his great taste in music and disparaging mine (“… a pathetic Pet Shop Boys tune, the sort of thing that Nick Hornby would listen to on a bad day.”)

It wasn’t exactly what I was expecting. But — step back — what was I expecting? Well, the blurb on the back tells you that you can learn how the iPod became the defining object of the 21st century. Having read most of Steven Levy‘s previous books, the obvious point of comparison was “Insanely Great,” the story of the Macintosh. But while the Mac took several years to put together, the iPod took only around six months. In hindsight maybe it’s pretty obvious that it’s not all the trials and tribulations of putting the machine together.

So what is it? In some ways this is the technology version of Alain de Botton’s “The Art of Travel.” It doesn’t so much talk about the making of the iPod as discuss the experience of owning and using one.

For example, one chapter is on the idea of “shuffle” and how people use it and attach super-human abilities to its ability to select the most appropriate mixes while theoretically being entirely random. Even when he talks about the design it’s more along the lines of how it makes people feel. One interesting observation was that when people speak about the iPod, they invariably reach into their bag or pocket to retrieve their machine and start touching it, pressing the controls, polishing the screen. How many other gadgets evoke this kind of sentimental reaction?

Certainly much mirrors my own experience. I remember sitting on the tube on the way home from Tottenham Court Road after buying a first generation iPod, the tiny cube ((I suppose 2001 was when the G4 cube still held the promise of being successful.)) that it was packaged in sat on my knee, and thinking, “I can’t believe I just spent ?350 on a Walkman.” ((In fact I was lucky to get away with that. A number of shops, having just one machine left, wanted to charge me more that list price. I knew I wanted one but not that much.)) Yet when I got home and started using it, any doubt vanished and quickly it became my most prized gadget.

In fact, as I type this my fifth generation iPod is on the blink. The emotional impact of this neat pile of components being on the verge of failing is quite unlike almost any other gadget I own.

Anyway, I was writing about the book “The Perfect Thing” and not my own experience, so let’s get back to the point. If you’ve ever read any other Levy books (or his column in Newsweek) you’ll know that he has an easy, engaging style and this book is no different. He covers all the bases, touching on everything from the design to downloading music from the Internet (and the fun that Apple had making iTunes) to Podcasts.

Given that it’s more about the experience of owning an iPod the fact that it’s already dated — there’s no mention of the iPhone, the Touch or the current range of Nano’s — is less of an issue than I initially expected.

Overall it’s much more of a “fluff” piece than most of his other books, but that does not make it any less entertaining or complete. Worth a read, just not as highly recommended as “Crypto” or “Insanely Great.”

Jordan and Egypt

"No Camels & Horses" sign, Dahab, Egypt

I always have immense difficulty choosing my next travel destination. The bottom line is that I’d happily visit almost anywhere I’ve not been before. And even then, many of the places I have been to I’d happily go back to. With around two hundred countries in the world this presents a problem. Then you need to combine this with the fact that I love reading about travel — books, brochures, back issues of Wanderlust — and you can easily believe that it can take me months to decide where to travel to next.

I know. I lead such a hard life.

Anyway, after a relatively short holiday last year, this year was going to be India. Except. Long story short: I did not have enough leave from work to be able to do everything I wanted.

Eventually, through a process of compromise and whittling down that I couldn’t explain even if I tried, I ended up deciding on the middle east in general and Jordan and Egypt in particular. I’ve had a mixed experience with the Middle East in the past. I loved Turkey but wasn’t keen on UAE. Fortunately both Jordan and Egypt promised more of the history and culture of the former and less of the shiny, characterless modernity of the Dubai I had seen.

As I have done for the last couple of trips, I felt it made most sense to break the holiday down into bite sized chunks. I am going to cover the sights in Jordan in the following posts:

And Egypt in these: