02. Computational Thinking
October 19, 2020
Agenda
Meeting notes
Note-taker: Kristen
Note-taking responsibilities will rotate, in first-name alphabetical order (Thu next session, then Zach, then Alice)
how computers work videos
- we didn’t know basically any of this
- Zach appreciates why maybe don’t have 1000 apps open at once
- idea of computer language new (talking to computer without a GUI)
- what did we know?
- questions?
- what stops them from editing any code in any computer?
- answer: some people do (see Linux)
- risk of breaking something or creating a vulnerability
- plus just hard
- Intellectual property issues may prevent code editing
- How was programming language developed?
- a Programming language is a program that allows you to write other programs
- usually happens within a community of developers
- see Pandoc, file conversion tool
- did the information in these videos make you think differently about anything you do?
- allayed some concerns for Zach
- Alice: no one is “tech savvy.” People just have different confidence
- Understanding how computers understand information
- Computers are good at counting and indexing
The Command Line
- In either git bash or terminal
- folder = directory
- different operating systems organize files differently
Business
- Announcements
- Individual updates and questions
Updates workflow
How to add your individual updates:
-
Navigate to the GitHub repository for this site and then to the logs folder
-
Download the file sample.md (click Raw and then save as wherever you keep your files for this group)
-
Open it up in your Atom text editor and save the file as name.md (your first name)
-
Edit the file to add your name and a few updates for this week
-
Pay attention to the syntax highlighting and follow the example when you add content
-
When you’re done, return to the GitHub repository. Use the branch dropdown menu (labeled master) and create a new branch. Name it something short (your initials or first name). This is your personal version of the repository.
-
In the logs folder, select Add file and Upload files
-
Write a brief comment to summarize your change (i.e. ‘updates for 10/19’) and select commit changes
-
Your updates will only be visible on your personal branch unless you create a pull request to merge them with the main branch
How to publish meeting notes:
-
Navigate to the GitHub page and make sure you switch to the master branch.
-
Download the markdown file for today’s session.
-
Use Markdown syntax to add your own notes. Save the document.
-
Return to GitHub and add the file in the same place while you’re on your personal branch
-
Navigate to Pull requests and click new pull request
-
Select master as your base branch and your personal branch as your compare branch
-
Select Create pull request and write a brief summary of the changes (i.e. ‘notes from 10/19 session’)
Discussion
Code.org videos
Command line
- Installations:
- Tutorial from DSRI
Resources
- Introduction to the Bash Command Line, Ian Milligan and James Baker, The Programming Historian
- The Unix Shell (for more advanced tutorials, see the “Loops” and “Shell Scripts” sections)
- Terminus command line game (a fantasy choose-your-own adventure like game) (good for getting use to navigating file structures–uses only a few commands)
- https://vim-adventures.com/
- https://codecombat.com/
For next time
- Add your updates by Monday morning 11/2
- Readings on DH in your discipline
- Archaeology, the Digital Humanities, and the ‘Big Tent’, Ethan Watrall, Debates in the Digital Humanities 2016 (Minnesota UP: 2016)
- “Digital Methods and Classical Studies”, Bernstein and Coffee, DHQ 10.2 (2016)
- Find additional resources, projects, and readings relevant to your sub-discipline
- Optional:
| «< Previous | Next -> |
Image: ENIAC (Electronic Numerical Integrator And Computer, By Unknown author - U.S. Army Photo, Public Domain, https://commons.wikimedia.org/w/index.php?curid=55124