Clean your work area!

24 Jan 2016

When in the kitchen, how are you behaving to old dishes? Do you make space in order to have space to cook the food? After finished cooking the food, do you leave dirty dishes to the next day?

I’ve worked in a couple school kitchen. When I worked, it would be in the form:

I’ve worked a few months in a mechanical workshop. My boss told me how to work:

My grandfather (engineer and architect) told me how to behave in his workshop:

In his mind, if you go for lunch, then work is considered finished (so you need to clean up before going to lunch).

In software development it’s not unusual to try to ignore the cleaning part of the job. Why is this considered OK? Will the job be easier if you have to slog through:

and the list goes on.

Why do you avoid to follow even the boy scout rule of leaving it a little better than you found it? Perhaps it’s because you have no sense of code smell? Perhaps it’s because you’re stressed? You’re a junior developer?

The thing about code is that once you have a clean working area (clean part of the code base where you are working), is that changes and additions will become easier to implement. Fewer things to keep in mind will keep your working memory focused.



Do you want to send a comment or give me a hint about any issues with a blog post: Open up an issue on GitHub.

Do you want to fix an error or add a comment published on the blog? You can do a fork of this post and do a pull request on github.