Keeping Your Kitchen in Order

I know you don’t want to admit it, but we all know that you love Kitchen Nightmares as much as I do. I actually enjoy cooking shows of all sorts and like applying their lessons to my somewhat limited selection of Kansas delicacies, which are generally limited to cuts of select beef in different shapes. Seriously, ask about my steak sushi sometime. Nevermind. My point is that while watching Kitchen Nightmares today, I had a thought about the web development trade and just how much it parallels the cooking world. I want to share these thoughts.

The People

Allow me to borrow some definitions from Wikipedia, the clear authority on all things culinary.

Head Chef

This person is in charge of all things related to the kitchen, which usually includes menu creation, management of kitchen staff, ordering and purchasing of inventory, and plating design. Chef de cuisine is the traditional French term from which the English word chef is derived. Head chef is often used to designate someone with the same duties as an executive chef, but there is usually someone in charge of them, possibly making the larger executive decisions such as direction of menu, final authority in staff management decisions, etc. This is often the case for chefs with several restaurants.

In many restaurants, like many web shops, this is where the story can begin and end – for better or worse. Sometimes you’re just stuck flipping the burgers on the grill by yourself. Good head and executive chefs are not only great cooks, they generally have a keen understanding of the business world as well, because at the end of the day, if the financials aren’t right then the restaurant won’t make money and then people get fired. Likewise, a good web lead will understand the business they work in, and how it ties in to things like marketing, customer service, etc. If a person is just a really good cook, that doesn’t make them a chef, and if a person is good at writing HTML, it doesn’t make them necessarily right to lead a web office. In the end, we can also distinguish between head and executive chefs in the web world. It’s similar to comparing a CWO to a Director of Web Services. Most organizations lack that level of granularity though, and like with restaurants, the duties and responsibilities will be ran from a single touch point that could be described as either or both simultaneously.

Sous Chef

The Sous-Chef de Cuisine (under-chef of the kitchen) is the second in command and direct assistant of the Chef. This person may be responsible for scheduling and substituting when the Chef is off-duty and will also fill in for or assist the Chef de Partie (line cook) when needed. This person is responsible for inventory, cleanliness of the kitchen, organization and constant training of all employees. The “Sous-Chef” is responsible for taking commands from the Chef and following through with them. The “Sous-Chef” is responsible for line checks and rotation of all product. Smaller operations may not have a sous-chef, while larger operations may have several.

When thinking sous chef, think art or creative directors. You can also put product and project managers in this category too. These people should be fully capable of doing any of the tasks that they oversee in a pinch, but more likely they’re somewhat more managerial in nature in the office. They communicate and coordinate. They’re the ones who will go to the project meetings so the web version of the chef de parties don’t have to.

Chef de partie

A chef de partie, also known as a “station chef” or “line cook”, is in charge of a particular area of production. In large kitchens, each station chef might have several cooks and/or assistants. In most kitchens, however, the station chef is the only worker in that department. Line cooks are often divided into a hierarchy of their own, starting with “first cook”, then “second cook”, and so on as needed.

Our chef de parties are the role-specific people. Our front end developers, our interaction designers, our graphic designers. Each has their station “on the line,” and best serves their team when they are working properly in concert with the others. Over time, they’ll usually pick up the skills from other stations to augment theirs, allowing them to move in and out of spots as necessary to help out. This gives them flexibility, a broader skillset, and an understanding of team building. It’s okay if they can’t do every station well, as long as they understand how each station gets them from prep to table.


A commis is a basic chef in larger kitchens who works under a chef de partie to learn the station’s responsibilities and operation. This may be a chef who has recently completed formal culinary training or is still undergoing training.

Interns. Nuff said.

What I think is the most important part of the striation of responsibilities in the kitchen is the principle behind earning your stripes. In a serious kitchen, you don’t just come in and become sous chef without the requisite experience. No, you start as the commis, and you work your way up. By the time you’re a sous chef, or ready to become the head chef in your kitchen or somewhere else, you know and understand the roles under you because you’ve been there. It helps you respect and understand those that work for you. Folks who have worked with me in the 24 Hour Plays have heard me give a very similar speech as it relates to theatre – that I find it very important that if you want to direct, you should spend some time as an actor, and a technician, etc. Be the ball.


Ask any ten chefs what skills are most important to being great at the craft, and you’re likely to get a broad spread of answers. But like with any trade, there are a few very atomic skills that are fairly consistently important. For instance…


A chef with a bad palate is like a web developer that uses Frontpage. Having a well trained palate is imperative to the process of selecting and procuring quality ingredients for meals. We aren’t buying beautiful rockfish or delicious cuts of beef, but we are selecting CSS frameworks and jQuery plugins. We have to have a good sense of color and design. We need to know if WordPress is the best platform for a new site, or Drupal. Our ability to “taste” the environment we’re developing and pick the right components to combine into it can make or break a project. You know you’ve developed a good palette when you can look at a website and tell what CMS it uses. Likewise if you can make the CMS you use disappear entirely to the user. They know it’s there, but you know how to keep it all perfectly balanced. This also gives you the instinct to tell when something is going wrong. When ingredients have “soured,” or you’re using too much of something, or not enough of something else.

Mise en place/Hygiene

Mise en place is a French phrase which means “everything in place.” It’s used to refer to having all your ingredients and tools ready and where they belong. I’m grouping this with hygiene because good mise en place skills inherently reinforce kitchen cleanliness and maintenance as well (I’m not just talking about washing your hands after peeing). Web mise en place would be everything from making sure your workplace ergonomics are well planned, to making sure that you lay out your software and tools in a way that makes sense and encourages good development. Just because our “countertop” is digital, doesn’t mean you shouldn’t think about how you have windows open and arranged, for instance. Web hygiene means coding clean – maintaining comments, keeping HTML semantic, and not leaving old code out to rot on the countertop, so-to-speak. A sloppily coded and presented website can be a turn off to visitors. Good web hygiene is a trait of good attention to core user experience on your site.

Knife Skills

This is a pretty direct metaphor. The chef’s knife is an extension of their hand, arm, and body – as is our Wacom stylus, magic touchpad, or mouse. It’s all about core skill competency and practice. A good chef can dice an onion blindfolded in a tenth of the time you or I would take. You should be able to spin up a Git repo, fork, and commit just as effortlessly. Mysqldump and LESS are your bitch. You can recite CSS selectors and attributes like a multiplication table. The knife needs to be sharp, and the knife is an extension of you. Those skills make your job easier, and they show to the visitor. The competency and effort that shows through is something that users will see and appreciate. Being adept at your skills won’t always change the “taste” of your end product, but the craftsmanship is something that will show through and visitors will respect and peers will admire.


When all a chef’s skills meet in the center, it makes for a magical sixth sense. Put a good chef in a room with some ingredients and give them a couple hours, and more than likely they will magically appear at the end with a beautiful dish. That’s the entire practical value in so many of the cooking competition shows – can the cook work under pressure with unknown variables? Knowing how flavors mix, understanding cooking principles, and solid plating techniques are all integral to producing fantastic dishes in a pinch, even if they don’t know what they are necessarily walking into. Because noweb developer has ever had to build something on the fly at the last minute, right? This is also how we grow as designers and developers. Anyone can follow a recipe – they’re just a Google away. But it’s what you can do with that recipe to make the end product your own that will really set you apart. If all web development was about was following a recipe, we would have been out of a job long ago, because solutions would all be simple cut and paste jobs a monkey can do. There are times when you can even get away with that, and certainly we all have. But those are times where you’ll never stand apart, and never produce anything unique.

Oh, and then there’s…

…that important fact about the sheer way work gets done. If you get nothing else from my rambling above, take this away with you. You know one of the common, recurring themes on Kitchen Nightmares regarding why restaurants are failing? Menus and procedures that are forced upon the chef without regard or respect for the chef’s role and abilities. People playing in kitchens that don’t respect ingredients. The head chef is rarely the top person in the restaurant – someone else probably owns it – but successful restaurants know how to put the chef in charge of the menu and allows them to run the kitchen their way to coordinate the production and distribution of food, taking orders from the wait staff and cycling out the finished product.  A president, dean, or director of marketing should be able to trust in their head web person implicitly – and it’s that inability to trust that I see repeated over and over as a core complaint from our peers at other institutions.

It’s that faith and commitment to excellence that makes the difference between a truly successful kitchen and restaurant, a perfectly mediocre one, and one that ends up with its doors closed.

Photo Credit: cc icon attribution small Keeping Your Kitchen in Ordercc icon sharealike small Keeping Your Kitchen in Order Some rights reserved by Edsel L

How Safe Is Your Job?

There was a point, about three years ago, where I was seriously wondering what job security in a jack-of-all-trades style web job was really like.  Was there value in it?  Was there a future in it?  These kinds of questions are inevitable when you consider where you are, where you can go, and what you can do between here and there.  The web is a big place, and those darn kids that won’t get off our lawn are sharper about web stuff than they used to be.  Are we destined to become a dime a dozen, especially at universities where we are effectively training people to replace us every day?

chickencubicleI think it’s always important to weigh your career once in a while, and determine what the longevity of it is, both as a job, and as a means to keep yourself satisfied.  That was where a lot of these questions originally came from for me.  I was trying to determine how to further develop myself professionally, and in what ways to do it.  The first thing I think I was able to really work out was that yes, we should keep ourselves sharp (a given), and that yes, the web is a great industry to be in.

I, for one, don’t view the younger generations as a threat just because they are young and have been exposed to the internet from birth.  Had the web stood still, and never evolved beyond basic HTML, I think it would be a totally different story.  Luckily, the web is crazy dynamic, and evolving in ways that can blow even the most hardened veteran’s mind if they think about it too hard.

Compare it to a Model T.  If automobiles were all still as simple as Model Ts, we’d all be mechanics by now, and we’d never need shops.  That’s how the web in a bubble would be.  But as cars have evolved and become more complex, so too does the web.  We will forever need mechanics the same as we will always need “web developers” (whatever that really means).  And at universities, we’re always short on skilled people and resources.  It might be easy to find a talented youngster to fill a spot, but it’s much harder to keep them when someone else can wave almost twice the money under their nose.

The other side of this point, being a jack-of-all-trades, is equally valuable.  As I mentioned, many of us work in shops where our staffing is painfully low.  It pays then to be good at everything and great at nothing.  I’m not saying that you shouldn’t strive to be experts in things, it’s just hard to do, and as a human, I require sleep once in a while.  If you network well and know your resources, even the hardest questions can be quickly answered (thank you Google).  Then as you grow in your position, you become better primed for project management and leadership positions.  The captain of a ship might not be able to fix the engine of his boat, but a good captain would at least be able to talk to the mechanics on their level and know what he can and can’t ask for.  An expert programmer might be able to hammer out Ruby or Java code like nobody’s business, but by specializing in that, they sacrifice other skills.

Ultimately, if you’re happy in what you are doing, and your boss is happy with you, then it’s all good.  But I think we all need a little to look forward to from time to time.  Where do you think the most valuable skills lie in university web positions?  Project management? Development?  Design?  Information Architecture?  Where are you putting your chips at?  And by investing in those skills, do you think doors can continue to open for you on your current ladder, or have you already hit the ceiling?