And if you don't reply within 24 hour: fired. By me at least. (don't be silly, I don't have the power to fire anyone anymore).

Yes, expecting a reply by email sooner than e.g. 4 working hours is futile.

But if you work in a team and only communicate once a day then you are not a team member, you are an ar#eh#le.

If you constantly check your emails and slack and write replies immediately then yes, we should probably have a chat about your time focus and productivity. But checking your emails quickly once an hour is common sense. And where appropriate with a quick receipt response, not a full answer.

And e.g. slack every 15 minutes or half an hour. Perhaps in a Pomodoro break or similar. (channel dependent)

It would perhaps be a good idea to have a well-known team/department convention on response times. More asynchronous for email especially if not internal (hours not days). Quite asynchronous in company-wide public slack chats, and more responsive but not instant in team irc-like chats.

Whether you program, write content, make sandwiches etc is no excuse to be an ar#eh#ole.

Maybe this is true if you're a bottom-level grunt programmer with nothing of value to give to other people in the company.

I reply to say "I will get to this request in x amount of time," and that amount of time simply increases as the requests go up and I factor in time spent focusing and context switching.

I check slack every hour or so. Not because I have to but as a break from coding. However it doesn’t mean I’ll answer every question or switch context.