Earlier quoted context omitted.
> Walking over and talking to someone is still far superior to any online communication. The reason it isn't, for me, is that I'm usually answering questions about Why we do something, or How something is supposed to work. I'm usually giving a quick response, with a link to a design, or a code snippet, or a git commit, or a Code Review link, or something online. So I have to provide an online response whether you ask…
Yeah I guess the difference is that at my workplace there's a lot of tribal knowledge. Even when there is a design document it often hasn't been updated or requires nuance to interpret that's only really in one or two peoples' heads. Often the question/discussions is about engineering priorities, some discovery was made during coding that would alter the design, and half the time simply bringing up the topic with the…
It seems like what you really want is for others to treat your emergencies as theirs. They're not, they're yours. If you can't wait 15 minutes for a ping back without being completely stuck, you aren't planning your work correctly. That's nobody else's fault.