<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Assignments :: CS135</title>
    <link>https://student.cs.uwaterloo.ca/~cs135/assign/index.html</link>
    <description>Assignments are where the rubber hits the road for CS135. Putting lecture content into practise is the best way for you to learn and one of the primary ways we assess your learning.&#xA;This section of the web site is concerned with the assignments themselves and resources for doing them. There are also a number of assignment policies .&#xA;Advice:&#xA;Begin early. Submit as soon as you have some results. Submit again every time you have a substantive improvement. Submit using the submission button for the appropriate assignment in the table, below. We don’t accept assignments any other way. Submit on time; there are penalties for being late. late policy Submit well before the due date; the servers get busy and slow as the due date/time approaches. Due date/time is the time in Waterloo; assuming your computer’s date/time is set correctly for your locale, Waterloo’s date and time are displayed in the upper left corner of every CS135 web page. Ask questions on Piazza . When release of assignment marks is announced on Piazza, check your marksheet (website -&gt; Assignments -&gt; View Submissions) to see what you did right, what you did wrong (if anything) and to see if there are any marking errors. Also check the post mortem (Assignments page) for common errors to avoid. After assignment 01, for each function we ask you to write, you must have a purpose, contract, function definition, and comprehensive tests. The basic tests only check for a contract and function definition, so it is your responsibility to make sure you have the other portions. For any helper functions you write, you don’t need any design recipe, but tests should still provide full coverage. Your tests should run all of your code ideally, there should be no highlighting left when you run them. You can never test too much.</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 28 Jun 2019 13:25:24 -0400</lastBuildDate>
    <atom:link href="https://student.cs.uwaterloo.ca/~cs135/assign/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Racket and DrRacket</title>
      <link>https://student.cs.uwaterloo.ca/~cs135/assign/dr_racket/index.html</link>
      <pubDate>Fri, 28 Jun 2019 13:17:33 -0400</pubDate>
      <guid>https://student.cs.uwaterloo.ca/~cs135/assign/dr_racket/index.html</guid>
      <description>CS135 uses Racket as its language of instruction. Racket is not widely used in industry, but is nonetheless very useful for teaching transferable skills that will serve you well professionally. It is also simple and clean enough that we cover computer science content many CS students do not see until later in their CS careers.&#xA;DrRacket The editor (IDE) we use in CS135 is called DrRacket.</description>
    </item>
    <item>
      <title>Style Guide</title>
      <link>https://student.cs.uwaterloo.ca/~cs135/assign/style_guide/index.html</link>
      <pubDate>Thu, 06 Jun 2019 17:04:25 -0400</pubDate>
      <guid>https://student.cs.uwaterloo.ca/~cs135/assign/style_guide/index.html</guid>
      <description>Style Guide The CS135 style guide should help you write better code and make it easier for you to complete your assignments quickly. It pulls together material from lectures L01 to L04, along with additional examples and explanations.</description>
    </item>
    <item>
      <title>Basic Tests</title>
      <link>https://student.cs.uwaterloo.ca/~cs135/assign/basic-tests/index.html</link>
      <pubDate>Fri, 28 Jun 2019 13:25:24 -0400</pubDate>
      <guid>https://student.cs.uwaterloo.ca/~cs135/assign/basic-tests/index.html</guid>
      <description>A few minutes after you submit your assignment you will be given a link containing feedback on your submission. These Basic Tests determine whether your assignment is gradeable by our scripts. For example:&#xA;Does it have the correct file names? Does it have the correct function names? Do functions have the correct number of parameters? Are the values the function produces in the correct format? Etc. Getting a mark of less than perfect on the Basic Tests means that you WILL FAIL many if not all of the automated tests, resulting in a very low mark for the program.</description>
    </item>
    <item>
      <title>View Submissions</title>
      <link>https://student.cs.uwaterloo.ca/~cs135/assign/viewsubmissions/index.html</link>
      <pubDate>Fri, 28 Jun 2019 13:15:04 -0400</pubDate>
      <guid>https://student.cs.uwaterloo.ca/~cs135/assign/viewsubmissions/index.html</guid>
      <description></description>
    </item>
  </channel>
</rss>