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+++
*hint: my KWL repo URL is: https://github.com/compsys-progtools/fall25-kwl-brownsarahm
How will we learn¶
“just play with it”
common attitude in CS
not optimal for learning
my goal is to teach you to get better at learning in that way, because it is what employers will expect you to be able to do
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
This is why attendance/participation is a big part of your grade.
Experience badges are evidence of having learned
Programming is Collaborative¶
There are two very common types of collaboration:
code review (working independently and then reviewing)
pair programming (sitting together and discussing while writing)
We are going to build your skill in the code review model. This means you need to collaborate, but collaboration in school tends to be more stressful than it needs to. If students have different goals or motivation levels it can create conflict. So there will be some chances for collaboration where people can show up at the level they want without impacting others.
You can also do build badges collaboratively, for a closer collaboration, but those are your choice.
GitHub Actions Tab¶
GitHub allows us to run scripts within our repos, the feature is called GitHub Actions and the individual items are called workflows.
Prepare for Next Class¶
Choose where on your local computer you will save work for this class and make note of that for yourself
Think about how files are organized in your computer. You do not need to go learn or read about this, but spend a few minutes thinking about what you know about this or how you interact with it.
Badges¶
the text in () below is why each step is assigned
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)
“Watch” the course website repo, specifically watch Releases under custom (to get notifications)
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)
the text in () below is why each step is assigned
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)
“Watch” the course website repo, specifically watch Releases under custom (to get notifications)
read Chapter 1, “Decoding your confusion while coding” in The Programmer’s Brain add a file called brain.md to your kwl repo that summarizes your thoughts on the chapter. Do you think this information will help you approach learning more effectively? why or why not? How, if at all, does it changes how you think about debugging and learning to program? Give examples of how you have encountered the different types of confusion in your prior programming experiences. (to help you get good strategies and prime for things we will see in the next few weeks)
map out your computing knowledge and add it to your kwl chart repo in a file called prior-knowledge-map.md. Use mermaid syntax, to draw your map. GitHub can render it for you including while you work using the preview button. (what we will learn will connect a lot of ideas, mapping out where you start, sets you up for success)
Read more about version control in general and add a “version control” row to your KWL chart with all 3 columns filled in. (git is version control, but not the only one)
Experience Report Evidence¶
You should have the about PR open and request a review from @brownsarahm