undefined | Better HN

0 pointsrglullis6y ago0 comments

Yes, it is that bad for some people. But most importantly, even if it meant "just" 5 minutes to get back into flow, you still have an organization that doesn't know how to share information and you have a manager that is crippling team productivity without even knowing.

https://www.joelonsoftware.com/2001/02/12/human-task-switche...

> I agree people should try and work things out on their own before asking for help

That is far from ideal in two ways:

- knowledge sharing suffers. You do your research and solve your problem or you don't and you have to ask to someone else more experienced. Knowledge sharing is kept to an oral tradition. Teams quickly start depending on one or two key members and juniors are often with a feeling with being left alone.

- you still have this anxiety of "when is it okay to interrupt?" On both ends. Everyone's threshold is different, so there is always someone who will be annoyed by the interruption and suffer.

The way to fix this is by promoting collaboration (pair-programming sessions are great and both partners already expect the communication, so "flow" is easier to maintain, also it is terrible to do on open-floor plans) and having a clear written practice to share knowledge and documentation.

There is no single situation where an open plan office leads to more team and individual productivity.

0 comments

4 comments · 1 top-level

ryandrake6y ago· 3 in thread

In my experience, "Being able to be productive while not in The Zone" is a job skill like any other that can/should be learned and improved with practice. I used to be like that, where if you said peep to me while I was focused, I snapped out of it and couldn't work my way back up to productivity easily. This is kind of a "junior developer" problem that IMHO developers just need to overcome with practice. Having a kid helped me a lot. Suddenly there were distractions all day, and I was forced to learn how to be productive in 30 minute spurts.

As one gets more senior in their development career, their days will get more and more punctuated with meetings. You start gradually moving from the "maker" to "manager" schedule. So your reality will be a day with a handful of 1 hour time slots available for deep work. In my view you just need to deal with this reality and learn how to be productive in it.

iateanapple6y ago

> In my view you just need to deal with this reality and learn how to be productive in it.

IMO, senior developers who are “productive in it” are getting by on pattern matching.

Just like I can drive to my local mall without even thinking about it.

They haven’t actually learned how to be productive working this way.

tanseydavid6y ago

>> Just like I can drive to my local mall without even thinking about it.

I have seen plenty of software that appears to have been written by someone who was 'not even thinking about it' and it is invariably problematic and expensive-to-maintain.

Do you really believe there are senior devs that are productive without even thinking about it?

That just strikes me as odd -- maybe they are working on stuff should be given to Juniors?

1 more reply

rglullisOP6y ago

Yeah, after two kids I did manage to learn to deal better with interruptions, but I still feel a difference between "able to work" and "being in the zone". I am able to be interrupted in the middle of a list of actionable items and resume to it somewhat painlessly, but ask me to, e.g, plan a sprint or write a longer-term strategy doc and I will just wait until all the lights in the house (or office) are out.

I do disagree, however, about it being a problem related to lack of experience. It is good when someone can learn to handle interruptions, but it's even better when they don't have to. Handling interruptions and impediments are the main responsibility of a good manager, not of the developers.

j / k navigate · click thread line to collapse