Skip to content

Conversation

@leahwho
Copy link

@leahwho leahwho commented Feb 5, 2020

This is the calculator project from Day 2 Homework

Assignment Submission: Calculator

Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions:

Reflection

Question Answer
What went well in your code style, such as indentation, spacing, variable names, readability, etc.? What was lacking? Variable names were descriptive, and my code is pretty DRY!
How did your code keep track of user input? I stored user input in variables.
How did your code determine what operation to perform? It called the "math" method which used a case statement for the operator_p parameter
What opportunities exist to create small methods for this project? I created 4 methods for validating a number, operator, acknowledging what operator the user entered, and doing math calculations
In the next project, what would you change about your process? What would you keep doing? CHANGE: I jumped right into this project without doing much pseudocode which I'm trying to get out of the habit of doing. KEEP DOING: I also got stuck on a problem, but instead of spinning my wheels, I asked a classmate and then went and got help from Kaida AND SOLVED THE PROBLEM WITH HELP! Also I was able to help a few classmates, which really helped solidify my understanding. I hope I can keep doing that.

This is the calculator project from Day 2 Homework
@jmaddox19
Copy link

Calculator

Major Learning Goals/Code Review

Criteria yes/no, and optionally any details/lines of code to reference
Correctly uses conditionals (if/else/elsif) ✔️
Correctly uses loops (while/until) ✔️
Correctly uses gets.chomp ✔️
Correctly uses variables ✔️
Correctly creates and uses custom methods ✔️

Functional Requirements

Functional Requirement yes/no
User can input two numbers and an operator and perform addition ✔️
User can input in two numbers and an operator and can perform subtraction ✔️
User gets feedback from the CLI when attempting to divide by zero, and the program does not give an error ✔️

Overall Feedback

Great work!

Overall Feedback Criteria yes/no
Green (Meets/Exceeds Standards) 3+ in Code Review && 2+ in Functional Requirements ✔️
Yellow (Approaches Standards) 2 in Code Review && 2+ in Functional Requirements
Red (Not at Standard) 0,1 in Code Review or 0,1 in Functional Reqs, or assignment is breaking/doesn’t run with less than 5 minutes of debugging

Code Style Bonus Awards

Was the code particularly impressive in code style for any of these reasons (or more...?)

Quality Yes?
Perfect Indentation
Elegant/Clever
Descriptive/Readable
Concise
Logical/Organized

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants