242 years ago the American Declaration of Independence was signed, and with it, a new paradigm for governance came into being. This government has experienced many highs and many lows, it continues to evolve and adapt. Yet, throughout it all, the underlying notion that people have a right to exert autonomy over their lives and can construct lives that are meaningful for them, in all of our myriad ways we interpret meaning, remains a fundamental foundation.
242 years after American independence, it is now time for programmers of the world to declare our independence and institute a new golden rule for our industry. Just as the colonists sought freedom from an oppressive ruling authority across the ocean, programmers of the world seek freedom from unnecessary interruptions that reduce our productivity, destroy our thought process and, in general, disrupt the work flow.
Yes, I am talking about the most insidious of issues plaguing our community:
The Headphone Interruption™
We all know it. We all have experienced it. You are in the zone. Your headphones are pumping the sounds into your ears that motivate and keep you focused, whether that's an NPR podcast, metal, jazz, country, or whatever gets your coding groove on. Then you feel it. The eyes of someone wanting to get your attention are burning a hole in the back of your head. The sounds of someone saying, "excuse me?," "excuse me?" starts to filter into your consciousness. Then it escalates and the tap on the shoulder is next. If none of those elicit a reaction, your headphones are lifted off your head.
You turn to face the person who so desparately sought your attention. It must be truly important.
- "Just wanted you to see those rain clouds outside. It looks like it's going to pour today!"
- "Can I pick you up something from the break room? I'm going to go get a coffee."
- "Any plans for the weekend?"
- "Is that English on your screen? It looks like it's from the Matrix!"
- "Did you know {random co-worker} is going on vacation soon? How lucky!"
These are all real world examples from the field of The Headphone Interruption™.
So, friends, on this day of barbecues, flag waving and reveling in the American experience (with apologies to my friends from other countries) let us declare and proclaim a new golden rule for programmers around the globe.
If the headphones are on and it's not an emergency, it can wait.
To all of our non-programming colleagues, we affirm that we like you, we like talking with you, we enjoy our coffee breaks and spending quality time together. The headphones are not a sign of our dislike of you at all. Rather, they are a necessary instrument to allow us to focus in the open floor plan offices of our modern era.
If we will it, it can be more than a dream. We can make this a reality.
Headphones on? It can wait.
Oldest comments (42)
I like the idea of having firmly established and signalled boundaries in the workplace regarding interruptions.
The problem with headphones is that I tend to have mine on all day because I like listening to music while I work.
My coworker has a small flagpole on his desk with a red flag that says "DO NOT DISTURB."
A friend at another company tends to wear ear plugs while he works, and he built a little red/green light to notify people.
Be it with headphones, flags, or lights, I'm with you. The expectation that we need to be immediately accessible is pretty disruptive, and it's not that difficult to leave an asynchronous message so that people can get back to you when their schedule allows.
Yes, that's definitely the issue with headphones, if you're accustomed to wearing them all day.
Just use the chat channels for that dude!
I think you should put this on old parchment with big swirly signatures and frame it. :)
Haha, that would be appropriate.
There needs to be a better signal than headphones.
My cube space is near the biggest "conference" area in my workplace. It is an open space where all the All Hands meetings and tech presentations are held. It's also where groups gather for lunch if there are no lunch-n-learns active. It's also where the most terrible device known to man is held (the foosball table).
I can guarantee anyone walking near our cubes will find us in headphones 90% of the time (10% I forget until someone plays stupid foosball again). That muddies the waters of making people wonder if it's an actual coding session or if I'm trying to drown out foosball with ABBA.
I propose a Raspberry Pi with an LED panel and a switch. I got a Pi Zero W recently so I've been tempted to do it. Red if go away and use Slack, and Green if whatever. Switch it as situations arise.
Or workplaces could just get rid of the stupid foosball table.
Love this idea!
Embrava Blynclights are good for this. Lots of color choices and you can manually control, or connect with Skype, RingCentral, etc.
I second this. Headphones on? Write me on slack, I will read it when it’s time )
Totally agree.
These kinds of things proceed in phases.
Phase 1: every developer has an office with a door.
Phase 2: every developer is in a cube.
Phase 3: every developer sits in one giant communal area. The dreaded open-office floor plan.
Phase 4: every developer telecommutes to work.
Phase 5: every developer has an office with a door.
Both Phase 2 and Phase 3 cause developers to utilize The Headphone Coping Mechanism.
First developed in Hamburg, Germany in the 1950s, the Headphone Coping Mechanism spread like wildfire as companies converted into the nuveau open-office floor plan. The open-office floor plan, coincidentally and likely completely unrelated, also first developed in Hamburg, Germany in the 1950s.
At first glance, there may appear to be absolutely no advantage to Phase 3. But with the advent of agile, it is a benefit for a co-located development team working on a single feature at a time as a team employing some agile-based methodology such as Scrum can reap a significant boon by have the team (and only that team) have a "pod" arrangement where there is an open-office floor plan communal area in conjunction with cubes or offices.
Alas, many companies have seen the square footage per employee benefits of an open-office floor plan, without understanding that the people in that communal area still need offices (or at least cubes), and they all must be comprised of members of the same team.
As ostensibly a cost saving measure, "penny wise pound foolish" facilities takes the initiative to save money by stacking developers like cordwood into a communal area. Regardless of project or role. This is classic cargo cult behavior, with lip-service to attaining the ultra-super-high-performance unicorn team, but in reality making the environment a soul sucking slave cesspool of sorrow. And headphones.
The best devices for The Headphone Coping Mechanism are undeniably Sennheiser. Sennheiser, coincidentally also a German company, had worked in secret on the ultimate headphones from 1945 to 1968, for one thing and one thing only: to create a unparalleled compensation device to stave off the incessant productivity killing and company destroying distraction known as the open-office floor plan.
Note: the open-office floor plan was registered as a weapon of mass destruction, and banned by the Geneva Convention. First employed by the creators to cause competitors to adopt it and die. The inventing company itself, in a twist of ill-fated irony, became a victim of its own creation. Since then, the open-office floor plan has swept across the globe leaving a wake of destruction in its path. There is no known cure, only through providence can a company weather the open-office floor plan storm.
Exactly! This is what IM is for.
Yup!
I think a better thing to seek our "independence" from is having to work on site. Can't stand having to go into an office to do what amounts to just using their internet connection but under the guise of team "collaboration".
The overseer mentality must die!!!
💯
This is one of the rules on my team's social contract.
If it's super urgent knock on their desk, if not, slack message them.
I have been startled several times by people either tapping me on the shoulder or waving their hand in front of my face.
This is an excellent rule.
-1 for starting it with something about US
I knew a few devs that keep their headphones on all day, so they will be in DND mode all the time.
I think we need a sign but not this one. I've tested a few Pomodoro like signs and they seems to work, if everyone in the office is trained as so, and devs do not abuse it.
If the dev stays 5h/day in the zone, then most probably coworkers will start ignoring it and disturb you never the less.
"-1" what do you think this developer community is? Your personal rating system? OTOH, I like your suggestion of the sign.
... Do you not also like (aka rate) others comments?