Hacker News Reader

Comment by xwolfi | Hacker News Reader

I work on a trading floor in a large investment bank in Hong Kong and I dont get what you dislike abt open floor. It's so nice to just know what's happening around you, have people rushing to you or you rushing to people, being able to yell or be yelled at.

Sure there are focus phases I d love to have less distractions in, but tbh sometimes your value lies in quick response to big problems rather than long concentration to solve small ones.

I worked in full height cubicles and sometimes you can spend 2 weeks without sharing something with a coworker to a point you end up having spent all you time on a silly assumption you discover made you overengineer something a dude sitting 10 meters away knew you could solve in 5 lines.

Maybe we both program different kind of software and maybe need different environments ?

View on HN

Trading floor is an entirely different environment from the majority of other open office concepts and related jobs out there.

It’s more akin to an SOC or other Ops centers, where the open floor and resulting info flow is crucial to the perma on-call nature of those work patterns.

> quick response to big problems

Most developers (the kind that actually just sits and codes all day long) are not putting out fires all the time. But, many, many ops (operations) people are. This comment makes a lot of sense if you consider that the author might be in ops.

As a former devops/infrastructure engineer (i.e., my coding was mostly around lighter projects or automation/scripting), I was in some open environments and sometimes they really were a ton of fun. One day I came in and there were server boxes all over my desk... it was funny. We were constantly pranking each other (nothing permanent or painful, of course!) That camaraderie and closeness produced one of the best work environments of my career and I miss it.

However, my job now is serious, head-down coding... I would find that very difficult in the same open office environment, so I think both perspectives can be true depending on the type of job you have.

Somewhat ironically, most of my career has been in Ops myself. I still don't think open floor plan offices are a good thing. While working in Ops I was generally at an organization that was either large enough or geographically dispersed enough that calling me on the phone or messaging me through internal systems would have been faster and more reliable than walking to my desk or yelling, so I still don't really see any plus for open floor plans. Also, I had to stop bringing my vintage IBM keyboards to work when we switched to an open floor plan at my prior office job because /I/ was too noisy for others with my typing.

This sounds like hell. People rushing around and yelling?

Yes, that's what trading floors are like.

> Maybe we both program different kind of software and maybe need different environments ?

That may be true. My dislike for open floor plan offices is actually less about noise and more about visual distractions. I stare off into the distance when thinking and having visual distractions within my field of view can easily interrupt those thoughts. Thanks to my upbringing, I'm pretty good at tuning noises out and I usually am wearing headphones anyway. But the visual distractions lead me to get off whatever train of thought that I'm on. I don't find cubicles to be significantly less noisy than open floor plans, but they do massively (to completely) eliminate visual distractions. One compromise I had at a previous employer that worked well was to "pod" cubicles, so you had your back to your team but could turn around and talk, but you weren't distracted by other teams during the day having nerf fights or whatever the heck they were doing elsewhere.

Also, I do think there's an element of different personalities involved. I think more extroverted people probably enjoy offices and open offices generally, where-as I am introverted and a bit socially anxious, so having privacy and no interruptions for my work is best for my personality.

it might also be a difference in the domain you're working on.

finance/banking tends to be a very different kind of programming then most developers are used to, even though the domain expertise is still CRUD at the heart.

i've been in that industry as well for 4 yrs now. I can kinda see his point, as its hard to not drift off in any other setting. You usually just get BusinessCases to implement, which are rigidly defined and just need to be implemented.

(and tested to a degree some people wouldn't believe on this forum where even TDD is often questioned)

Nothing that I do is urgent enough to warrant a yell across a room.

Yeah, but your boss being able to do it to you makes him feel important and powerful!

I wonder if your success is some combination of:

- Unusually good aptitude for handling context switches.

- Unusually good skill at concentrating on your work in noisy / busy environments.

- Not much time writing code that's near the limits of your abilities.

Reply on news.ycombinator.com