Alex Hardy


Hello there!

What Gordon Ramsay can teach developers

While watching Kitchen Nightmares I’ve been thinking about writing a post. I think a lot of the advice Ramsay dispenses applies not only to businesses generally, but particularly well to web design and application development.

37signals have beaten me to it. They list some mistakes chefs and restaurateurs make, and draw parallels with our own field. I’ve abbreviated their list, so go read it there and come back for my two cents worth!

Everything to no one

Over-stuffed menu syndrome. Too many dishes, done poorly. You might compare this to the kitchen-sink approach that many developers adopt. A simple concept executed with flair is often the best.

Cook what you know

Or eat your own dog food. If you don’t use your product and others of its kind, how would you know what characterises an excellent product? When I started using simpleContact I soon realised that messages ought not to come from the admin address, because I was sending replies to myself. Version 1.1 corrected that.

Passion for your environment

If you don’t take pride in your work, or are unwilling to invest in a continual learning process, then you need to leave the industry to us professionals.

Here are a couple more that occurred to me and Kevin as we discussed it:

Seek user feedback

Sadly, this is done too rarely. Criticism is more useful than praise! It’s nice to think that a silent majority is happily using your product, but your dealings with users who have a problem or unsatisfied requirement are most valuable.

Is your product the equivalent of a sushi restaurant in a small Yorkshire village? A wise individual said: Just because there’s a gap in the market doesn’t mean there’s a market in the gap. Perhaps yours doesn’t exist?

Mistakes made in the kitchen, should stay in the kitchen

Test your work rigourously. This goes double for fixed media like CD-ROMs. You can’t un-burn a thousand discs because you fucked up (I had to use the F-word once, considering the subject!). Experience has taught me to stick to my guns here. My work is done when I say it is, irrespective of some arbitrary deadline.

Still, errors may slip through and this is when your recovery is all that matters. A swift and honest response may come in the form of an update, but often feels like more than 9/10 companies can manage in this life.

… but there’s nothing he can teach us about swearing :)

These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • Facebook
  • StumbleUpon
  • del.icio.us
  • Reddit
  • Ma.gnolia
  • Technorati

2 comments for “What Gordon Ramsay can teach developers”

  1. Neil Woodman

    What about taking in a new recruit, completely breaking them down to quivering, blubbering wrecks by means of continually shouting and calling them ‘donkeys’. Continue this until all their bad habits and attitude are totally changed, then, and this is key, build them back up again with random praise when they least expect it. The first of which will undoubtedly reduce them to tears again, but these are tears of happiness, not fear. You then end up with what Ramsay refers to as a ‘crack team’; witness Hells Kitchen for evidence of this technique in action.

    And I tell you what I bet El Jobso uses exactly the same method.

  2. Alex

    It’s all a bit Full Metal Jacket, isn’t it?

    *Holy shit Private Pile! What is your major malfunction? This scallop is undercooked, you worthless sonofabitch! Now give me fifty laps of the yard!*

    I’ve no doubt at all that Jobs is a total nightmare to work for.

Comments are welcome. Keep it friendly and on-topic please.

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>