CHIPS (Programming assignments)
To complement the Content-Oriented Didactic (COD) materials such as the book and lectures, CHIPS (Coding & Hands-on Integrated Projects) provide hands-on skills practice and are keyed to specific sections in the book. This section describes how to use them with Codio. The book's website has other options if you don't wish to use Codio, but we have pretty extensive automated workflows that are optimized for Codio, for publishing both the book content itself and these CHIPS along with their autograders.
The relative effort of each CHIPS is indicated by one star (a couple of hours of work), two stars (several hours of work), or three stars (a potentially multi-day assignment).
- 1.Autograded: The solutions repos include reference solutions, Codio-based autograders in the Codio course, and files for manually configuring Gradescope-based autograding. (Gradescope is no longer officially supported, so use those files at your own risk.)
- 2.Self-graded: CHIPS involves coding, but rather than an autograder, includes tests students run themselves.
- 3.Comprehension: CHIPS involves minimal or no coding, but rather performing some tasks and answering self-check questions about them. The questions are usually built into the Codio version of the assignment.
- 4.5 Rails Routes (self-graded): not actually a homework assignment, but a simple app that lets students enter syntactically valid Rails routes and understand the RESTful routes that Rails would generate for them.
- 5.7 Associations (TBD)
- 6.9 AJAX Enhancements to RottenPotatoes (TBD)
- 8.5 RSpec on Rails: (Note: This CHIPS is in the process of being replaced. We recommend just using 8.9 until that time.) Given a Cucumber scenario for a not-yet-implemented feature, students use TDD and RSpec to write tests that drive the creation of the code to make the scenario pass. Students also learn to use Travis CI to automate testing workflow.
- 10.5 Agile Iterations Two (or more) full iterations of Agile adding features to an existing (legacy) app
- Design Review: We use this in the project portion of the course. This is not a programming assignment but rather a 3-part scaffolded process for doing design reviews and technical presentations. (Each part can be used more or less independently.) It is intended to be used in conjunction with student teams doing their own open-ended projects, so no code is provided. In part 1 (Design Review), teams are paired up and each team evaluates the other's design and gives feedback on possible improvements. In part 2 (Presentation), teams give technical presentations about the design review; these are peer-evaluated (or instructor-evaluated) according to a provided rubric. In part 3 (Handoff), teams modify their repos as needed to ensure the project is easy for another team to pick up and continue working on.