5 ms·
Different learning styles. I once worked with a programmer who needed to externalize thoughts before he could make sense of them. He needed a sounding board an
by lj3 10y ago
Different learning styles.
I once worked with a programmer who needed to externalize thoughts before he could make sense of them. He needed a sounding board and was constantly talking to anyone who would listen and respond. That was his thought process.
I, on the other hand, need to internalize thoughts before I can make sense of them. I need silence to process and chew on a problem for at least a couple of minutes before I can talk about them to others. That is my thought process.
We worked together on exactly one feature. He would get frustrated because when he talked to me, he got nothing in return. I was too busy listening to respond and as a result he kept talking, which frustrated me to no end because he gave me no time to process what he was saying.
Neither of us got what we needed, so he finished the feature by himself and I moved on to a different one.
My co-worker loved open office plans. I hate them.
- mixmastamyk 10y agoHmm, a super talkative programmer, I've never met one.
- kevinstubbs 10y agoI've met quite a few. In an open office it's easier to ignore or gracefully leave the conversation. With individual offices you'll get pulled into tangential/"fun" discussions after a meeting when the team is on the way back to their offices. I could keep going, but you get the picture... After working with enough diverse programmers, you will see some varieties.
- zimpenfish 10y ago> In an open office it's easier to ignore or gracefully leave the conversation. Not when people are having a conversation with the people sat next to / opposite you and you're trying to finish a complicated feature. An office or cubicle would help (but probably not stop these assholes) because it sends the signal that this is a workspace, not a communal chat space.
- lj3 10y agoIt's helpful if you don't refer to the loud folk as assholes for the crime of being themselves. I've never had a coworker tell me "no" when I've asked them if they could take their conversation to a meeting room because I need to concentrate to finish X feature. If the office is especially noisy, I'll camp out in empty meeting rooms.
- zimpenfish 10y agoWe have plenty of communal areas away from desks (e.g. the kitchen area is the size of this section of office) for people to have conversations - they know this already. But open plan softens (if not erases) the distinction between "communal area" and "work area". Also we don't have enough meeting rooms to accommodate even scheduled meetings which means "camping out in empty meeting rooms" is a non-starter of a suggestion, sadly.
- tfigment 10y agoI've had 2 reporting to me. I am not naturally one myself. Its a trait that has to be monitored and kept in check to certain degree but is I think a very good trait when properly focused on work (while at work). I've had VPs ask me about how productive those programmers were with side remarks about seeing them frequently talking with front desk and hr (presumably socially). One was really productive so not really an issue for me but not good having to explain that.
- jon-wood 10y ago> I've had VPs ask me about how productive those programmers were with side remarks about seeing them frequently talking with front desk and hr (presumably socially). Developers like that are hugely valuable in a start-up, they talk to everyone, get to know what their jobs are, and are the people you go to when you need to know what the problems internal users are facing really are.
- parasubvert 10y agoI'd say the main tradeoff of open office plans and active pair programming is that it requires a lot of empathy for the differences of others' communication and learning styles. That goes both ways for those that need to listen/digest and those that like to talk. Not everyone has the same capacity and thus would prefer to be more of a solo contributor. I am kind of in between - I love pairing but after several weeks I need a break and prefer to be an individual contributor for a while.
- lj3 10y agoI'm not sure it has anything to do with empathy. You can empathize with somebody else's need to either work alone or work with other people, but that doesn't really change anything. Pair programmers still need people to talk to and no matter how quiet they are they will always hamper the efforts of those who need silence. Something that doesn't often get mentioned is it also works the other way around: if the quiet programmers exert their influence over the open office so it's quiet, that hampers the efforts of those who need to verbalize to think. The "oppression" goes both ways. I'm not naive. I don't think companies will ever go back to individual offices for everyone. But putting a soundproof barrier down the center of a bullpen is doable. One side is for the loud folks, the other for the quiet ones. Everyone can hop from one side to the other as needed.