10:30 because we have some early and some late workers. Has turned out to be helpful for the parents in the team too
09:00 at the start of the daily “Kernarbeitszeit”. I am not sure how to translate the term. A literal translation is “core working time”. Basically, my employer gives us the option to work between 06:00 to 18:00 with mandatory “presence” (working from home is possible) from 09:00 to 15:00.
We call it flexible office hours with an expected presence between 9 to 15. It's not a smooth as kernarbeitzeit though.
12:15, which is great as we break for lunch at 12:30. It prevents the time-wasters blathering on endlessly, as they are focused on lunchtime. A maximum of 15 minutes of wasted time.
A maximum of 15 minutes of wasted time.
🤣
9.30, which works well for me because I'm not awake enough/caffeinated enough before that to be able to be coherent or have much idea what I am doing that day. Although often I don't really see the point in them when our team is so fragmented and working on loads of different projects.
As early as possible, if everyone is in the same timezone. First thing in the morning. We devs work on a maker schedule, not a manager schedule. Get meetings out of the way so that you have the rest of the day to be productive.
10:00. We normally don't have meetings before 10:00 in the engineering dept. I'm cool with the schedule because that leaves time for kid transport and wordle and connections
Same
Fully remote job and we have people spread across time zones. We just moved it to 8:45 AM west coast time, because the previous 7:15 time slot wasn't working for those of us way over here. I kinda feel bad for the east coast people who have to do it at 11:45 now, since that's usually lunch time for me.
Really I wish we'd go back to just not doing standups.
Do you have other regular meetings? I'm at a fully remote company and if we didn't have stand ups I probably barely ever talk to my coworkers via anything more than email and chat.
Way too many other meetings. Meetings all the time.
There was a nice period where we had 2 meetings a week. One team meeting, then one social happy hour meeting with just the devs and no manager. (Mostly so we could complain about the manager, but general social bonding also). We also did plenty of ad-hoc meetings as needed, but generally the two regularly scheduled ones struck a good balance of getting things done without wasting time.
In hindsight, that manager could be a difficult person to work with, but the overall balance of trade-offs was way better with him than it is now. Very few, very efficient meetings, were one of the positive tradeoffs for sure.
8:30. It was basically just the only timeslot when everyone involved in the project was free.
Not a fan of it, though. The parents in our team frequently miss it, because personal life gets in the way.
And for me, it was annoying during the summer, as I then prefer going to the shops early in the morning, before the scorching heat arrives, and well, one of the shops around here doesn't open until 8:30, so I could only go there on Saturday or risking a heat stroke...
Noon or a little after. Works for me, though it does punch a hole in the day
Our team has daily meeting at 10am, but for me it’s 7pm, yay remote work w/9h difference in TZs.
12 PM, Ofcourse before lunch, otherwise you'll find me sleepy
11:30 am my time. It's annoyingly late, but necessary because I work with people who range from half an hour ahead of me to 2 hours behind me.
Same for me. My team spans 4 time zones and I'm in the eastern one
10 am. Not too early and not too late.
09:30 on my team. Between multiple project teams I believe our dailies are between 9:00, maybe slightly before too, and 10:00. Can also depend on the customer if we're part of their development team. I believe not all teams have them every day.
It's a good time for me because I sometimes begin at around 9:00.
At 9:00 begins our central working hours where we're expected to be working. And I think that's late enough for the late starters. So I like where we're at.
I think it's good to have it "early" rather than late. If you struggled the previous day it's a good point of fresh start and possible discussion or follow-up support. It's also where you have [to make] a plan for the day.
9:00
Had been using audio recordings in a slack thread on one client for 6 months. The time varied but it was good as the lack of discussion meant that it was kept short. However the timing was very imprecise.
i am involved in 4 teams right now in some capacity, so, 830, 900, 930, 1000. id prefer any timea round 9 or 930
2PM and I chose it that way with my project manager. That way I can have either at the end of my day or at the start of my day.
We rarely really need it but we enjoy the casual chit chat as the serious stuff is handled in less than 5 minutes.
A community for discussion amongst professional software developers.
Posts should be relevant to those well into their careers.
For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out: