Computer Science Pragmatics

This is a 2-credit hour seminar designed to teach students the essentials of using a computer effectively for EECS students. While the target audience is EE/CE/CS/DS students, any student wishing to learn how to use their computer more effectively is encouraged to join. Students are expected to be familiar with basic concepts of programming, such as control flow (e.g. if-else, loops, functions) and expressing their ideas in program statements. Topics covered include Unix-like systems, shells, version control, build systems, debugging, and scripting. The ultimate goal of the class is to give students hands on experience with the prevailing tools of the trade as well cultivate research skills for picking up new tools in an ever-evolving computing landscape.

This course is designed with several objectives in mind:

• Introduce topics in the development of and usage of computing systems, such as version control
• Cultivate research skills for reading up on and picking up new tools in a constantly changing computing landscape
• Provide hands on experience with mature and prevailing tools and technologies that have survived the test of time

This class is run as a “flipped classroom”, where the bulk of information transfer happens at home or on your own time via videos made by yours truly and in-person class time is used as a more interactive environment for questions and answers, hands on activities, and time to complete your assignments while having direct access to the course staff. This approach was taken as a means to optimize means of instructor contact: videos allow the instructor to provide you more tightly edited content to condense the amount of time needed to convey information and frees up more in-person time for interactions with the instructional staff that aren’t dry information.

In-person classes will be held in person and remotely accessible live via the Zoom teleconferencing software, and will be recorded. Attendance will not be mandatory. If you intend to attend the live lecture over Zoom, please log in using your UMich email as attendance is restricted to the UMich domain.

To facilitate the goals of the class, there will be two assessment types: “Basic” and “Advanced”. Basic assessments are in the form of weekly assignments designed to guide and ease students into picking up a new tool or method. Advanced assessments come in the form of weekly assignments, referred to as “advanced assignments”. These assessments are designed for students to practice researching additional information and apply it towards solving problems that may very well crop up in real computing systems. The weekly advanced assignments are structured similarly to the weekly basic assignments except with less guidance.

Each week a set of videos will be released about the week’s topic along with the associated Basic and Advanced assignments. The Basic assignment will usually be the topic of a given week’s in-person class and time will be reserved for you to work on either assignment with the opportunity to ask the instructor for help.

Basic assignments that will contribute points to the Basic category. Advanced assignments that will contribute points to the Advanced category. Not all assignments will have to be completed: the grading section will have details on how you can organize your efforts.

This course utilizes a point-accumulation method whose point sums map to a typical grading scale. That means that there is no averaging of grades: to make the letter grade you want, you simply have to accumulate enough points for it by completing assignments. There are multiple categories of points, and the “adjusted” sum of each category’s points is used to determine your final letter grade. Each category may have certain rules on how many points you can earn from them, hence the quoted “adjusted”. This will be elaborated in the following sections.

Final Letter Grades

If you are unfamiliar with interval notation, ‘[’ / ‘]’ include a number and ‘(‘ / ‘)’ exclude a number. “[90, 93)” means the range of numbers between 90 and 93, including 90 but excluding 93.

• [100, ∞): A+
• [93, 100): A
• [90, 93): A-
• [87, 90): B+
• [83, 87): B
• [80, 83): B-
• [77, 80): C+
• [73, 77): C
• [70, 73): C-
• [67, 70): D+
• [63, 67): D
• [60, 63): D-
• [0, 60): E

Basic (60 points)

Each basic assignment will be worth 6 points in total. The total number of points for basic assignments is capped at 60. This means that if you do 12 basic assignments, the number of points you get from the Basic category will be max(12 * 6, 60) = 60. Nominally, this means you only have to get full credit on 10 basic assignments to hit the 60 point total. This serves as a built-in buffer for missing/not doing assignments, as there are more than 10 basic assignments in the class. That being said, it is expected that you do each basic assignment as a means to familiarize yourself with a topic.

The goal of these assignments is to reinforce concepts introduced in lecture and to give hands-on experience. To emphasize this, your assignment scores will be converted the following way for final grade calculation: what number we report to you will be the raw score. On the left is the raw score and on the right is the adjusted final score.

• Scores below 0.5 will not be adjusted
• (0.5, 2] = 2
• (2, 4] = 4
• (4, 6] = 6
• Scores above 6 will not be adjusted

This allows you to get full credit while allowing the staff to point out mistakes.

Some assignments will be submitted over the EECS GitLab server (gitlab.eecs.umich.edu) and some assignments will be submitted over Gradescope. All assignments have “hard” deadlines, after which submissions will not be accepted.

Advanced (40 points)

There are two possible ways to approach the Advanced category. Each weekly advanced assignment is worth 10 points in total, which means you only have to do 4 to meet the category total.

Unlike the Basic category, all points past the category total of 40 points will be worth 50%. For example, if you do 9 advanced assignments and get full credit, you will earn 9 * 10 = 90 raw Advanced points. The 50 points after the initial 40 points will be worth half: therefore your final Advanced score would be 40 + (50 / 2) = 40 + 25 = 65.

Submission and grading of advanced assignments consists of two steps:

• You submit the assignment to the EECS GitLab server (gitlab.eecs.umich.edu) or Gradescope, as specified in the assignment instructions. All assignments have “hard” deadlines, after which submissions will not be accepted.
• You attend a lab session to get the assignment graded by the course staff. In general, you will have until the end of the following week to have the assignment graded. For instance, if an assignment is due on a Wednesday, you will have until the last lab session on the Friday 9 days after that to get your work graded. This timeline may be shortened for the last advanced assignment due to the end of the semester.

Make sure to come to lab prepared to talk over your work with course staff. If it has been several days since you completed it, make sure to review it before coming to lab to get it graded.

Class

Attendance during the in-person lecture is not required for this course. However, there may be activities for which you can get participation points. I may open up a survey to ask you about what you learned or got out of a class (recording), giving you 1 point for each survey.

In addition, there may be quizzes for the lecture videos. Each quiz is worth 1 point.

Both the surveys and quizzes will be time sensitive to encourage you to keep up with them in a timely manner. Both surveys and quizzes will have a hard cut-off date after which they will no longer accept submissions.

There is no point cap for this category: each point will be worth its full amount. This category effectively serves as extra credit for your participation, and can help get you out of other work :)

Attendance in lab sections is only required for getting advanced assignments graded. However, the staff are there to help – we won’t have many office hours outside of lab, so labs are the best place to get real-time help from the course staff.

Summary

Your final score is based off of sums of the final “adjusted” point totals of each category, having taken into account the cap of 60 points for the Basic category and points past the Advanced category total of 40 being worth 50%. This allows for multiple ways to get an A or A+ in the class. You can do 10 basic assignments and 4 advanced assignments. You could slack off on some basic assignments and make up for it with more advanced assignments. This grading scheme is set up to allow for flexibility dealing with the workloads in whatever classes you are taking. Keeping up with the class by watching videos and doing the quizzes will only improve your grade by adding unweighted points to the total.

tl;dr You add up the point values you earn for each assignment, taking into account the cap on Basic points and how Advanced points past the category total are worth half, and your final total determines your letter grade.

Work in this class is intended to be done alone: your code should be your own. That being said, you can help point each other towards information or help explain concepts to each other.

You should have a computer that runs Windows, macOS, or Linux that you can install software on. Chromebooks are welcome if they have have the ability to set up a Linux environemnt (Crostini).

While the class is very flexible, it’s still on you to keep up and not get left behind. You are encouraged to keep up with the weekly videos, do the quizzes for extra points, and come to class to complete the week’s basic assignment. The quizzes will add up in the end, allowing you to skip out on some assignments.

There will be multiple ways that communication can occur in the class:

• Canvas: Announcements and a fancy gradebook
• Ed Discussion: Course content and logistics related questions
  • If you share part of your solution, please make your question private
• Email: For personalized correspondance and more personal matters
  • Please start the subject line with “EECS 201” so I can find it