CSE 163

Introduction & Syllabus

�

Suh Young Choi��🎶Listening to: Unwed Sailor�💭Question of the Day: How are you doing today? Add to our Slido!

​

​

Slido code:

3101867

Agenda

• Overview
• What is this class? Who is taking this class?
• Who are we (the people leading this class)?
• Course structure
• Assessments and Grading
• Introduction to course tools
• Course website – stay tuned for this!
• Ed
• Gradescope
• Hypothesis

2

Slido Q&A will be open all class

Overview

What is this class?

​

​

​

​

​

​

Competencies

​

1. More advanced programming concepts than in CSE 122 or CSE 160 including how to write bigger programs with multiple classes and modules.�
2. How to work with different types of data: tabular, text, images, geo-spatial, etc.�
3. Ecosystem of data science tools including Jupyter Notebook and various data science libraries including scikit-image, scikit-learn, and pandas data frames.�
4. Basic concepts related to code complexity, efficiency of different types of data structures, and memory management.

​

• Foundations of data literacy and technical communication for critical and conscientious data science.

3

Overview

Who is taking this class?

This class is designed to have students from

​

• 122: Know control structures, file I/O, arrays in Java
• Will spend first weeks learning 122 in Python fast!
• Practice is KEY!�
• 160: Know control structures, file I/O, data structures in Python
• First week will be review while everyone learns Python�
• 123 or Beyond: Seen more advanced programming in Java
• Class material should be complementary to what you would have learned in 123
• Competency 1 is aimed at the 123 level of programming

4

Poll on Slido!

Who am I?

• Suh Young Choi
• not Suh! ☺
• Fresh UW Grad!
• Office Hours
• Time:
• Friday 1:30 – 3:30pm
• Location: CSE 214
• Or by appointment!
• Contact
• Personal Matters: atobdura@cs.washington.edu
• Course Content + Logistics: Ed

5

Our TAs!

6

Syllabus

7

Bicycles?

8

Having The Talk… ✨��

• We discourage use of Gen AI in CSE 163
• It’s hard to strike a balance that is meaningful and sustainable�
• Can deprive you of real learning opportunities
• We want you to own your craft!�
• Treat it like any other external resource
• If you wouldn’t ask another human being, don’t ask AI!

​

• We value humanity in CSE 163
• Being human is messy but rewarding. ☺

​

9

Lesson Due

10

Current THA Due��

• We don’t record attendance in lecture/section, but attending these sessions is expected
• There are recordings of the class sessions, but the content comes from the lesson.

Lesson Due

​

Weekly Assignment Due

11

4

2

3

1

Pacing

We are releasing the lessons and assessments as we move throughout the quarter

​

As a general note: Interacting compassionately and empathetically is key!

​

Community is built by all of us! We need you to participate in the active classroom environment. This means

• Attend class sessions and quiz sections when you can
• Participate in discussions on Ed Discussion and chat
• Reach out to your peers and the course staff when you need help!

12

Assessments�and Grading

• Our goal in the course is for you to become proficient in the concepts and skills we teach.

​

• We assess your proficiency by asking you to apply concepts and skills on tasks or problems. By necessity, we are assessing your work as a proxy for your proficiency

​

• Your final grade should reflect the extent to which you have demonstrated proficiency of the course objectives

​

​

​

13

Assessments

We will have the following assessments in CSE 163:

• Checkpoints (biweekly)
• Short assignments consisting of a few problems to assess your learning on ~2 weeks of course content.
• Reading Assignments (biweekly)
• Reflect on readings related to course content
• Section Assignments (weekly)
• Structured practice with code and concepts with TAs
• Take-Home Assessments (mostly weekly)
• Longer programming assignments.
• Final Project / Portfolio (parts throughout quarter)
• Create something new that you want to share!

14

Grading

• Checkpoints and Reading Assignments on correctness and completion, respectively
• Take-Home Assessments are graded on correctness for the following dimensions:
• Technical Component
• Behavior
• Concepts
• Quality
• Testing/Writeup
• Creative Component
• Requirements
• Review
• Final Project / Portfolio is graded on completion and correctness of minimum requirements.

​

Course component weights and GPA mapping can be found in syllabus

15

Resubmission

Learning is a challenging process that takes time; it doesn’t always happen on your first try.

• One previous take-home assessment can be resubmitted each week.
• Must be accompanied by write up explaining changes
• Grade on resubmission replaces original grade
• To stay on-track with the course, each take-home assessment can only be resubmitted within two weeks of receiving feedback.
• If you find an unforeseen circumstance that causes you to fall behind on an assignment, please reach out to the course staff sooner than later!

​

16

Resubmission�Example

17

Resubmission�Example

18

Late Work

Late work will generally only be accepted with one of the mechanisms outlined in the syllabus.

• If you can’t finish a take-home assessment by the initial submission date, you will need to use a resubmission in a future week to turn it in.
• Checkpoints and reading assignments are generally not accepted late unless you have sufficient Weekly Tokens.

​

Weekly Tokens: A single token lets you turn in 1 checkpoint or 1 reading assignment late at any point in the quarter before the Friday of finals week.

• Every student will start with 1 Weekly Token
• Every 6 Lessons you complete on-time (by 11:59 pm the day of the Lesson), get converted to a Weekly Token.
• Includes two free Lesson completions for the�MLK Day and Presidents’ Day holidays

​

​

19

Collaboration Policy

• Form study groups (you can use Ed/Canvas chat for this)! You are encouraged to discuss assessments and concepts at a high level
• If you have code in front of you in your discussion or showing each other solutions, probably NOT high level
• If you discuss your ideas with others, you must cite them
• All code and answers submitted must be your own
• Any work found to not be your own will receive a grade of a 0 and may not be resubmitted
• If it’s not your work, we can’t assess your mastery

​

Final project can be done in groups of up to 3 (not more!)

Portfolios are individual work

20

Amnesty

Sometimes, we make bad choices that we regret

​

“If you submit work that is in violation of the academic conduct policy, you bring the action to Suh Young’s attention within 72 hours of submission and request amnesty. If you do so, you will receive a grade of 0 for the initial submission, but you will be allowed to resubmit your work under the normal resubmission process.”

21

Project

• Culmination of all the things you learned in this class.�
• Open ended project where you find and use real-world datasets to answer an interesting question. Encouraged to work in groups with 1 or 2 other students!

​

• Broken into various checkpoints throughout quarter:
• Pick a research question and your datasets + �find a partner(s)
• Give preliminary findings about the data
• Gather results and write final report
• Final Project presentations will happen during the last section of the quarter

22

Portfolio

• Reflection and revision for the creative work you have done in class

​

• Polish your creative work from the quarter and give us your best showcase. This is a solo work!

​

• Broken into various checkpoints throughout quarter:
• Vision statement describing your work at a high level
• Milestone “preview” of your final portfolio
• Finish your revisions and make your code presentation-ready
• Portfolio presentations will happen during the last section of the quarter

23

Technology�Resources

• Course website: https://courses.cs.washington.edu/courses/cse163/26wi/
• Everything you need is linked from here!
• Check the calendar for all links for that day
• Ed: https://edstem.org/us/courses/90028/discussion
• For discussion board and announcements
• Canvas for gradebook, assignment tracking, reading assignments

​

VS Code setup guide can be found in Software page of the Course Website

​

More to come, but we will introduce them as necessary

24

Before Next Time

• Get started on RA 1
• Introduce yourself on Ed!
• Complete Lesson 1 on the course website
• Read lesson slides. Stop after completing “Pause and Think”
• Encouraged to save problems for class session!
• Due for EC @ 11:59 pm Wed 1/7

​

Next Time

• Intro to Python
• How to write a program
• Loops
• Conditionals
• Functions, parameters, returns

25

Questions?

26