This glossary defines common terms used in our class. Most are split up by the week they are introduced, though you can skip to course-specific terms for acronyms and words that are about our class itself (rather than computer science concepts).

This glossary is a new experimental resource! We’d love to hear from you with questions, suggestions, or concerns. Post on Ed!

Week 1: Java Basics; Printing, Strings, and Variables¶

Jave Basics¶

• bug: an error in a program
• class*: a file in Java where code is written
  • Note: all code you write in CSE 121 goes into one class
• class comment: a comment that explains a program and its general functionality
• comment: text in a code file that does not affect the behavior of a program
• compiler: a program that translates a programmer's instructions into a form that is more usable by a computer
• console: the place where a program's printed output appears
• debugging: the process of finding and fixing bugs
• executes/runs: when a computer reads a set of instructions written in code and performs them
• hardcode: the practice of placing fixed, unchangeable values directly into code that cannot be modified without modifying the program
• header comment: a comment at the top of a program that includes your name, the date you wrote the program, the class, the assignment, and your TA's name.
• print: display text to the console
• String: represents a collection of letters, digits, or other characters that are strung together
• whitespace: a term to describe characters that are 'invisible' on a screen, such as spaces, tabs, and new lines

Data Types, Expressions, Operators¶

• boolean: a data type that represents either true or false
• char: a data type that represents a single character
• double: a data type that represents decimal numbers
• expression: a combination of values and operators that evaluates to a single value
• int: a data type that represents whole numbers
• logical operators: a symbol used to evaluate an expression to true or false (ex &&, ||, !)
• modulo (mod): an operation that finds the remainder of division (%)
• operator: a symbol that performs an operation on a value or variable (ex +, /, %, &&)
• PMMDAS (a simplified order of operations):
  • P - parenthesis
  • MMD - modulo, multiplication, or division, whichever comes first (left to right)
  • AS - addition or subtraction, whichever comes first (left to right)
• precedence: the order in which subexpressions of an expression are evaluated
• relational operators: a symbol used to compare two values and evaluate an expression to either true or false (ex ==, <, >=)
• subexpression: a portion of an expression that can be evaluated independently
• type: the kind of data specified for a value (ex: int, double, String)
  

Course Specific Terms¶

• Pre-Class Materials/Work (PCM/W): Ungraded but highly encouraged short readings. Brief introduction to the new topics that will be covered in lecture; as such, they are due before every lecture.
• Post-Section Work (PSW): Short Google form submitted before midnight on the day of section, as problems within will typically be walked through during section. If enough are satisfactorily completed based on effort, an extra resubmission will be awarded.
• Introductory Programming Lab (IPL): CSE 12x's TA office hours, located in Mary Gates Hall (MGH) 334. Staffed for most of the afternoon and early evening on weekdays, as well as occasional weekends. Hours vary quarter to quarter. View this quarter's schedule.
• ESN Grading: The three grade buckets we use to categorize graded work, with E for Excellent, S for Satisfactory, and N for Not yet. Evaluations based on the skills required to understand and apply the concepts, as we are not necessarily looking for “perfect” code.
• Resubmissions (Resub): An opportunity to revise and resubmit either a programming assignment or a creative project, offered once per week.
• Creative Projects (Cx): Medium to longer semi-guided assignments that allow exploration of programming skills, as well as incorporating more freedom in extension implementations. Assigned a single ESN grade (based on the rubric) and are typically due on Tuesday by 11:59pm.
• Programming Assignments (Px): Longer assignments to assess understanding of class concepts, occasionally incorporating more elements and going further in-depth. Assigned four ESN grades (based on the rubric) and are typically due on Tuesday by 11:59pm.
• Code Quality Guide: Guide to writing quality code, as well as our grading standards for code quality.
• Commenting Guide: Guide to writing quality comments, as well as our grading standards for comments.
• Spec (Specification): Instructions that tell you what the program should do. Will often contain guidance, implementation guidelines, and tips!

Footnotes¶

* This is a topic that is not covered deeply in CSE 121. However, you’ll revisit this idea in-depth in CSE 122 & 123.

Acknowledgements¶

This iteration of the glossary was developed by Hannah Swoffer, Maitreyi Parakh, and Sushma Shankar. This is based on a prior glossary written by Hannah Swoffer and Trey Adams.