Home Basic expectations
Programming homework must be completed individually; all code you submit must be your own work. Please consult the syllabus for more details.
Do not use material that you haven't been taught. When in doubt, ask.
In this course, you may not use "advanced material" – material we have not taught you yet.
The reason we assign you homework is to make sure you understand certain concepts and to make sure you are practicing and honing your problem-solving skills. Using advanced material will often make assignments "too easy", depriving you of the opportunity to practice both those things.
If you don't know if something counts as advanced material, definitely feel free to ask, and we'll be more then happy to clarify.
If you have prior programming experience, and have just started CSE 142 or CSE 143x, you should be aware that on your first assignment, the only language features you are allowed to use are:
- Methods that accept no parameters
If you have skipped CSE 142 and have jumped straight to CSE 143, you should be aware that the only material you are initially allowed to use is material covered during CSE 142 and directly taught in lecture or section. It may be good idea to review old 142 websites to get a sense of what is and isn't allowed, but in general, you are expected to know and are permitted to use:
- Control flow structures (
while, but NOT
- Methods, returns, and parameters
- Variables and basic types (
- Arrays (but NOT ArrayList!)
- Basic objects (some inheritance)
This is not a comprehensive list of topics, but should be enough to get you started on your first homework assignment and get a basic feel for what is and isn't expected.
Practice good craftsmanship
When submitting a homework assignment, make sure it is as complete, clean, and polished as possible – endeavor to submit a professional product. Just like writing an essay, you should plan on having several proofreading stages before submission. Our course is designed to reward people who are detail-oriented.
In particular, be sure to throughly test your code, write good comments, check for segments of code that break a rule from this style guide, remove all debug code, and so forth.