A lot of work this week, possibly fueled by too much caffeine (3 cups in 4 days is a lot for me). But I am practicing deep work techniques to avoid email, single task and stay in the flow.
Jvns post from a couple days ago caught my attention. Just today I encountered both sides of how to answer questions in a helpful way.
How you phrase a question is important:
- Rephrase a more specific question back at them (“Are you asking X?”)
- Ask them for more specific information they didn’t provide (“are you using IPv6?”)
- Ask what prompted their question. For example, sometimes people come into my team’s channel with questions about how our service discovery works. Usually this is because they’re trying to set up/reconfigure a service. In that case it’s helpful to ask “which service are you working with? Can I see the pull request you’re working on?”
When asking a question, you need to be cognizant that the other person may not know your level of understanding. Set the state by giving them some insight into your point of view. Maybe start with a drawing.. Visualizing the problem often makes it easier to communicate.
Figuring out what your question-asker knows already is important because they may be confused about fundamental concepts (“What’s Redux?”), or they may be an expert who’s getting at a subtle corner case. An answer building on concepts they don’t know is confusing, and an answer that recaps things they know is tedious.
Building on the idea of visualizing the problem, when talking about how you solve a problem, try to show what you did and explain your thought process
New person: “I’m seeing errors on the site, what’s happening?”
More Experienced Person: (2 minutes later) “oh that’s because there’s a database failover happening”
New person: how did you know that??!?!?
More Experienced Person: “Here’s what I did!”:
Often these errors are due to Service Y being down. I looked at $PLACE and it said Service Y was up. So that wasn’t it.
Then I looked at dashboard X, and this part of that dashboard showed there was a database failover happening.
Then I looked in the logs for the service and it showed errors connecting to the database, here’s what those errors look like.
High Frequency Trading
If this doesn’t seem like a company run by a Bond villain, I don’t know what does: Citadel