News for hackers. Stuff that matters.
Re:Why to Not Not Start a Startup by nostrademons on Sunday May 23, 2010 @02:28AM (#1371931)
"My favorite part about being self-employed is that I can say something nobody can say at a big company: "The firm will not benefit from my further presence today. Well then, I'm done. See you tomorrow."

I say that on average about once or twice a week at Google. (The other days, the firm would benefit from my further presence, and I'm there till late.) Nobody bats an eyelash.

I wonder perhaps if a large part of Google's recruitment and retention advantage is that they get this, and understand that you're responsible for your own productivity and should do whatever it takes (including taking time off) to maintain that. If you want to come in at 1 and work till 10, nobody cares as long as you're getting stuff done in those hours. There've been times where I worked 12 hour days for 2-3 weeks, followed by 6 hour days for the next week after that. The guy who integrated the PacMan doodle was in the office from about 1 PM to 8 AM a couple days before it was scheduled to go live, but then yesterday he came in at about 1 and left after dinner.

Re:Why to Not Not Start a Startup by iskander on Sunday May 23, 2010 @04:59PM (#1373001)
>come in at 1 and work till 10

I did an internship at Google, so I have only seen one team in action for a small period of time. That said, there were a shocking number of meetings-- daily standups, one-on-one meetings, video conferences with California, weekly team meetings, cross-functionals and a few extra bits of coordination bureaucracy. These were scattered throughout the day in a way that put firm limits on how free of a schedule you can make for yourself.

Re:Why to Not Not Start a Startup by nostrademons on Sunday May 23, 2010 @08:52PM (#1373471)
It depends a lot on which team you're working on, how tightly they're colocated, and what your role on the team is. When I was working on the effort to move all the different search properties into google.com - which involved teams in 5 different offices scattered all across the U.S. and China - there were quite a few meetings, several at odd times to accommodate the time zones. (My tech lead took the brunt of that herself, though.) When I was working on the visual redesign, which mostly involved a tight team colocated in a single cube - I came in when I felt like, because if I needed to talk to someone, I could just turn around and ask them something.

Also, oftentimes interns don't have a firm grasp on which meetings they can skip and which they really should show up for. There are at least 4 weekly or bi-weekly meetings on my calendar that I rarely go to unless the particular week's topic is relevant to what I'm doing. I always go to meetings that are specifically scheduled with me, and usually go to the daily standups. It takes a while to develop the organizational awareness to make the distinction, though a usually good rule of thumb is that meetings that someone specifically sets up with you should be attended, while meetings that you're invited to simply by virtue of being a member of some group can safely be skipped.