class: title # Introduction ## CSC 161 – January 20, 2026 --- # Agenda for Today 1. Introductions 2. Course Information 3. Upcoming Work 4. Discussion 5. Lab 6. Wrap Up --- class: section blue # Introductions --- # Hello... 1. My name is .blank[]. 2. I would like to be called .blank[]. 3. I use the pronouns .blank[]. .light[(they/them, she/her, he/him, ...)] --- class: section, blue # Course Information --- # Basic Information ## Course Website <https://curtsinger.cs.grinnell.edu/teaching/2026S/CSC161/> ## Textbook Beej's Guide to C Programming (online only) ## Class Mentors - Reo Saito (morning) - Nicole Moreno Gonzales (afternoon) --- class: section, gray # Class Website Tour --- class: section, blue # Upcoming Work --- # Week 1 Quiz We'll have our first quiz at the start of class on Thursday. The quiz will last 10 minutes, and could cover any of these topics: 1. The C Development Environment (excluding `git`) 2. Course Policies (from the syllabus) 3. Variables 4. Expressions 5. Statements In general, you should expect weekly quizzes to include at least one question from the reading assigned for that day. --- class: section, blue # Discussion --- # Discussion Format We'll follow a ***think, pair, share*** model for discussions in this class. I will ask questions, usually on a slide. For each question, you should: -- 1. Think about the question yourself and try to come up with an answer. -- 2. Discuss your idea with at least one other student and try to reach some agreement. -- 3. Be prepared to share your thoughts when I call on you. -- I will let you know when to move on from each step. Please don't shout out answers, and make sure you're working respectfully with your partners. --- # Discussion: Pair Programming **Questions for think, pair, share:** -- 1. What are the names of the two roles in pair programming? -- 2. One of the members of a pair programming group does the typing. What are some of their other responsibilities? -- 3. What is one benefit to pair programming? -- 4. What is one thing that makes pair programming challenging? -- *Start by thinking of answers on your own. I will let you know when to start discussion.* --- # Discussion: Course Policies **Questions for think, pair, share:** -- 1. What are the different types of work you will do for this course? -- 2. What should you do if you need to miss class? -- 3. Are you allowed to use AI tools for work in this class? -- 4. What do you think the justification is for the AI policy in this course? -- *Start by thinking of answers on your own. I will let you know when to start discussion.* --- # Discussion: C Development Environment **Questions for think, pair, share:** -- 1. What is the name of the program that converts C source code into a runnable program? -- 2. What `git` command makes a copy of a remote repository on your computer? -- 3. What is one other `git` command you read about, and what does it do? -- 4. Why do you think developers use version control systems like `git`? -- *Start by thinking of answers on your own. I will let you know when to start discussion.* --- # Discussion: C Programming Language **Questions for think, pair, share:** -- 1. When and where was the C programming language developed? -- 2. What does it mean for C to be a "low-level" language? -- 3. What are some differences between C and the language you used in CSC 151? Try to come up with at least three. -- 4. What is one thing you're nervous about learning to do in C? This can be from the reading or something you've heard about the course. -- *Start by thinking of answers on your own. I will let you know when to start discussion.* --- # Questions Do you have any questions about the reading before we start our lab? --- class: section, blue # Lab --- # Lab: Tips Here are a few tips for lab time: 1. Introduce yourself to your lab partner(s). 2. Remember to take turns driving and navigating. 3. Take notes as you complete lab exercises so you can easily prepare your weekly lab report (more details later). --- class: section, blue # Wrap Up --- # Reminders -- ## Lab Work You do not need to submit any work from today's lab. Going forward, you will submit lab work in weekly lab reports due each Tuesday. -- ## Reading - **Variables** (Beej's Guide to C Programming, Section 3.1) - **Operators and Expressions** (Beej's Guide to C Programming, Section 3.2) -- ## Quiz There will be a quiz at the start of class on Thursday. The quiz can cover material from today's reading, class discussion, and lab, as well as any concepts from the reading for Thursday (including the syllabus).