Hacker News Reader

Comment by papito | Hacker News Reader

Oh, God, I hate that. I would rather get the stand-ups out of the way first thing in the morning so I can have interrupted time before lunch, but most software engineers are massive divas, who think it's a horrible affront to be in the office before 10AM. And even then some people are regularly late.

And now with no commute for most of is, it's still somehow difficult.

View on HN

A lot of developers are of the late chronotype. That has nothing to do with being a diva, immature or lazy, it's just how we're built. There are plenty of reasons developers can be divas, but being a night owl isn't one. Chronic sleep deprivation will drastically shorten one's life span.

Yes, I did my share of that. Then I started going to be bed early, got myself an accu-pressure mat and all. Does wonders. How many of these people who are late nighters simply postpone going to bed, squeezing in that one movie before 1AM? And then they are wet sponges in the morning.

I am not denying genetic traits, but like with most things, it's not the only factor.

Not everyone's circadian clock works the way yours does. I hate having to schlep myself out of bed to join a pointless status update meeting half asleep.

10AM already is before my definition of "first thing in the morning".

Maybe we should just kill the synchronous status update meeting altogether and avoid conflicts like these?

Just block out the rest of your day and auto decline meetings. I do that and it works great. Forces everyone to schedule everything before noon. Also make sure to schedule lunch in as well. It make sure you auto decline that’s the trick. If you’re manually approving/declining each one you’ll end up allowing some which signals the blocked out time isn’t that blocked out to the rest of the team.

If you are not a manager, that sounds a little agro. I can stand for my untouchable lunch break, but the rest is not up to me.

Reply on news.ycombinator.com