Last Sunday I took my family to Red Robin (a family style restaurant) after church. I requested a table with a high chair for my 3.5 yr old son. Upon bringing this high chair the hostess simply moved an adult chair to the side and put the high chair in its place. (See Image)
This is where the fun began…
For the next hour or so I watched countless customers, servers and managers limbo their way between these two chairs. A lot of them did it repeatedly, some even carrying trays full of drinks and/or food. Finally I provided evidence to to my family that I am 100% full on geek. I got excited about the insight that this little experience game me (to the point of taking pictures)
I was simply amazed that people would allow this “friction to continue” It was a simple problem in this case. Move the chair!
I find it interesting that it’s built into our DNA incur friction in our lives without really addressing it. In real life its called denial. I know the chair was not that big a deal but it did open my eyes to our basic nature. Our basic nature follows through to software development as well.
The example of the misplaced chair provides some interesting parallels when it comes to technical debt (which is a cause of software development friction) We all have technical debt in our applications and it’s in our nature to shimmy, shuffle, limbo, mambo, and shake around these issues whenever possible. It takes a constant vigilance to address technical debt. We must be active in our quest to remove technical debt. We must take the time to do two things:
- Recognize the debt. In our case: The chair.
- Remove the debt: In our case: Move the chair.
That’s it for this blog post. Just a simple observation brought to you by the staff and management of Red Robin