gchappel Goto Github PK

• 👋 Hi, I’m Gavin (@gchappel)
• 👀 I’m interested in becoming a better engineer
• 🌱 I’m currently learning how to stop procrastinating on learning...
• 💞️ I’m looking to collaborate on anything that's causing you a problem. I like solving problems.
• 📫 How to reach me
  • Webex

Some things I've learned (and try my best to practice) to help communicate more effectively...

• Don't just say "hello" - I work for a global company, if you send me just a "hello!" outside my working hours, I'm not going to see it until the next day, which isn't a good use of anyone's time. Help me answer your questions more quickly by just asking them outright. I promise I won't think you're rude if we don't exchange a full three-way handshake of pleasantries first.
• In a similar vein, don't ask to ask, just put the question out there, whether privately or publicly, but...
• Preferably publicly. We have a lot of Webex spaces, with a lot of really knowledgable people. Questions almost always belong in a public space. If it isn't something that only I can answer then you'll probably get your answer much quicker. And if it is something that only I can answer, it'll still be there for me to answer the next day as soon as I see it.
• In a nod to my troubleshooting heritage, the X/Y problem is a useful concept to be aware of. When you're having a problem, ask questions about the problem, not about what you perceive as the solution. This has some advantages:
  • maybe your solution is not going to solve the actual problem, or it will cause different problems. If you explain the problem then people can work together with you on finding the best available solution
  • articulating your problem (particularly in text) can also be a form of rubber ducking; maybe halfway through writing your message about the problem you solve the problem yourself, which is unlikely to happen when you're instead writing a message about a solution that you don't know how to implement