Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Review Badges

Review badges will help you to reinforce what we do in class and guide you to practice with the most essential skills of this class, they represent the minimum bar for C level work. This includes reviewing prismia chat to see any questions you got wrong and reading the notes.

2025-09-04

related notes

Activities:

  1. make sure you have joined the team to get access to more features in our course organization.

  2. Review the notes from today’s class carefully

  3. Fill in the first two columns of your KWL chart (content of the PR; named to match the badge name)

  4. Post an introduction to your classmates on our discussion forum (include link to your comment in PR comment, must accept above to see)

2025-09-09

related notes

Activities:

the text in () below is why each step is assigned

  1. review today’s notes after they are posted, both rendered and the raw markdown versions. Include links to both views in your badge PR comment. (to review)

  2. “Watch” the course website repo, specifically watch Releases under custom (to get notifications)

  3. 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 in a file called prior-knowledge-map. (optional) try mapping out using mermaid syntax, we’ll be using other tools that will faciltate rendering later (what we will learn will connect a lot of ideas, mapping out where you start, sets you up for success)

2025-09-11

related notes

Activities:

Any steps in a badge marked lab are steps that we are going to focus in on during the next lab time. Remember the goal of lab is to help you complete the work, not add additional work. The lab checkout will include some other tasks and then we will encourage you to work on this badge while we are there to help. Lab checkouts are checked only for completion though, not correctness, so steps of activities that we want you to really think about and revise if incorrect will be in a practice or review badge.

  1. Read the notes. If you have any questions, post an issue on the course website repo.

  2. Using your terminal, download your KWL repo. Include the command(s) used in your badge PR.

  3. Try using setting up git using your favorite IDE or GitHub Desktop. Make a file gitoffline.md in your kwl repo and include some notes of how it went. Was it hard? easy? what did you figure out or get stuck on? Is the terminology consistent or does it use different terms?

  4. lab Explore the difference between git add and git commit: try committing and pushing without adding, then add and push without committing. Describe what happens in each case in a file called gitcommit.md. Compare what happens based on what you can see on GitHub and what you can see with git status.

2025-09-16

related notes

Activities:

  1. Create a merge conflict in your KWL repo on the branch for this badge and resolve it using your favorite IDE. Describe how you created it, show the files, and describe how your IDE helps or does not help in ide_merge_conflict.md. Give advice for when you think someone should resolve a merge conflict manually vs using an IDE. (if you do not regulary use an, IDE, try VSCode) You can put content in the file for this step for the purpose of making the merge conflicts for this exercise.

  2. Read more details about git branches(you can also use other resources) add branches.md to your KWL repo and describe how branches work, in your own words. Include one question you have about branches or one scenario you think they could help you with.

2025-09-18

related notes

Activities:

badge steps marked lab are steps that you will be encouraged to use lab time to work on. In this case, in lab, we will check that you know what to do, but if we want you to do revisions those will be done through the badge.

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

  2. Clone the course website. Append the commands used and the contents of your fall2025/.git/configto a file in your KWL called terminal_review.md (hint: history outputs recent commands and redirects can work with any command, not only echo). Edit the README.md in the course website (you can add anything), commit, and try to push the changes. Describe what the error means and which GitHub Collaboration Feature you think would enable you to push? (answer in the terminal_review.md)

fork is the answer, must be one of the things higlighted in the link

  1. lab Organize the provided messy folder in a Codepsace (details will be provided in lab time). Commit and push the changes. Answer the questions below in your kwl repo in a file called terminal_organization.md

  2. clone your messy_repo locally and append the history.md file to your terminal_organization.md

2025-09-23

related notes

Activities:

  1. Export your git log for your KWL main branch to a file called gitlog.txt and commit that as exported to the branch for this issue. note that you will need to work between two branchse to make this happen. Append a blank line, ## Commands, and another blank line to the file, then the command history used for this exercise to the end of the file.

  2. In commit-def.md compare two of the four ways we described a commit today in class. How do the two descriptions differ? How does defining it in different ways help add up to improve your understanding?

  3. Find the detailed view of the commit that added today’s notes to the website in github.com and locally. In commit-detail.md include the url to the commit in github and the contents of the commit object with some notes on any differences (if any).

2025-09-30

related notes

Activities:

  1. Review the notes from today

  2. Read about different workflows in git and describe which one you prefer to work with and why in favorite_git_workflow.md in your kwl repo. Two good places to read from are Git Book and the atlassian Docs

  3. Update your kwl chart with what you have learned or new questions in the want to know column

  4. In commit_contents.md, redirect the content of your most recent commit to your kwl repo, its tree, and the contents of one blob. Edit the file or use echo to put markdown headings between the different objects. Add a title # Complete Commit to the file and at the bottom of the file add ## Reflection subheading with some notes on how, if at all this excercise helps you understand how git works.

2025-09-30

related notes

Activities:

  1. Review the notes from today

  2. Read about different workflows in git and describe which one you prefer to work with and why in favorite_git_workflow.md in your kwl repo. Two good places to read from are Git Book and the atlassian Docs

  3. Update your kwl chart with what you have learned or new questions in the want to know column

  4. In commit_contents.md, redirect the content of your most recent commit to your kwl repo, its tree, and the contents of one blob. Edit the file or use echo to put markdown headings between the different objects. Add a title # Complete Commit to the file and at the bottom of the file add ## Reflection subheading with some notes on how, if at all this excercise helps you understand how git works.

2025-10-02

related notes

Activities:

2025-10-07

related notes

Activities:

  1. Review the notes from today

  2. Make a table in gitplumbingreview.md in your KWL repo that relates the two types of git commands we have seen: plumbing and porcelain. The table should have two columns, one for each type of command (plubming and porcelain). Each row should have one git porcelain command and at least one of the corresponding git plumbing command(s). Include two rows: add and commit.

2025-10-09

related notes

Activities:

  1. Review the notes from today

  2. Create tagtypeexplore.md with the template below. Determine how many of the tags in the course website are annotated vs lightweight using. (You may need to use git pull --tags in your clone of the course website)

# Tags

<!-- short defintion/description in your own words of what a tag is and what it is for -->


## Inspecting tags

Course website tags by type: 
- annoted:
- lightweight: 

2025-10-14

related notes

Activities:

  1. Review the notes from today

  2. Analyze the xor hashing algorithm in the notes to determine which properties of a cryptographic hash are/not met. Include your analysis in xorhash.md

  3. find 2 more real world examples of using other number systems (either different bases or different symbols and bases) not mentioned in class that are currently used. Describe the number system and its usage in numbers.md. Include links to your sources and be sure that the sources are trustworthy.

  4. Calculate the maximum number of git objects that a repo can have without requiring you to use more than the minimum number of characters to refer to any object and include that number in gitcounts.md with a title # Git counts. How many commits would you be able to make before you have to use more than the minimum number of characters to refer to any git object if each commit added a new folder with 1021 files in it? If you get stuck, outline what you know and then request a review.

2025-10-16

related notes

Activities:

  1. Review the notes from today

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

  3. write a bash script to make it so that cating the the files in your gh_inclass repo does not make the prompt move

2025-10-21

related notes

Activities:

  1. Review the notes from today

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

2025-10-23

related notes

Activities:

  1. Review the notes from today

  2. Answer the following in hpc.md of your KWL repo: (to think about how the design of the system we used in class impacts programming and connect it to other ideas taught in CS)

    1. What kinds of things would your code need to do if you were going to run it on an HPC system? 
    1. What sbatch options seem the most helpful?
    1. How might you go about setting the time limits for a script? How could you estimate how long a script will take?

2025-10-28

related notes

Activities:

  1. Review the notes from today

  2. Read through this rsa encryption demo site to review how it works. Find 2 other encyrption algorithms that could be used with ssh (hint: try man ssh or read it online) and compare them in encyryption_compare. Your comparison should be enough to advise someone which is best and why, but need not get into the details.

  3. File permissions are represented numerically often in octal, by transforming the permissions for each level (owner, group, all) as binary into a number. Add octal.md to your KWL repo and answer the following. Try to think through it on your own, but you may look up the answers, as long as you link to (or ideally cite using jupyterbook citations) a high quality source.

    1. Describe how to transform the permissions [`r--`, `rw-`, `rwx`] to octal, by treating each set as three bits.
    1. Transform the permission we changed our script to `rwxr-xr-x` to octal.
    1. Which of the following would prevent a file from being edited by other people 777 or 755 and why?

2025-10-30

related notes

Activities:

  1. Review the notes from today

  2. Create some variations of the hello.c we made in class. Make hello2.c print twice with 2 print commands. Make hello5.c print 5 times with a for loop and hello7.c print 7 times with a for loop. Build them all on the command line and make sure they run correctly.

  3. Write a bash script, assembly.sh to compile each program to assembly and print the number of lines in each file.

  4. Put the output of your script in hello_assembly_compare.md. Add to the file some notes on how they are similar or different based on your own reading of them.

2025-11-04

related notes

Activities:

  1. Review the notes from today

  2. Run and examine how rect.hack and max.hack in the projects/05/ folder of the CPU Emulator work. Make notes and answer the questions below in assemblyexplore.md.

    1. Write an excerpt of code in a high level compiled language that would compile into this `max.hack``.
    1. What does rect.hack do?
    1. What did you learn trying to figure out how it works?

2025-11-06

related notes

Activities:

  1. Review the notes from today

  2. While we saw many types of gates today, but we actually could get all of the operations needed using only NAND gates. Work out how to use NAND gates to implement and and or in nandandor.md

  3. Find what bitwise operation would complete each of these transformations (eg 1 << 3 = 4 and 4^4 = 0) that is replace the ? with a bitwise operator. For each show work to explain how you found it in bitwise.md:

    4 ? 3 = 32
    11 ? 7 = 3
    8 ? 2 = 2

2025-11-18

related notes

Activities:

  1. Review the notes from today

  2. Update your KWL chart.

  3. If you were to use something from this course in an internship for an interview, what story could you tell?

  4. Use time to compare using a bash loop to do the same operation on every file in a folder vs using the wildcard operator and sending the list of files to command. In loop_v_list.md include your code exerpts, the results and hypothesize why the faster one is faster.

2025-11-18

related notes

Activities:

  1. Review the notes from today

  2. Update your KWL chart.

  3. If you were to use something from this course in an internship for an interview, what story could you tell?

  4. Use time to compare using a bash loop to do the same operation on every file in a folder vs using the wildcard operator and sending the list of files to command. In loop_v_list.md include your code exerpts, the results and hypothesize why the faster one is faster.

2025-11-20

related notes

Activities:

  1. Review the notes from today

  2. Examine the assembly for the sq_sum_threaded.c we wrote in class and find the lines that show why the race condition occurs. Describe how you figured it out and include the relevant lines in race.md.

2025-11-25

related notes

Activities:

  1. Review the notes from today

  2. Choose two languages from the desired admired list. THis could be a highly admired and least desired; it could be one with a small gap and one with a large gap. Read a few posts about each language and try to figure out why it is/not admired or desired. Summarize your findings. Include links to all of the posts you read in a section titled ## Sources in your markdown file. For each source, make a bulleted list with some notes about the author’s background and any limitations that might put on the scope of their opinions. (for example, a data scientists’s opinion on languages is very valuable for data science, but less for app development) Add this to your kwl repo in language_love_dread.md.

2025-12-02

related notes

Activities:

  1. Review the notes from today

  2. Try a new IDE and review it in newide.md. Your review should be 3 secictions: Summary, Evaluation, and Reflection. Summary should be 1-3 sentences of your conclusions. Evaluation should be a detailed evaluation according to your group’s criteria and one other group’s criteria. In Reflection, reflect on your experience: What is easy? hard? What could you apply from the ones you already use? Were there features you had trouble finding?