-
Notifications
You must be signed in to change notification settings - Fork 44
TechNERDs
The TechNERD program started during Season 4 of Optimism Governance with the intent to further technical decentralization. They're Technical support specialists assisting developers building on the OP Stack. You can view the original governance proposal here.
This will have a training program that wanna-be TechNERDs can complete async. Once they've completed the program, they can start to answer questions in the discussion section. When they've proven themselves as reliable technical support, they can gain the TechNERD role.
The following are some general tips for answering technical questions effectively:
- Understand the question: Before you start answering, make sure you fully understand the question. If something is unclear, don't hesitate to ask for clarification.
- Use simple language: Avoid jargon unless you're certain the person you're talking to understands it. Explain things in plain language whenever possible.
- Discuss your thought process: Explain how you're approaching the problem. Laying out your steps can help identify any misconceptions.
- Admit when you don't know: Its okay if you don't know the answer. It is important to be honest with our limitations and offer to research or find out the information from someone else.
There will be many times when we don't have enough information to answer a question.
- Discuss desired outcomes: Understand what the person is ultimately trying to achieve. This can help us provide a more targeted response.
- Get environment information: Having more context around the operating system, configurations, software versions or git commit hash, log information, and other relevant information will help answer questions.
If a question is a duplicate, you can provide the following copy as a response and close the discussion thread.
Thank you for your question! It appears that this topic is being discussed or answered in [link to original thread]. I recommend checking out that thread for the information you're looking for. If you have any further questions or need additional clarification, feel free to ask in the original discussion. If you think this is a mistake, comment here, we're here to help!
If it turns out to not be a duplicate, re-open the discussion thread.