Lab exercises will be posted here weekly each Wednesday. The usual deadline is the following Tuesday night at midnight. But there are some exceptions. The work in lab will lead into and be part of the week's project. Labs will also count significantly towards participation.

Section A, B
Semester Fall 2018
Lab Times & Locations

Section A: W 2:30 - 3:50 pm, Davis 102

Section B: R 1:00 - 2:20 pm, Davis 102

Lab Instructor Eric Aaron
Office: Davis 113
Email: eaaron AT
Phone: (207)-859-5857
Office hours: M 11am-12:00noon, T 2:30-4:00pm (immediately following the CS231 lab section), R 11am-12:00noon and 2:30-3:30pm (immediately following the CS152 lab section), and by email appt.
Course Goals The learning goals for the lecture and lab are the same -- both are meant to work together to accomplish the goals for the course as a whole. They are
  1. Students can read a simple program and correctly identify its behavior.
  2. Students can convert a problem statement into a working program that solves a problem.
  3. Students understand abstraction and can break down a program into appropriate procedural and object-oriented components.
  4. Students can generate an approximate model of computer memory and describe how an algorithm affects its contents.
  5. Students can communicate the result of their work and describe an algorithm.
Labs and Projects

The work in lab will lead into and be part of the week's project. Labs will also count significantly towards participation.

During each lab, the instructor will not be able to answer questions about any projects until you have completed the exercises for that lab.

Programming projects involve completing more significant programs as well as a writeup describing the work completed in the project.


The grading policy for projects is designed to support three aspects of software production that are important for any computer scientist to have: high quality code, effective communication to the software's user or future programmer, and coding creativity and initiative. Each project has 30 points associated with it:

  • Completing programming tasks with well-designed, working code (up to 20 points)
  • Completing the write-up according to the instructions (up to 5 points). There were will 3-5 mini writing lessons throughout the semester. Each write-up will be graded based on whether or not it meets the standards set in the mini lessons.
  • Extensions (up to 5 points). The written instructions will include a variety of extensions to the assignment, or you can come up with your own. Completing one or more extensions is typical. Extensions are graded on quality and complexity -- not simply by counting the number of extensions.
Submission, Late Policy

You are expected to finish your write-up on Wiki and submit your source codes to filer before the deadline of each project.

Every student is allowed a free 3-day grace period on one project. Be sure to let us know when you are taking your "freebie" deadline extension! Other late projects will be given reduced grades. Programming projects are graded on a 30 point scale. Late projects (including freebies more than 3 days late) will not be eligible for extension credit and will be capped at a maximum of 25 points.

Collaboration, Academic honesty

Computer science, both academically and professionally, is a collaborative discipline. In any collaboration, however, all parties are expected to make their own contributions and to generously credit the contributions of others. In our class, therefore, collaboration on homework and programming assignments is encouraged, but you as an individual are responsible for understanding all the material in the assignment and doing your own work. Always strive to do your best, give generous credit to others, start early, and seek help early from both your professors and classmates.

The following rules are intended to help you get the most out of your education and to clarify the line between honest and dishonest work. We reserve the right to ask you to verbally explain the reasoning behind any answer or code that you turn in and to modify your project grade based on your answers. It is vitally important that you turn in work that is your own. We do use automated plagiarism detection software, so please be sure to abide by these, rather minimal, rules. Reports of academic dishonesty are handled by an academic review board and a finding of academic dishonesty may result in significant sanctions. For more details on Colby's Academic Integrity policies and procedures, see

  • If you have had a substantive discussion of any homework or programming solution with a classmate, then be sure to cite them in your write-up. If you are unsure of what constitutes "substantive", then ask me or err on the side of caution. As one rule of thumb, if you see more than 10 lines of someone else's code, then you should cite them. You will not be penalized for working together.
  • You must not copy answers or code from another student either by hand or electronically. Another way to think about it is that you should communicate with one another in natural human sentences, not in lines of code from a programming language.
The Colby Affirmation

Colby College is a community dedicated to learning and committed to the growth and well-being of all its members.

As a community devoted to intellectual growth, we value academic integrity. We agree to take ownership of our academic work, to submit only work that is our own, to fully acknowledge the research and ideas of others in our work, and to abide by the instructions and regulations governing academic work established by the faculty.

As a community built on respect for ourselves, each other, and our physical environment, we recognize the diversity of people who have gathered here and that genuine inclusivity requires active, honest, and compassionate engagement with one another. We agree to respect each other, to honor community expectations, and to comply with College policies.

As a member of this community, I pledge to hold myself and others accountable to these values. More ...

Academic Accommodations

I am available to discuss academic accommodations that any student with a documented disability may require. Please note that you’ll need to provide a letter from the Dean of Studies Office documenting your approved accommodations. Please meet with me to make a request for accommodations at the beginning of the semester--and at a minimum two weeks before any key due dates--so that we can work together with the College to make the appropriate arrangements for you. Dean Joseph Atkins ( is the primary contact for accommodations and any questions related to educational testing and documentation.

Title IX Statement

Colby College prohibits and will not tolerate sexual misconduct or gender-based discrimination of any kind. Colby is legally obligated to investigate sexual misconduct (including, but not limited to, sexual assault and sexual harassment) and other specific forms of behavior that violate federal and state laws (Title IX and Title VII, and the Maine Human Rights Act). Such behavior also requires the College to fulfill certain obligations under two other federal laws, the Violence Against Women Act (VAWA) and the Jeanne Clery Disclosure of Campus Security Policy and Campus Statistics Act (Clery Act).

To learn more about what constitutes sexual misconduct or to report an incident, see:

If you wish to speak confidentially about an incident of sexual misconduct, you may contact:

  • Counseling Center: 207-859-4490
  • Gender and Sexual Diversity Program: Director Emily Schusterbauer ( 207-859-4093)
  • Office of Religious & Spiritual Life: 207-859-4272
    • Dean of Religious & Spiritual Life, Kurt Nelson (
    • Jewish Chaplain, Erica Asch (
    • Catholic Campus Minister, Charles Demm (

Students should be aware that faculty members are considered "responsible employees"; as such, if you disclose an incident of sexual misconduct to a faculty member, they have an obligation to report it to Colby's Title IX Coordinator. "Disclosure" may include communication in-person, via email/phone/text, or through class assignments.

© 2018 Eric Aaron (who gratefully acknowledges contributions of Colby CS colleagues!) .