CSE 20289 is a core Computer Science and Engineering course at the University of Notre Dame that explores the fundamentals of computing systems. This course introduces students to the Unix programming environment where they will explore various command line utilities, files, processes, memory management, system calls, data structures, networking, and concurrency. Examining these topics will enable students to become familiar and comfortable with the lower level aspects of computing, while providing the foundation for further study in subsequent systems courses such as computer architecture and operating systems.
Upon successful completion of this course, students will be able to:
Utilize commands to navigate filesystems, manipulate files, manage processes, and explore system and network resources.
Compose shell scripts that combine common Unix commands with shell syntax to automate tasks.
Construct regular expressions and software pipelines to filter and process a variety of datasets.
Employ development tools to debug, profile, and test software applications.
Build and install software from source distributions or using package managers.
Compose Python scripts that employ data structures and libraries to process and manipulate data.
Construct C programs that use low-level functions or system calls to allocate memory, manipulate files and directories, and communicate over sockets.
Discuss the core tenets of the "Unix Philosophy" and how it is applied to modern software development.
Online office hours for the teaching assistants will take place in Zoom Meeting 916 0683 5006. Please use the main session for general questions. If you have an individual question, then request a private breakout room with one of the teaching assistants.
If you need more individualized attention, please contact the instructor to schedule an appointment.
|Introduction||Wed 01/18||Syllabus, Unix Shell Slides 00 Slides 01 Panopto|
|Fri 01/20||Git Slides 02 Panopto||Reading 00|
|Unit 01: Bourne Shell|
|Using the Shell||Mon 01/23||Files Slides 03 Panopto||Reading 01|
|Wed 01/25||Processes, I/O Redirection Slides 04 Slides 05 Panopto|
|Fri 01/27||Networking Slides 06 Panopto|
|Sat 01/28||Command Line Adventure||Homework 01|
|Shell Scripting||Mon 01/30||Variables, Command Substitution, Matching Slides 07 Panopto||Reading 02|
|Wed 02/01||Control Flow, Command Line Arguments Slides 07 Panopto|
|Fri 02/03||Pipelines Slides 08 Panopto|
|Sat 02/04||Meeting the Oracle||Homework 02|
|Text Filtering||Mon 02/06||Regular Expressions Slides 08 Panopto||Reading 03|
|Wed 02/08||Filters Slides 08 Panopto|
|Fri 02/10||Filters Slides 08 Panopto|
|Sat 02/11||Weathering with Zipcodes||Homework 03|
|Exam 01||Mon 02/13||Slides R1 Panopto Checklist 01||Reading 04|
|Wed 02/15||Exam 01|
|Fri 02/17||Python Scripting Slides 09 Panopto|
|Unit 02: Python|
|Python Scripting||Mon 02/20||Functions, Doctests, Lists Slides 09 Panopto||Reading 05|
|Wed 02/22||Strings, Dictionaries Slides 09 Panopto|
|Fri 02/24||I/O, Processes, Requests, Regular Expressions Slides 09 Panopto|
|Sat 02/25||RPN, Unique||Homework 04|
|Data Processing||Mon 02/27||CSV Slides 09 Panopto||Reading 06|
|Wed 03/01||JSON Slides 09 Panopto|
|Fri 03/03||Functional Programming Slides 10 Panopto|
|Sat 03/04||Reddit and CSE Demographics||Homework 05|
|Functional Programming||Mon 03/06||Iterators, Generators Slides 11 Panopto||Reading 07|
|Wed 03/08||Parallel Computing Slides 12 Panopto|
|Fri 03/10||Server-Side Programming Slides 13 Panopto|
|Sat 03/11||Hulk Smash||Homework 06|
|Exam 02||Mon 03/20||Slides R2 Panopto Checklist 02||Reading 08|
|Wed 03/22||Exam 02|
|Fri 03/24||Compiling and Building Slides 14 Panopto|
|Unit 03: C|
|Pointers, Arrays, Strings||Mon 03/27||Libraries, Pointers, Arrays Slides 15 Panopto||Reading 09|
|Wed 03/29||Strings, Debugging (GDB, Valgrind) Slides 16 Panopto|
|Fri 03/31||Memory Allocation Slides 17 Panopto|
|Sat 04/01||C-String Library||Homework 07|
|Memory Management||Mon 04/03||Structs, Unions Slides 18 Panopto||Reading 10|
|Wed 04/05||Linked Data Structures Slides 19 Panopto|
|I/O and Files||Mon 04/10||Easter|
|Wed 04/12||I/O Slides 20 Panopto||Reading 11|
|Fri 04/14||Files, Directories Slides 20 Panopto|
|Sat 04/15||Detecting Duplicates||Homework 08|
|Sockets||Mon 04/17||TCP/IP, URLs, Sockets Slides 21 Panopto||Reading 12|
|Wed 04/19||HTTP Client Slides 21 Panopto|
|Fri 04/21||HTTP Server Slides 21 Panopto|
|Processes||Mon 04/24||Processes Slides 22 Panopto||Reading 13|
|Wed 04/26||Signals Slides 22 Panopto|
|Fri 04/28||VPS / Concurrent HTTP Server Slides 23 Panopto|
|Sat 04/29||Thor's Hammer||Homework 09|
|Exam 03||Mon 05/01||Slides R3 Panopto Checklist 03|
|Fri 05/12||Exam 03|
|Readings Weekly reading assignments.||10 × 4|
|Homeworks Weekly homework assignments.||3 × 10, 4 × 12, 2 × 16|
|Exams Exams covering each unit.||45, 45, 60|
All Readings and Homeworks are to be submitted to your own private GitHub repository. Unless specified otherwise:
Students are expected to attend and contribute regularly in class. This means answering questions in class, participating in discussions, and helping other students.
Foreseeable absences should be discussed with the instructor ahead of time.
Recalling one of the tenets of the Hacker Ethic:
Hackers should be judged by their hacking, not criteria such as degrees, age, race, sex, or position.
Students are expected to be respectful of their fellow classmates and the instructional staff.
Any student who has a documented disability and is registered with Disability Services should speak with the professor as soon as possible regarding accommodations. Students who are not registered should contact the Office of Disabilities.
Any academic misconduct in this course is considered a serious offense, and the strongest possible academic penalties will be pursued for such behavior. Students may discuss high-level ideas with other students, but at the time of implementation (i.e. programming), each person must do his/her own work. Use of the Internet as a reference is allowed but directly copying code or other information is cheating. It is cheating to copy, to allow another person to copy, all or part of an exam or a assignment, or to fake program output. It is also a violation of the Undergraduate Academic Code of Honor to observe and then fail to report academic dishonesty. You are responsible for the security and integrity of your own work.
In the case of a serious illness or other excused absence, as defined by university policies, coursework submissions will be accepted late by the same number of days as the excused absence.
Otherwise, there is an automatic penalty of 25% late penalty for assignments turned in 12 hours pass the specified deadline.
Note, there are opportunities for extensions as described below.
This course will be recorded using Zoom and Panopto. This system allows us to automatically record and distribute lectures to you in a secure environment. You can watch these recordings on your computer, tablet, or smartphone. In the course in Sakai, look for the "Panopto" tool on the left hand side of the course.
Because we will be recording in the classroom, your questions and comments may be recorded. Recordings typically only capture the front of the classroom, but if you have any concerns about your voice or image being recorded please speak to me to discuss your concerns. Except for faculty and staff who require access, no content will be shared with individuals outside of your course without your permission.
These recordings are jointly copyrighted by the University of Notre Dame and your instructor. Posting them to other websites (including YouTube, Facebook, SnapChat, etc.) or elsewhere without express, written permission may result in disciplinary action and possible civil prosecution.
Each Homework assignment has an associated Guru Point, which is an extra credit opportunity. To avoid a late penalty, a student may choose to forgo or give up that week's Guru Point in exchange for two more days in which the student can work on the assignment for full credit.
For instance if an assignment is due on Saturday, then the student will have until Monday to submit their work.
To take advantage of this, a student simply makes a note on the Pull Request for the assignment and refrains from getting credit for the Guru Point.
Note, there are no free extensions for Readings. Instead, students should be aware that they can drop three Reading grades.
For the assignments in this class, you may discuss with other students and consult printed and online resources. You may quote from books and online sources as long as you cite them properly. However, you may not look at another student's solution, and you may not copy any significant portions of other's solutions. Furthermore, you may not utilize AI powered tools such as Co-Pilot, Tabnine, or ChatGPT for any of your programming assignments.
The following table summarizes how you may work with other students and use print/online sources:
|Consulting||Allowed||Not Allowed||Not Allowed|
|Copying||Cite||Not Allowed||Not Allowed|
See the CSE Guide to the Honor Code for definitions of the above terms.
If an instructor sees behavior that is, in his judgment, academically dishonest, he is required to file either an Honor Code Violation Report or a formal report to the College of Engineering Honesty Committee.
In this class, as elsewhere on campus, students must comply with all University health and safety protocols, including:
We are part of a community of learning in which compassionate care for one another is part of our spiritual and social charter. Consequently, compliance with these protocols is an expectation for everyone enrolled in this course. If a student refuses to comply with the University’s health and safety protocols, the student must leave the classroom and will earn an unexcused absence for the class period and any associated assignments/assessments for the day. Persistent deviation from expected health and safety guidelines may be considered a violation of the University’s "Standards of Conduct,” as articulated in du Lac: A Guide for Student Life, and will be referred accordingly.