Code Like a Chef: Work Clean

The post uses Thomas Keller’s idea of “working clean” as a model for programming. It says a programmer should keep both the physical desk and the virtual workspace organized, reset between tasks, and prepare only what is needed for the next task.

Reading notes

#

• Keller’s notion of mise en place is presented as being organized and having everything needed to do the task at hand.
• Good organization is described as removing anything that interferes with the process and creates distractions or errors.
• The author says working clean is the most valuable idea taken from the kitchen because he is not naturally organized.
• At the office, working clean means keeping the physical workspace clear of dirty dishes, papers, and knick knacks.
• It also means cleaning the virtual workspace by closing files, docs, spreadsheets, and browser tabs that are not needed.
• A cluttered desktop is described as a sign of a disorganized and unintentional mind.
• When working well, the editor, terminal, browser, and other tools are arranged for the current task, and email does not stay open.
• After finishing a task, the author resets by closing windows, stepping away from the computer, and checking whether he needs a break or to handle interruptions.
• Before the next task, he prepares the needed server, code, tests, and docs.
• The post cites Bob Martin’s view that professionals stay clean rather than create messes, because dirty work is slow.
• It ends by linking a clean workspace with clean code and asking how clean code could come from a dirty desktop.