News for hackers. Stuff that matters.
Re:Ask HN: How to implement “office hours” as a software eng... by pc86 on Friday January 17, 2020 @10:15AM (#22075261)
"Office hours" as an individual contributor developer will never happen. But for the sake of argument..

1) Do you have the organizational and political clout (and skill) to institute this?

You can say "no admittance!" all you like, but if you're a mid-level dev and your lead needs something, you're going to get interrupted. Like it or not this sounds like a big culture change and it's not something even most senior devs have the organizational power to implement.

2) Are you prepared for the objections and potential backlash?

Whether we like it or not software has gotten written for decades with the devs fighting against constant interruptions from peers, managers, and other random coworkers.

3) Do you really need this?

Sort of building off #2, what makes your project or your work so special that you need to be available for only certain specific times of the day?

4) Are you prepared to push back?

So let's say you actually get this implemented. Then your boss's boss's boss comes up to your desk in the middle of your working time and asks to talk to you. Are you going to tell them no in front of all your peers? Are you prepared for them to get upset with you? There's no way your "no admittance" time would be on their radar unless it was a team-wide change (and even then, maybe not).

--

In reality, most of us are not working on anything so complicated and important that the occasional interruption is a terrible thing. The same way 99% of companies do not need to hire the best rockstar developer they can find, most developers are good-not-great at their jobs and realistically being interrupted is not going to cause us to miss deadlines or put out terrible code.

There are no comments on this comment yet.