News for hackers. Stuff that matters.
Re:Stop Working More than 40 Hours a Week by majelix on Friday February 15, 2013 @10:51AM (#5226727)
> without losing face.

Honestly, isn't the crux of the problem? Even if you are a superstar, you'll still get typecasted as smart-but-lazy and find yourself on the outside. Generally speaking, this is an organizational problem.

Re:Stop Working More than 40 Hours a Week by hvs on Friday February 15, 2013 @11:26AM (#5226923)
In many offices, you need to be around when things come up. There are very few jobs where you come in, work by yourself for 8 hours and then go home. Communication is important, and if you aren't there, it's hard to communicate.
Re:Stop Working More than 40 Hours a Week by greedo on Friday February 15, 2013 @11:30AM (#5226940)
Email, sms, voice can cope with crisis that arise. In a small office face is important; less important in an environment that's geographically distributed.
Re:Stop Working More than 40 Hours a Week by potatolicious on Friday February 15, 2013 @11:57AM (#5227065)
Very little communication I have around the office are crises - but they are important. If I insisted on having a completely different schedule from my coworkers, I'd either be impeding their work, or subjecting myself to emails, SMSes, calls, etc, outside of my work hours.

Lots of company have flex time so people can choose their hours but have some overlap for communications. This is also where the "mid day meeting rush" comes from that exacerbates the situation.

Re:Stop Working More than 40 Hours a Week by typicalrunt on Friday February 15, 2013 @02:48PM (#5228091)
This. The medium of communication really depends on the type of content and it's priority.

High priority: call me or use some other synchronous communications protocol. Everything else: email, ticket please. Async is better.

I'm used to working in geographically separated teams in different timezones, so starting my day 2 hours ahead of everyone else is no different than me working in a different timezone. Once you solve this problem, you have solved the majority of your communication difficulties.

Re:Stop Working More than 40 Hours a Week by bskap on Friday February 15, 2013 @07:09PM (#5229622)
Sure, but when that emergency crops up in the middle of that 40 minute commute, you aren't going to be helping the team very much.
Re:Stop Working More than 40 Hours a Week by greedo on Saturday February 16, 2013 @06:31PM (#5233510)
It's no different than being out to lunch. You're 20 minutes away from the office in your scenario, and hopefully you're not the only person who can fix things. No one should be the company savior, and if you can't leave the office, you have bigger issues than working different schedules.
Re:Stop Working More than 40 Hours a Week by jes5199 on Friday February 15, 2013 @12:41PM (#5227298)
but the question is: what's the time range necessary for immediate communication? Do all developers need to be in full-communication mode for a full eight-hour span? And if so, when does code get written?
Re:Stop Working More than 40 Hours a Week by enraged_camel on Friday February 15, 2013 @01:07PM (#5227451)
They don't need to communicate immediately, but when I ask a question to a developer I need them to get back to me on that same day. For most of my projects I cannot afford to wait until the next day for an answer. I emphasize this in every email I send. It usually goes something like, "I understand if you're busy working on something else at this very moment. However, this is for a project due tomorrow morning so I would appreciate a response before lunch/end-of-the-day."
Re:Stop Working More than 40 Hours a Week by jes5199 on Friday February 15, 2013 @05:07PM (#5228969)
Is there always exactly one developer who has the answer to each of your questions?