Schedule

This class meets TuTh 12:30PM - 1:45PM in Library 166 and lab on Monday 3:00PM - 4:45PM in Ballentine Hall 114.

Overview¶

The following is a tentative outline of topics in an order, these things will be filled into the concrete schedule above as we go. These are, in most cases bigger questions than we can tackle in one class, but will give the general idea of how the class will go.

How does this class work?¶

~ one week

We will start by introducing some basics of GitHub and setting expectations for how the course will work. This will include how you are expected to learn in this class which requires a bit about how knowledge production in computer science works and getting started with the programming tools.

What tools do Computer Scientists use?¶

Next we’ll focus in on tools we use as computer scientists to do our work. We will use this as a way to motivate how different aspects of a computer work in greater detail. While studying the tools and how they work, we will get to see how some common abstractions are re-used throughout the fields and it gives a window and good motivation to begin considering how the computer actually works.

Topics:

• bash

• linux

• git

• i/o

• ssh and ssh keys

• number systems

• file systems

What Happens When I run code?¶

Finally, we’ll go in really deep on the compilation and running of code. In this part, we will work from the compilation through to assembly down to hardware and then into machine representation of data.

Topics:

• software system and Abstraction

• programming languages

• cache and memory

• compiliation

• linking

• basic hardware components

Recommended workload distribution¶

To plan your time, I recommend expecting the following:

• 30 minutes, twice per week for prepare work (typically not this much).

• 1.5(review)-3(practice) hours, twice per week for the dated badges (including revisions).

For each explore :

• 30 min for proposal

• 7 hours for the project

For each build:

• 1.5 hour for the proposal (including revisions)

• 22 hours for the project

• 30 min for the final reflection

This is a four credit course, meaning we have approximately 4 hours of class + lab time per week($75 \times 2+105 = 255$ minutes or 4.25 hours). By the accredidation standards, students should spend a minimum of 2 hours per credit of work outside of class over 14 weeks. For a 4 credit class, then, the expected minimum number of hours of work outside of class you should be spending is 112 hours(2 * 4 * 14). With these calculations, given that there are 26 class sessions and only 18 review or practice are required, it is possible to earn an A with approximately 112 hours of work outside of class and lab time.

Tentative Timeline¶

This is the planned schedule, but is subject to change in order to adapt to how things go in class or additional questions that come up.

Tentative Lab schedule¶