Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think there are at least two different kinds of productivity. One is the kind where you need to progress through a non-trivial body of work with a well-understood end-state. Your primary, if not sole, output is code. This is probably well suited for private offices and remote teams.

The other is where you're solving a problem that isn't in the first order a code problem. There are typically humans involved in these kinds of problems. Most instances where the problem is defined as "building the right thing for the customer" where part of the problem is coming up with "the right thing". This works well in open plan offices where multiple people can quickly give input/get feedback. Remote working is probably not a great idea. Most work in early startups is probably in this category, and that also offers a model to explain why open plan offices are so common in not-startups-anymore: these companies are very eager to retain the energy of their early days, and a lot of that energy is tied to the collaboration of the open plan office, even if not necessarily suited to the workloads of the more mature company.

Tl;dr: when people speak of being more or less productive under certain conditions, a lot probably hinges on what kind of work they are doing.



Unfortunately I think personal productivity overall in industry is less of a factor than people suggest. Everyone wants have high pay, use exciting technologies, work in comfort etc. but they don't see the bigger picture.

Investing in people at the end of they day has to make sense, otherwise other companies will out compete you. When it's hard to determine people skills, work varies highly in intensity, projects fail for any number of reasons, people don't stay very long at even the most "comfortable" companies etc. the personal productivity of any employee becomes marginal, at least in the lower ranks. This is true for most "craft" industries like newspapers, fashion or design.


There are also people other than coders in tech companies. I'm next door to a sales group for a tech company. They do a lot of yelling.


Yes, I agree that co-locating teams that aren't directly collaborating can be counterproductive. Loud sales teams, obviously, yes, but quieter teams will also have different patterns of buzz that will be disturbing to unrelated teams near them.


It's interesting. They get REALLY PISSED at the developers about stuff.


When I've worked in none-developer companies I've always found the office staff are fine as long as you don't rub it in their faces that you earn more and have more freedom.

Well except one place where the people in the office where just horrible (really toxic culture largly down to the 'office manager' been about one step short of invading Poland) so I just did as I pleased (wandering in at 10am wearing flip flops and combat shorts), I was pulling 60hr weeks so the boss didn't care and she hated me anyway because she had to do payroll and knew what I was earning, I was knackered from day one on that job.


What's interesting here is the sales group is from a different company. Their devs are at a different office. So I hear the stuff like a fly on the wall.

What I don't hear is the root cause of the angst. Is the sales team overpromising? I don't know. But when something's not ready for their demo it gets quite loud.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: