Live data from Hacker News

How GitHub Works: Be Asynchronous

zachholman.com

61–62 of 62 posts

Re: How GitHub Works: Be Asynchronous

#61
post #12

For a number of years I had a team in five offices in four timezones, so asynchronous working became the norm. We used Skype however. The only "rule" that needed to be enforced was "Away means Away, Available means Available" A lot of realtime problems got stymied by people thinking others were ignoring them.

The "away" rule seems counter productive. The value of async is that I can ask you a question when convenient for me, and you can answer when convenient for you. If I have to wait for your status to become available, I'm wasting my attention.

Basically it means we should trust the "away" message, but still can drop a line if you want. Away could also mean "mentally busy" or "on the phone"

If I could trust the away messages, as a team lead I always had a status board as to where my team was (since we were in five offices)

Re: How GitHub Works: Be Asynchronous

#62
post #35

> I tend to loathe meetings even more than 37signals. Zach, can you go into more detail? From the few things I’ve seen, you seem to admire them more than despise them. Is there a particular reason for your displeasure?

It should read as > I tend to loathe meetings even more than 37signals loathes meetings. (assuming you are not being facetious)

Doh. I honestly misread that line. Thank you.
Post reply on HN