3 ms·

I'm going to sound really entitled saying this, but I hate morning status meetings because they eventually end up being used as a "this is a reasonable time to

by WWLink 7y ago

I'm going to sound really entitled saying this, but I hate morning status meetings because they eventually end up being used as a "this is a reasonable time to expect you to be in the office by" kinda measuring stick lol. It ends up leading to unnecessary stress trying to make the damn 'meeting time'.

eden_hazard 7y ago
I know engineers are in demand and we are a high priced commodity but is it unreasonable for a company to expect you to be in office at a certain time? The standup at my current project is at 10:30. And most of us here come around 10.
- bpyne 7y ago
  It's not unreasonable. My team is usually in by 9, 9:30 at the latest. We take 20 minutes to get coffee and discuss issues, what needs to be done, etc. Then we set about completing tasks. A startup I worked at in the mid-90's had people working in pairs: a server developer and a client developer. They didn't care what hours you kept as long as you didn't hold up the other person in your pair. I arrived around 9:30am daily. The client guy I was paired with came in around 8:30am. I always stayed later so I'd check in code before I left and leave a message for him about the progress. He tested stuff before I arrived and went over any issues when I got in. Then we'd work together the rest of the day. Other engineers came in at 10:30am, noon, and as late as 1pm. They worked it out with their other halves the same way I did. I think wise managers work with the team, minding company-imposed limitations, rather than enforce personal preferences.
bpyne 7y ago
I can completely see it. In the hands of a controlling manager, it can be abused. My manager recognizes that we're usually in the office by 9-9:30 so we walk regularly at 9:30. Late day meetings are great too if it works better for the team. In my team's case, we also walk or ride bikes together at lunch. So we can also use that time if necessary, but usually we just keep it casual.

by WWLink 7y ago

eden_hazard 7y ago

I know engineers are in demand and we are a high priced commodity but is it unreasonable for a company to expect you to be in office at a certain time? The standup at my current project is at 10:30. And most of us here come around 10.

bpyne 7y ago
It's not unreasonable. My team is usually in by 9, 9:30 at the latest. We take 20 minutes to get coffee and discuss issues, what needs to be done, etc. Then we set about completing tasks. A startup I worked at in the mid-90's had people working in pairs: a server developer and a client developer. They didn't care what hours you kept as long as you didn't hold up the other person in your pair. I arrived around 9:30am daily. The client guy I was paired with came in around 8:30am. I always stayed later so I'd check in code before I left and leave a message for him about the progress. He tested stuff before I arrived and went over any issues when I got in. Then we'd work together the rest of the day. Other engineers came in at 10:30am, noon, and as late as 1pm. They worked it out with their other halves the same way I did. I think wise managers work with the team, minding company-imposed limitations, rather than enforce personal preferences.

bpyne 7y ago

I can completely see it. In the hands of a controlling manager, it can be abused. My manager recognizes that we're usually in the office by 9-9:30 so we walk regularly at 9:30. Late day meetings are great too if it works better for the team. In my team's case, we also walk or ride bikes together at lunch. So we can also use that time if necessary, but usually we just keep it casual.