News for hackers. Stuff that matters.
Re:Maximizing Developer Effectiveness by piva00 on Saturday January 16, 2021 @08:11AM (#25801985)
In my current team (and my previous one from another company) we have what we call "goalie" duties. Each week one engineer from the team is responsible for answering inquiries, not necessarily they have to know the answer but they are the ones to be interrupted and handle accordingly.

It works pretty well, our devs are capable of assessing urgency to either bring it up on Slack, wait for the next stand-up or call to arms if it's something critical.

It improves rapport with stakeholders and other teams; it improves morale, it's predictable who will be interrupted during the week, alleviating that from the rest of the engineers. And as a side-effect it helps to force knowledge sharing over time.

Re:Maximizing Developer Effectiveness by jy2947 on Saturday January 16, 2021 @11:48AM (#25803393)
Isn't the typical responsibility of the manager or the team lead?

Inquire often is followed with more requests, if each developer serves as the weekly-speaker-of-the-team, will the external partner eventually figure out "John will do anything for us and Steve is mean"?

Re:Maximizing Developer Effectiveness by gregd on Saturday January 16, 2021 @10:32AM (#25802814)
This is actually a great idea and something I'm likely to bring back to my own teams!