What Software Developers Can Learn From Fish and Chips

fish_n_chips I love a good plate of fish and chips. I also love a good chance to compare the software development field to a completely separate industry. It’s a great way to find solutions to problems that have been solved decades ago in other fields (genealogy for example) and it helps to keep me grounded in the good ‘ol practical reality.

I came across a great example of this today while watching Diners, Drive-Ins and Dives with Guy Fieri. It involves the owner of a fish and chips shop (Grant) talking to Guy about how they make their Toad in the Hole. There is a clip of the sequence here. Fast forward to about 5:10. For those unable to watch, the clip goes like this:

Guy: And the gravy? Mirepoix, drippings from the sausage?
Grant: Yeah, no none of that.
Guy: None of that?
Grant: We're not looking to make that kind of gravy. What we're
looking for is a fish 'n chips shop gravy, and the best way we've 
been able to replicate that, with no shame, is a powdered gravy.
Guy: Seriously?
Grant: Seriously.

This dialogue jumped out at me. Guy was expecting this renowned shop to be using an industry-standard technique, but the chef had decided to do otherwise. He was using something which would certainly be considered inferior (powdered gravy) and even shameful by some, but he was doing it because he thought it gave him the best result. He ignored the fact that it was not industry-standard, that it was not the pretty solution, that it was even considered shameful. He ignored all of that because he knew it would result in a better experience for his users.

I imagined him posting his recipe to his equivalent of Hacker News and being ridiculed by all of the other chefs for using a powdered gravy.

Sometimes, we software developers get caught up trying to make perfect software and forget that what matters most is what we deliver to our users. Looking to other industries helps remind us of that.

You can follow me here on Twitter