-
-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #149 from chennesy/add_jargon
- Loading branch information
Showing
2 changed files
with
56 additions
and
1 deletion.
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,44 @@ | ||
--- | ||
title: Jargon Busting | ||
teaching: 5 | ||
exercises: 30 | ||
--- | ||
|
||
::::::::::::::::::::::::::::::::::::::: objectives | ||
|
||
- Explain terms, phrases, and concepts associated with software development in libraries. | ||
- Compare knowledge of these terms, phrases, and concepts. | ||
- Differentiate between these terms, phrases, and concepts. | ||
|
||
:::::::::::::::::::::::::::::::::::::::::::::::::: | ||
|
||
:::::::::::::::::::::::::::::::::::::::: questions | ||
|
||
- What terms, phrases, or ideas around code, data, or software development have you come across and feel you should know better? | ||
|
||
:::::::::::::::::::::::::::::::::::::::::::::::::: | ||
|
||
::::::::::::::::::::::::::::::::::::::: challenge | ||
|
||
## Jargon Busting | ||
|
||
This exercise is an opportunity to gain a firmer grasp on some concepts related to data, code or software development in libraries. | ||
|
||
1. Pair with a neighbor or small group and decide who will take notes. | ||
2. Talk for three to five minutes about any terms, phrases, or ideas related to code, data, or software development that you've come across and perhaps feel you should know better. | ||
3. Have the note-taker compile your list of problematic terms, phrases, and ideas. | ||
4. Now in a larger group (or with everyone in the workshop) spend 5 to 10 minutes working together to try to explain what some of those terms, phrases, or ideas on your list mean. You can use other people in the room/Zoom, the Carpentries' Glosario below, and other internet research to learn more about the terms. | ||
5. The instructor will collate terms and explanations on a whiteboard or Etherpad and facilitate a discussion about what we will cover today and where you can go for help on things we won't cover. | ||
|
||
### [Carpentries Glosario (English)](https://glosario.carpentries.org/en/) | ||
While there's not a single site that will include *every* term that workshop attendees bring to the table, the Carpentries' glossary is a great starting place for computing and data science terms. [Glosario includes multilingual glossaries](https://glosario.carpentries.org/), as well. | ||
|
||
:::::::::::::::::::::::::::::::::::::::::::::::::: | ||
|
||
|
||
:::::::::::::::::::::::::::::::::::::::: keypoints | ||
|
||
- It helps to share what you know and don't know about software development and data science jargon. | ||
|
||
:::::::::::::::::::::::::::::::::::::::::::::::::: | ||
|