Editing DS4UX (Spring 2016) (section)

=== Weekly Tutorials and Coding Challenges ===
For the first few weeks of the course, I will assign you some short tutuorials as homework. These are intended to help you practice and remember basic programming concepts. 

Each week I will also give you all a set of weekly coding challenges before the end of class. Most of these challenges will involve changing or adding to code that I've given you as part of the projects in the final parts of class to solve new problems. 

These tutorials will not be turned in or graded. I may ask your to turn in ''some'' of the coding challenges--I'll be very clear in specifying which ones. Coding challenges I ask you to turn in need to be submitted, even if you only have a partial solution, however they '''will not be graded for correctness'''. You'll receive credit for attempting the coding challenge, not for whether your answer is correct. 

I will share my solutions answers to each of the coding challenges by Monday morning of class. As you will see over the course of the quarter, there are many possible solutions to many programming problems and my own approaches will often be different than yours. That's completely fine! Coding is a creative act!

Please do not share answers to challenges before midnight on Sunday so that everybody has a chance to work through answers on their own. After midnight on Sunday, you are all welcome to share your solutions and/or to discuss different approaches.  We will discuss the coding challenges for a short period of time at the beginning of each class.

Graded coding challenges only account for a small part of your grade, but if you repeatedly ignore them the numbers will add up. Worse: you're likely to fall behind in the course. Best practice is to always turn something in! Remember: you're not being graded on whether you answered the question correctly, only that you attempted to answer the question.
<br/>