Earlier quoted context omitted.
I think the "war room" solution is often a symptom of generalized poor management. And bad project management drives away experienced staff. The open office plan is a nightmare for tech work IMO.
Then how do you explain the many happy teams I see working in exactly that environment, and how do you explain the research? (Part of the confusion may be that "war room" and "open plan" are not synonyms. The former only includes people actively working on the project. This is not the environment where you have the sales guy yapping on the phone.)
A Short Rant About Working Remotely
331–339 of 339 posts
Re: A Short Rant About Working Remotely
#332Earlier quoted context omitted.
Whether or not there are some measurable benefits to the company for telecommuting does not matter . What matters is this: (1) The software company needs your software skills more than you need the company. (2) You decided and plan your life around telecommuting. (3) So telecommuting is non-negotiable. Non-telecommuters tend to be wary of remote workers, not because they are any more or less productive. There's an un…
Whether or not there are some measurable benefits to the company for telecommuting does not matter. I don't think that it's always this clear cut. In other words, the managers, speaking for the company say they want more "productivity". What they really need is more control and reduction of risk. They feel a certain level of assurance when they can see people walking into the office on time, every day. It assures the…
If you only address that want, then you are not addressing the underlying need.
Lots of people say they need to get stuff done, but that is not the true underlying need. These are usually driven by deeper motives, generally relating to need for parental approval (fame, glory, success, achievement, etc.), need for security, and need to eat.
Why do you really want to build a startup? If you're honest with yourself, you'll generally find that your want and need don't match. (And if you are impeccable, and your want and need matches, things tend to go smoother).
Re: A Short Rant About Working Remotely
#333Earlier quoted context omitted.
As you suspected, I'm developing solutions in the areas I work in specifically (stuff I'm "knee-deep" in). I read the usual CS papers, plus lots of PhDs thesis. I follow the references in the bibliographies like crazy, and I also look up the writer's on the 'Net and see what other stuff they've done/written. It feels like detective work, actually: the most-cited papers are frequently not the best. There's tons of res…
It feels like detective work, actually: the most-cited papers are frequently not the best. There's tons of researchers working in obscurity but who nevertheless have useful results. What are some examples of the best research that is obscure?
In general, stack languages are great for graphics in both 2 dimensions (PostScript) and 3 dimensions (GML)[1].
[0] http://digisrv-1.biblio.etc.tu-bs.de:8080/docportal/receive/...
[1] http://en.wikipedia.org/wiki/Generative_Modelling_Language
Re: A Short Rant About Working Remotely
#334(lightly edited copy of my usual plea for evidence on this topic ;-) Pretty much all the evidence (rather than anecdote) I can find shows that co-located teams in a single team room environment are the most productive - all other things being equal. (And I'm saying this as somebody who spends a lot of their time working from home, and talking to other folk over Skype, etc. There are reasons for telecommuting - person…
Very relevant video from Gabe Newell about this topic. http://www.youtube.com/watch?v=t8QEOBgLBQU&t=22m30s
Re: A Short Rant About Working Remotely
#335Earlier quoted context omitted.
The most productive team I worked with, and one of the most senior teams within an organization of several tens of thousands with a very significant development staff, was approximately 50% remote, depending upon how one measured and when one included some remote developers and operations people (also very senior) who were intermittently present depending upon project needs. (Some of the operations people were often…
Granted, I and the people I've described may be a minority. But in my observation and perhaps in staid corporate environments, those who benefit from colocation tend to be those who need to be herded and hand-held. Those who want and are really able to get shit down, don't mind face to face but are greatly frustrated with pointless and distracting face to face. I too don't know what the numbers are like. I've seen gr…
I'm plenty social. And I'm not a snob -- I can talk with most anyone, about genuine interests (interests on either party's part, not just my own). Or just sit around drawing spirals in the pancake syrup, for a while.
I don't particularly enjoy discussing the latest Hollywood movies and actors ad nauseum, whose existence and which conversation seems to serve significantly to reinforce established, simplistic stereotypes. Especially when the conversation ranges in exactly that direction.
I don't enjoy conversations that "get personal", looking for ways to pick apart those not present (behind their back). Or that look for ways to pick apart those present, in active, emotionally manipulative pursuit of a pecking order.
On the team I described, we socialized, although people were on average fairly reserved. A good part of that socialization reflected people actually paying attention to and remembering what each other were interested in and doing, and what was going on in their lives.
Again, this is just an opinion, but I think some of the "anti-social" attributed to "nerds" and "geeks" is rather an active dis-interest in much of the lowest common denominator of what we consider "social".
(Some, not all. I've met plenty of intellectual assholes, too.)
Another, personal example: I rather enjoy playing sports. I couldn't care less about watching paid professionals doing it. (This does vary somewhat by sport and event. Also, if anything, I tend to find amateur games more interesting; they bear a closer relationship to my life than the over-produced, over-medicated thing that professional sports has become. Upon reflection, maybe this is a somewhat arrogant or avoidant attitude on my part; I received a lot of abuse as a kid for not being "sports-wise" -- something my father wasn't and never passed on to me.)
I've spend too much time and energy on self-doubt, as it is. A lot of places and people have told me that I'm the one who needs to change. They love my work, and how do I do that? But, you know, "We all work in cubes."
If you are outperforming your peers (and, not infrequently, management) and otherwise succeeding, then, well, who has the problem?
The following may take the interpretation a bit far, but: The bully will always insist that it's "your problem".
Re: A Short Rant About Working Remotely
#336"...But I don't see a reason why, in 2013, given the tools we have, a developer has to be on-site at a desk every day, as the normal operating procedure..." I am struggling with this same question, but from the other side. I help teams become more Agile, and I'm a startup junkie, so all I care about is performance here. I want to know what works best in terms of product quality and pivot ability. And guess what? So f…
I'm generally not interested in hiring remote workers at our company. While it can work in rare cases (where the need for collaboration is low) it is much more the exception than the rule for us. Our company culture and structure is based around trust and collaboration. We allow VPN/remote work, but as a tradeoff. For the most part, our employees are local and have a desk in the office that they spend most of their t…
Did this help things at all?
Re: A Short Rant About Working Remotely
#337Earlier quoted context omitted.
Yes, but haven't the tools for working remotely improved a lot since 2006?
Not really - no. I can't think of anything off the top of my head that I couldn't do six years ago. There are a few more options maybe - but nothing fundamentally different .
For example, a cell phone from today isn't fundamentally different than a cell phone from a decade ago. They're both computers and can be used to make phone calls. But with the cellphone of today, I can have a virtual meeting with anyone from anywhere, face-to-face. That alone is a huge improvement for distributed teams.
Re: A Short Rant About Working Remotely
#338Earlier quoted context omitted.
> If I need to ask a teammate a question, I turn my head slightly to the left and ask them. Avoiding this is the primary reason I like working at home. Getting distracted by things like that are a productivity killer for me.
Because team work is all about you , right? Quite a myopic view. How dare anyone try to increase the productivity of the team by stealing precious seconds from you! Teams are more productive when they're in the same location. That is a fact. Your individual productivity may suffer at times, but the team will do better overall if you all work together in one location.
Re: A Short Rant About Working Remotely
#339Earlier quoted context omitted.
I'm generally not interested in hiring remote workers at our company. While it can work in rare cases (where the need for collaboration is low) it is much more the exception than the rule for us. Our company culture and structure is based around trust and collaboration. We allow VPN/remote work, but as a tradeoff. For the most part, our employees are local and have a desk in the office that they spend most of their t…
> For what it's worth we have done several experiments. We even tried having a remote worker on a constant skype connection, with a monitor/camera in a shared office with other workers (over a period of several months). Did this help things at all?