• CS220@JHU
• Syllabus
• Staff Office Hours
• Course Material
• Assessments
• Resources

Homework 0

Learning Objectives

Part 1

In your private git repository (created for you on Github under jhu-ip organization), create a new folder named homework, then a subfolder named hw0. In that hw0 subfolder, create three separate C source files with names given below that output exactly the messages shown below. In each case, the desired output message should be followed by a newline (“\n”) character.

The name and behavior of each program is as follows:

At the top of each source file, add two comment lines that provide your anonymous Hopkins ID (the random 6 characters code) and the current date:

// J3V6G9
// August 29, 2025

Compile and execute each of the three programs and ensure that they give the output exactly as shown. Finally, add all three source files to your git repository, commit them with an appropriate message, and push.

Part 2

Create a text file named gitlog.txt which demonstrates your recent git activity by typing the command git log > gitlog.txt

Part 3

Create a .zip file named hw0.zip which contains exactly the following four files: gold.c, silver.c, bronze.c, gitlog.txt. Copy the hw0.zip file to your local machine, and submit it via Gradescope. Specifically:

• Log into Canvas, access the EN.601.220 site.
• Click on the Gradescope link in the sidebar menu to access our course site for assessments and grading feedback.
• Click Homework 0.
• Click Submit (or Resubmit if you have done this before).
• Drag your zip file onto the Drag & Drop box (or click the box and select the zip file).
• Click Upload. You should see a confirmation that the submission uploaded successfully.

When you submit, Gradescope conducts a series of automatic tests. These tests do basic things like check that you submitted the right files and that your .c files compile properly. If you see error messages here (look for red), address them and resubmit.

Style Guidelines

You should make sure that your code has good style. You can look at the coding style guidelines here from a course you may take later (CSF) that also apply to this course. In brief, you should make sure that your submission is well formed, readable, consistently styled, and documented as follows:

• it is not overcommented or undercommented (not relevant for this little assignment)
• there are no ambiguous or meaningless variable names
• it has proper/consistent bracket placements and indentation
• there are no global variables
• lines are at most 80 characters long

Grading

Two notes regarding automatic checks on Gradescope for programming assignments:

• Passing an automatic check is not itself worth points. (There might be a nominal, low point value like 0.01 associated with a check, but that will not count in the end.) The checks exist to help you and the graders find obvious errors. This will be true for most of the assignments; the actual grades are given manually by the graders, along with feedback comments.

• The automatic checks cover some of the requirements set out in the assignment, but not all. For this assignment, you will notice that the silver.c program is checked, but not the other two. In general, it is up to you to test your own work and ensure your programs satisfy all stated requirements. Passing all the automatic checks does not necessarily mean you will earn all the points.

The 20 points for this assignment will be distributed as follows when we grade:

• [5] Style & Submission (including correct filenames, zipping, gitlog, and no compiler warnings)
• [5] Gold program
• [5] Silver program
• [5] Bronze program

Always practice incremental coding and testing, and frequent submissions for best results!