Prepare for the next class#

These tasks are not always based on things that we have already done. Sometimes they are to have you start thinking about the topic that we are about to cover. Getting whatever you know about the topic fresh in your mind in advance of class will help what we do in class stick for you when we start.

The correct answer is not as important for these activities as it is to do them before class. We will build on these in class. These are evaluated on completion only, but we may ask you questions or leave comments if appropriate, in that event you should reply and then we’ll approve.

2023-09-12#

Activities:

  1. (for lab) Read the syllabus section of the course website carefully and explore the whole course website

  2. Bring questions about the course to lab

  3. (for class) Think about one thing you’ve learned really well (computing or not). Be prepared to discuss the following: How do you know that you know it? What was it llike to first learn it?

2023-09-14#

Activities:

  1. Find the glossary page for the course website, link it below. Review the terms for the next class: shell, terminal, bash, git, GitHub.

  2. Check your kwl repo before class and see if you have recieved feedback, reply or merge accordingly.

  3. Make sure you have a working environment, see the list in the syllabus, including gh CLI if you use mac`. Use the discussions to ask for help.

  4. Sign up for announcements

2023-09-19#

Activities:

  1. Reply below with any questions you have about using terminals so that you can bring it up in class

  2. Be prepared to compare and contrast bash, shell, terminal, and git.

  3. (optional) If you like to read about things before you do them, read about merge conflicts. If you prefer to see them first, read this after.

2023-09-21#

Activities:

  1. Read the notes from 2023-09-19 carefully

  2. Examine an open source project on GitHub. Answer the reflection questions below in software.md in your kwl repo on a branch that is linked to this issue. You do not need to make the PR, we will work with this in class on 2023-09-21.

## Software Reflection

1. Link and title of the project
1. What types of files are there that are not code?
1. What different types of code files are in the project? Do they serve different goals?
1. Is it all in one language or are there multiple languages?
1. Are there files that are configurations or settings?
1. Is there help for developers? users? which support is better?
1. What type of things are in the hidden files? who would need to see those files vs not?

Some open source projects if you do not have one in mind:

2023-09-26#

Activities:

  1. Review your software.md file from last prepare

  2. Review the notes from 2023-09-21

  3. Bring git questions or scenarios you want to be able to solve to class on Thursday (in your mind or comment here if that helps you remember)

  4. Update your .github/workflows/experienceinclass.yml file as to add another paramter to the last step (Create Pull request) reviewers: <ta-gh-name> where <ta-gh-name> is the github user name of the TA is in your group. You can see your group on the organiation teams page named like “Fall 2023 Group X”. Do this on a branch for this issue.

2023-09-28#

Activities:

  1. Read the 2023-09-26 notes when posted

  2. Make sure that the gh CLI tool works by using it to create an issue called test on your kwl repo with gh issue create

  3. Take a few minutes to think about a time you were debugging or pay attention the next time you debug something. Make note of how you think about the problem, how do you decide what to check? how do you decide what to try? what information do you look for?

2023-10-03#

Activities:

  1. Follow up on your grade plan PR and self reflection that you complete in lab

2023-10-05#

Activities:

  1. Review the notes from past classes

  2. Think through and make some notes about what you have learned about design so far. Try to answer the questions below in design_before.md. If you do not now know how to answer any of the questions, write in what questions you have.

- What past experiences with making decisions about or studying design do you have? 
- What processes, decisions, and practices come to mind when you think about designing software?
- From your experiences as a user you would describe the design of command line tools vs other GUI based tools?

2023-10-12#

Activities:

note this is posted on 2023-10-05 because October 10th is a “Monday” for URI classes

  1. Read the notes from October 5 and October 3. We will build on both of them on October 12. Make sure you have completed all of the steps in the github inclass repo from September too.

  2. Start recording notes on how you use IDEs for the next couple of weeks using the template file below. We will come back to these notes in class later, but it is best to record over a time period instead of trying to remember at that time. Store your notes in your kwl repo in idethoughts.md on an ide_prep branch. This is prep for much later, it does not go in the October 12 experience branch

2023-10-17#

Activities:

  1. Read the notes from October 12. We will build on these directly in the future. You need to have the test repo with the same status for lab on 10/13 and class on 10/17 Make sure you have completed all of the steps in the github inclass repo from September too.

  2. Start recording notes on how you use IDEs for the next couple of weeks using the template file below. We will come back to these notes in class later, but it is best to record over a time period instead of trying to remember at that time. Record which IDE(s) you use, what tasks you do, what features you use, what extensions, etc. Store your notes in your kwl repo in idethoughts.md on an ide_prep branch. This is prep for much later, it does not go in the October 17 experience badge branch

2023-10-19#

Activities:

  1. Review the course website releases to get familiar with what content appears there

  2. Review the GitHub Action files in your KWL repo and make note of what if any syntax in there is unfamilar. (note that link may not work on the rendered website, but will work on issues)

  3. Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.

  4. Use git log to view recent updates to the course website from the October 12 class to the October 17 class release

  5. review the open PR about a build badge if you are intersted in that option and comment if anything is unclear or approve if it is helpful.

2023-10-24#

Activities:

  1. If you have not already or right before class, review the GitHub Action files in your KWL repo and make note of what if any syntax in there is unfamilar. (note that link may not work on the rendered website, but will work on issues)

  2. Use quote reply or edit to see how I made a relative path to a location within the repo in this issue.

  3. Check out the github action marketplace to see other actions that are available and try to get a casual level of understanding of the types of things that people use actions for.

2023-10-26#

Activities:

  1. Read the 3 bulleted examples of why use a cluster from HPC carpentry.

  2. Read this discussion of why using a remote server

2023-10-31#

Activities:

  1. Read about connection protocols in general and specifically https and ssh. Wikipedia is a good source to start from,and use additional sources to verify anything you find confusing. Be sure you have the basic terminology down and bring questions to class. Plan to check off your questions as they are answered during class on Tuesady and then submit others in your experience reflection.

2023-11-02#

Activities:

No separate preparation, focus on badge work and reviewing the notes if you missed class.

Make sure you did the prep for 10-31, we will work from that on 11/2.

2023-11-02#

related notes

Activities:

No separate preparation, focus on badge work and reviewing the notes if you missed class.

Make sure you did the prep for 10-31, we will work from that on 11/2.

2023-11-07#

related notes

Activities:

  1. Create operators.md and make some notes about what you know about operators. What kinds of operators are you familiar with? Which have you seen in programming? math?

  2. Look over build/explore ideas if you plan to do any.

2023-11-14#

related notes

Activities:

Review the prep from 2023-11-07 or do it if you have not.

2023-11-16#

related notes

Activities:

  1. Refresh your knowledge of logical operations/ logic gates: and, or, xor, not. For an example reference see the logicemu emulator we will use in class

2023-11-21#

related notes

Activities:

  1. In fractionalbinary.md use 8 bits to represent the following numbers by using 4 bits as usual (8,2,4,1) and the other 4 bits are 1/2, 1/4, 1/8, 1/16th:

  • 3.75

  • 7.5

  • 11.625

  • 5.1875

  1. Add to your file some notes about the limitations of representing non integer values this way. How much would using more bits help with, what limitations are not resolved by adding more bits. For example, how could you represent .1?

2023-11-28#

related notes

Activities:

none

2023-11-30#

related notes

Activities:

Spend a few minutes thinking about what you know about memory and reading and writing files in programming. Make some notes about it (that you do not need to submit). (you’ll discuss this with classmates at the start of class)

2023-12-05#

related notes

Activities:

None.

2023-12-07#

related notes

Activities:

  1. Preview the Stack Overflow Developer Survey Technology section parts that are about tools. Create dev_insights.md with 3-5 bullet points for discussion. These can be facts you found most interesting or questions you have based on the results (it can be clarifying or deeper questions)