-
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
practices: asking questions - new page
- Loading branch information
1 parent
afbb275
commit b4724a4
Showing
3 changed files
with
48 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# Asking Questions | ||
|
||
The way to get useful answers is to ask effective questions. | ||
|
||
The act of creating an effective question can often produce the answer without even needing to share the question with others (although it is valuable to still ask for a wider scope of answers). | ||
|
||
The act of creating a question allows for a clear analysis of what the problem is, what has been tried already. | ||
|
||
|
||
!!! HINT "No need to apologies for asking" | ||
People enjoy answering other peoples questions as it provides a sense of satisfaction that they could help. There is never a need to apologies that your are asking a question, especially if you think the answer should be obvious | ||
|
||
!!! HINT "There are no silly questions" | ||
People are not born omnicient, they spend their lifetime learning on a unique path. No two people will understand all the same things in the same way, even when working in the same area. | ||
|
||
|
||
|
||
## Ask an Engineering question | ||
|
||
The more detailed an engineering question is, the more likely that an appropriate answer will be given. | ||
|
||
1. Convey the goal of your question (what are you trying to achieve) | ||
2. Establish the facts as clearly as possible | ||
- What steps did you try | ||
- How does someone else reproduce this issue (create the simplest possible example) | ||
3. Convey assumptions made | ||
4. Examples, examples, examples | ||
5. Review and refactor (remove unnecessary words and information, reread and rewrite to ensure the question is easy to understand) | ||
|
||
!!! WARNING "Fast questions take more time" | ||
Asking questions with little or no thought leads to much more time spent explaining the question once its out there. | ||
|
||
|
||
### Example questions | ||
|
||
Some example engineering questions (TODO: review questions in slack / stack exchange for useful, not so useful examples) | ||
|
||
|
||
|
||
## The Art of Asking Questions | ||
|
||
1. Demonstrate preparedness for the conversation | ||
2. Illustrate your expertise without showing off | ||
3. Invite others to deepen or broaden their thinking and challenge held beliefs | ||
|
||
[Article from the Harvard Business School](https://hbr.org/2022/05/the-art-of-asking-great-questions){target=_blank .md-button} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters