Important

The grade free zone covers classes 1-5, ending on 2022-09-21.

Review#

Review After Class#

After each class, you will need to review the day’s material. This includes reviewing prismia chat to see any questions you got wrong and reading the notes. Some days there will be specific additional activities and questions to answer. These should be in your KWL repo.

2022-09-07#

related notes

Activities:

  1. More practice with GitHub terminology

  2. Review the notes after I post them

2022-09-12#

related notes

Activities:

  1. review notes after they are posted, both rendered and the raw markdown

  2. map out your computing knowledge and add it to your kwl chart repo. this can be an image that you upload or a text-based outline. (optional) try mapping out using mermaid syntax, we’ll be using other tools that will faciltate rendering later

  3. fill in the first two columns of your KWL chart

2022-09-14#

related notes

Activities:

  1. Follow along with the classmate issue in your inclass repo from today. Work with someone you know or find a collaborator in the Discussion board

  2. read the notes

  3. try using git in your IDE of choice, Share a tip in the course discussion repo

2022-09-19#

related notes

Activities:

  1. Review the notes

  2. Reorganize a folder on your computer ( good candidate may be desktop or downloads folder), using only a terminal to make new directories, move files, check what’s inside them, etc. Answer reflection questions (will be in notes) in a new file, terminal.md in your kwl repo.

  3. Make a PR that adds a glossary entry to your team repo to define a term we have learned so far. Create an issue and tag yourself to “claim” a term and check the issues and PRs that are open before your.

  4. Review past classes activities (eg via the activities section on the left) and catchup if appropriate

Start with a file explorer open, but then try to close it and use only command line tools to explore and make your choices

### Terminal File moving reflection
1. Did this get easier toward the end?
1. Use the history to see which commands you used and how many times each, make a table below.
1. Did you have to look up how to do anything we had not done in class?
1. When do you think that using the terminal will be better than using your GUI file explorer?
1. What questions/challenges/ relfections do you have after this?
1. What kinds of things might you want to write a bash script for given what you know in bash so far? come up with 1-2 scenarios

2022-09-21#

related notes

Activities:

  1. Read today’s notes

  2. Update your KWL chart with the new items and any learned items.

  3. Update the title to any discussion threads you have created to be more descriptive

  4. add branches.md to your KWL repo and describe how branches work and what things to watch out for in your own words.

2022-09-26#

related notes

Activities:

  1. Review and update your listing of how data moves through a program in your abstraction.md. Answer reflection questions.

  2. practice with the hardware simulator, try to understand its assembly language enough to modify it and walk through what other steps happen.

  3. Update your KWL chart with the new items and any learned items

1. Did you initially get stuck anywhere?
1. How does what we saw with the hardware simulators differ from how you had thought about it before?
1. Are there cases where what you previously thought was functional for what you were doing but not totally correct? Describe them.

2022-09-28#

related notes

Activities:

  1. Practice with git log and redirects to write the commit history of your main branch for your kwl chart to a file gitlog.txt and commit that file to your kwl repo.

  2. Review the notes

  3. Update your kwl chart with what you have learned or new questions

2022-10-03#

related notes

Activities:

  1. Fix any open PRs you have that need to have a commit moved to a different branch, etc.

  2. In your github in class repo, create a series of commits that tell as story of how you might have made a mistake and fixed it. Use git log and redirects to write that log to a file in your KWL repo and then annotate your story in gitstory.md.

  3. Create tracking issues for last week’s activities and link them to PRs for any activities you have already completed.

2022-10-05#

related notes

Activities:

  1. Review the notes

  2. For the core “Porcelain” git commands we have used (add, commit), make a table of which git plumbing commands (of those we have seen) they use in gitplumbingreview.md in your KWL repo. it might be multiple Porcelain for each plumbing.

  3. Contribute to your group repo and review a classmate’s contribution

2022-10-12#

related notes

Activities:

  1. review the notes

  2. find 2 more real world examples of using other number systems (either different bases or different symbols and bases) that are current. Describe them in numbers.md

  3. Read about hexpeak from Wikipedia for an overview and one additional source in your kwl repo in hexspeak.md. Come up with a word or two on your own.

  4. Create a single branch for all of the work related to today’s class in your KWL

2022-10-17#

related notes

Activities:

  1. Read the notes and repeat the activity if needed

  2. use git cat-file over the objects to draw a graph diagram of your current status in your test directory include your drawing in test_repo_map.md using mermaid syntax to diagram it. Name each node in your graph with 5-7 characters of the hash and the type. eg 0c913 commit

2022-10-19#

related notes

Activities:

  1. Update your KWL Chart learned column with what you’ve learned

  2. Make a contribution to your group repo and do a peer review of a team member’s PR.

  3. Use the gh cli, grep, and bash to create group_contributions.md to your KWL repo with a list of all of your PRs. Append your history from creating this to the bottom of the file after ## Commands

  4. Move your checker script into your kwl repo and update the paths so that it still works

2022-10-24#

related notes

Activities:

  1. Review the notes

  2. Update your Get Assignments action to use the current date. Once the notes are posted, run it to get today’s tasks.

2022-10-26#

related notes

Activities:

  1. Review the notes (to reinforce ideas and improve your memory of them)

  2. create a bash script that counts the number of lines in each .fastq file, saves the line counts to a text file, then finds how many times Act5C is in dmel-all-r6.19.gtf on the server. (save this on the server; we’ll get it downloaded locally later)

  3. Configure ssh keys to your GitHub account (this is actually GitHub’s preferred terminal authentication method)

  4. Contribute to your group repo and review someone else’s contribution

2022-10-31#

related notes

Activities:

  1. Update more rows on your KWL Chart based on what we did today.

  2. Practice using gcc. Repeat steps we did in class, change the order of parameters; try skipping steps to produce errors, etc. Then in gcctips.md summarize what you learned as a list of tips and reminders on what the parameters do/why/when you would need them (or not). (to reinforce what we learned)

  3. Contribute to your group repo and review a team mate’s PR>

2022-11-02#

related notes

Activities:

  1. Add bitwise.md to your kwl and write the bitwise operations required for the following transformations:

    4 -> 128
12493 - > -12494
127 -> 15
7 -> 56
4 -> -5

  2. For the following figure out the bitwise operator:

    45 (_) 37 = 37
45 (_) 37 = 45
3 (_) 5 = 7
6 (_) 8 = 0
10 (_) 5 = 15

  3. Create readingbytes.md and answer the following:

    1. if a file had the following binary contents, what would it display in the terminal? Describe how you can figure this out manually and check it using C or Python. '01110011011110010111001101110100011001010110110101110011'
1. What is the contents of the `sample.bn` if `cat sample.bn` is: ` ¢¶"*`

  4. Read about integer overflow and in overflow.md describe what it is, use an example assuming an 8 bit system.

2022-11-07#

related notes

Activities:

Write a C program to compare values as doubles and as float (single precision/32bit) to see that this comparison issue is related to the IEEE standard and is not language specific. Make notes and comparison around its behavior and include it in a code cell in cdouble.md

2022-11-14#

related notes

Activities:

Compare the 2 bit multiplier to the full adder in multiplication.md. Use comparison with the full adder to explain how the 2bit multiplier works works, relative to the fact that multiplication can be thought of like repeated addition.

2022-11-16#

related notes

Activities:

  1. Learn about the history of some programming practice or the history of a term (eg why debugging is called debugging) and contribute them to a history.md file in your team repo. Be sure to include your sources and make sure to use a trustworthy source. Review a team mate’s contribution. (see notes for guidance)

2022-11-21#

related notes

Activities:

  1. Review the notes.

  2. Update your KWL chart.

  3. Simulate a more computationally intensive program using the sleep function in C and compare the time of a threaded vs single threaded (ie serial, no intentional threading) version of the program. Include your two programs and the bash script to show how you tested it with notes on the performance in threaded.md (to better illustrate the impact of the threads)

2022-11-28#

related notes

Activities:

  1. Explore the IDE you use most and add frequentide.md to your kwl with notes about which features it does/not have. (to review/reinforce)

  2. Try a new IDE and make some notes about how it was to learn in newide.md What is easy? hard? What could you apply from the ones you already use? Were there features you had trouble finding?

2022-11-30#

related notes

Activities:

  1. For 2 languages from the loved vs dreaded list (one top 5; one bottom 5) read 2-3 posts about why people love/hate that language and summaries the key points on each side. Add this to your kwl repo in language_love_dread.md

2022-12-05#

(counts as 2)
related notes

Activities:

  1. Review the questions from class today and in review.md for any questions that you got wrong, write a solution and explanation for your confusion. If you missed class, write a solution guide for all of the questions in today’s notes.

  2. Update your KWL chart by adding 2-3 rows about topics you learned about that are not listed.

  3. Add a new, up to date overview of how you think about computing overall to your KWL repo. Mark the one you made at the beginning as overview-pre.md and this one as overview-post either with heading or the file name

2022-12-07#

(counts as 2)
related notes

Activities:

  1. Review the questions from today’s class and write a solution guide for any that you got wrong with notes about what confused you in review.md (to make sure you do not leave with misconceptions)

  2. Add conclusion.md to your KWL repo. In the file include 2 sections: summary with an overall description of what you learned and how this course was/not helpful to you (paragraph or bullet form is fine) key points with the top 10 thigns you want to make sure you remember from this class

2022-12-12#

(counts as 3)

related notes

Activities:

Write 15 multiple choice questions that cover topics from at least 5 different class sessions (15 total questions) . Each question should have 4 options, 1 correct and 3 that represent a reasonable, but incorrect idea someone may have. For each option explain why it is/not correct in a way that would help clarify someone’s confusion in final.md