Homework

• All assignments are due before class begins.^due
• No assignments should include copy and pasted code.^copy
• No assignments should include code lifted or 'borrowed' from someone else without proper citation and licensing.^lift
• Incomplete homework is better than late homework.^incomplete
• Late homework is better than no homework.^late
• Asking for clarify or help on assignments is encouraged.^help
• Turning in code that you do not understand is discouraged and should be noted so we can address those issues.^{understanding}

^due. Why? So I have the same reference point across all students. Feel free to keep committing, I'll just use the last commit before class. ↩

^copy. Why? You don't get a prize for completed homework. The completed homework here is your growth as a developer. Not working code, necessarily. The priority is your work. ↩

^lift. Why? Ruby and Rails are built on open source and we should strive to be good members of the community. More than that: You need to know where things come from. And I need to know what's your's and what's somebody else's. ↩

^incomplete. Why? Again: the homework exists to make you a better developer, not to make new widgets, necessarily. To be frank, there will probably be some homework assignments that I fully expect won't be completed in time, but it's important that we have some code to review - so we can learn. ↩

^late. Why? See the previous. But more than that: You become a developer by doing the work. So, more than anything: do the work. ↩

^help. Why? We're here to learn, not beat our heads against the wall (too much). If you get stuck, speak up. ↩

^{understanding}. Why? More than syntax, we're trying to teach you how to think like a developer. On a practical basis: I will ask you to explain your code from time to time and at any time. ↩