Re:Updating classic workplace sabotage techniques
by pseudalopex on Sunday May 15, 2016 @05:57PM
(#11702958)
How is an open layout better for pairing than a shared office?
[ Parent
| on HN ]
Re:Updating classic workplace sabotage techniques
by dredmorbius on Sunday May 15, 2016 @07:12PM
(#11703215)
It's not.
Re:Updating classic workplace sabotage techniques
by parasubvert on Monday May 16, 2016 @01:52AM
(#11704479)
Pairs switch up every day or two and people switch teams every 12-16 weeks or so. Also there's a strong belief in "open door" policy for impromptu conversations with the product managers or other devs, and in having build/test/CD pipeline status screens visible by the team at all times.
Re:Updating classic workplace sabotage techniques
by douche on Monday May 16, 2016 @06:51AM
(#11705480)
So the status quot is one of constant churn and never settling into any kind of groove, ever.
Sounds extremely stressful
Re:Updating classic workplace sabotage techniques
by parasubvert on Monday May 16, 2016 @07:27AM
(#11705604)
If you're in a small team, you get to know everyone, and cross-pollinate the various skills some individuals may have over others. The groove and "team gel" happens within a couple of weeks.
It's not for everyone, and there are some "consulting" individual contributors here and there, but the point is to have a sustainable pace that's always "busy" and everyone is "checked in" rather than have a few weeks of "crunch time" to meet a deadline. Some need to "check out" for a while, that's also fine.
Most product cycles last 3-4 months, and it's up to you if you want to switch teams. some don't.