-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0d71934
commit afe384b
Showing
45 changed files
with
1,255 additions
and
48 deletions.
There are no files selected for viewing
Binary file removed
BIN
-41.6 KB
_images/35812509b63106e40df9ed2934b4c3a91019b4f0dec5e959e2dc3a436cf4465b.png
Binary file not shown.
Binary file added
BIN
+41.3 KB
_images/73e69eff6f09db590d8ccf79418cf7519fe5988a585269fa5da34744abe5206e.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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,187 @@ | ||
|
||
+++{"lesson_part": "main"} | ||
# More orientation | ||
|
||
Today we will: | ||
- continue getting familiar with the structure of GitHub | ||
- clarify more how the course will flow | ||
- practice with new vocabulary | ||
|
||
*Last class was a lot of new information, today we will reinforce that mostly, and add only a little* | ||
|
||
## Warm up | ||
|
||
1. Navigate to your KWL repo | ||
2. Find the issues tab | ||
3. Open the prepare-2024-09-10 issue and discuss the questions with your classmates at your table | ||
|
||
*hint: my KWL repo URL is: `https://github.com/compsys-progtools/fall24-brownsarahm` | ||
|
||
Becoming an expert requires: | ||
- different types of study | ||
- pracitce and feedback to get better | ||
|
||
|
||
|
||
## Making up for action issue last week | ||
|
||
To activate the workflows in your repo, edit them, even adding a space or deleting a blank line will make it work. | ||
|
||
````{margin} | ||
```{note} | ||
[where I found this workaround](https://github.com/orgs/community/discussions/127455#discussioncomment-9741103) | ||
``` | ||
```` | ||
|
||
We fixed the `forgottenexperience.yml` file and then [ran it manually](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow). | ||
|
||
Then we edited the file it created to add a title on the line with one `#` (should be line 10) uisn ghte 3 dots menue in the top right of the file on the `files changed` tab of the PR. | ||
|
||
|
||
```{note} | ||
When you add more commits to a branch that has a PR, it automatically updates the PR. | ||
``` | ||
|
||
|
||
note, here we are learning *by example* and then *synthesizing* that into more concrete facts. | ||
|
||
+++{"lesson_part": "main"} | ||
|
||
"just play with it" | ||
|
||
- common attitude in CS | ||
- not optimal for learning | ||
+++{"lesson_part": "main"} | ||
**my goal is to teach you to get better at learning in that way, bc it is what employers will expect** | ||
|
||
To do this: | ||
- set up opportunities for you to *do* the things that give you the opportunity | ||
- highlight important facts about what just happened | ||
- ask you questions to examine what just happened | ||
+++{"lesson_part": "main"} | ||
|
||
This is why attendance/participation is a big part of your grade. | ||
|
||
Experience badges are evidence of having learned. | ||
|
||
|
||
+++{"lesson_part": "main"} | ||
|
||
### My focus is for you to learn | ||
|
||
|
||
- that means, practice, feedback, and reflection | ||
- you should know that you have learned | ||
- you should be able to apply this material in other courses | ||
|
||
+++{"lesson_part": "main"} | ||
|
||
### Learning comes in many forms | ||
|
||
- different types of material are best remembered in different ways | ||
- some things are hard to explain, but watching it is very concrete | ||
|
||
+++{"lesson_part": "main"} | ||
|
||
## Learning is the goal | ||
|
||
- producing outputs as fast as possible is not learning | ||
- in a job, you may get paid to do things fast | ||
- your work also needs to be correct, without someone telling you it is | ||
- in a job you are trusted to know your work is correct, your boss does not check your work or grade you | ||
- to get a job, you have to interview, which means explaining, in words, to another person how to do something | ||
|
||
|
||
+++{"lesson_part": "main"} | ||
|
||
## What about AI? | ||
|
||
Large Language Models will change what programming looks like, but understanding is always going to be more effective than asking an AI. Large language models actually do not know anything, they just know what languages loook like and generate text. | ||
|
||
|
||
*if you cannot tell it when it's wrong, you do not add value for a company, so why would they pay you?* | ||
|
||
+++{"lesson_part": "main"} | ||
|
||
## This is a college course | ||
|
||
- more than getting you one job, a bootcamp gets you one job | ||
- build a long (or maybe short, but fruitful) career | ||
- build critical thinking skill that makes you adaptable | ||
- have options | ||
|
||
+++{"lesson_part": "main"} | ||
## How does this work? | ||
|
||
### In class: | ||
|
||
1. Memory/ understanding checks | ||
1. Review/ clarification as needed | ||
1. New topic demo with follow along, tiny practice | ||
1. Review, submit questions | ||
|
||
|
||
### Outside of class: | ||
|
||
|
||
1. Read notes to refresh the material, check your understanding, and find more details | ||
1. Practice material that has been taught | ||
1. Activate your memory of related things to what we will cover to prepare | ||
1. Read articles/ watch videos to either fill in gaps or learn more details | ||
1. Bring questions to class | ||
|
||
+++{"lesson_part": "main"} | ||
|
||
I give a [time breakdown](https://compsys-progtools.github.io/spring2024/syllabus/schedule.html#recommended-workload-distribution) in the syllabus. | ||
|
||
|
||
## Prepare for next class | ||
|
||
```{include} ../_prepare/2024-09-12.md | ||
``` | ||
|
||
## Badges | ||
|
||
`````{tab-set} | ||
````{tab-item} Review | ||
```{include} ../_review/2024-09-10.md | ||
``` | ||
```` | ||
````{tab-item} Practice | ||
```{include} ../_practice/2024-09-10.md | ||
``` | ||
```` | ||
````` | ||
|
||
## Questions After Class | ||
|
||
### How can I create my own actions to run that will create issues and pull requests? | ||
|
||
We will learn this a bit later, but you can read ahead in the [docs](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions). | ||
|
||
### What is the purpose of the wiki within GitHub? | ||
|
||
To serve as documentation, wiki-style for the repo. It was more common before github added pages. A lot of open source projects now host documentation using github pages. We will learn how this works later, but this website uses pages. | ||
|
||
### Do we merge the pull request for the experience report into main? | ||
|
||
Only when approved (but if you forget, @ me and I can fix it) | ||
|
||
### Just still how to better navigate github because while I understood most of it was still confusing at points | ||
|
||
We will be doing all of these things over and over, so you will get them, it's okay! | ||
|
||
### Is it possible to rename a committed change? | ||
|
||
You can change a commit message, yes! | ||
|
||
### How do we access the old file after we already commit changes? | ||
|
||
On GitHub.com, you go to the commits on the repo (click the {fa}`fa-clock-rotate-left` icon or add `/commits` to the repo's URL) and then choose view at that point. | ||
|
||
### How can we edit our github using the terminal? | ||
|
||
Next class! | ||
|
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
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
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
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
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
Binary file not shown.
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
Oops, something went wrong.