Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 7
    The only thing close I could find was a "Joel on Software" post on the top 12 things every company should provide for their programmers. One of the 12 was a quiet place to work. I doubt Joel Spolsky meant this, though. Commented Mar 15, 2011 at 19:12
  • 5
    A quiet workplace would be one where if you are not having a conversation, things are generally quiet, and where you can have a conversation without disturbing others. That means no culture of paging people over the intercom, and use of white noise generators or other methods of minimizing the apparent level of sound in areas where many people work. A no talking rule does not make a quiet workplace. Commented Mar 15, 2011 at 19:58
  • 6
    @Kevin Cathcart, we are in violent agreement on that one. Now, I've been in a company where the opposite was true. We had ~40 people in a bullpen with open tables and no cubes. The only team that could get anything done was the one that made the majority of the noise. That's the type of environment you want to protect against. Commented Mar 16, 2011 at 11:59
  • 8
    @Kevin - My development department is an open cubicle farm, right next to an array of three bells labelled "Sale", "Big Sale", and "Huge Sale". A few times a day, sales people ring those and yell "wooooo!". :-\
    – Dan Ray
    Commented Mar 16, 2011 at 12:30
  • 3
    @Dan I had a string of interviews a few years back where three startups told me they had to move the sales guys away from the devs because they were too !@#$ing loud. Commented Dec 20, 2012 at 6:13