Create Jessica Owens -- Carets

[vertige]

Calculator

Congratulations! You're submitting your assignment.

Comprehension Questions

Question	Answer
Describe how you stored user input in your program.	Into variables.
How did you determine what operation to perform?	Using the users input, sorted it by hash where key would indicate which operation to perform.
How did you make sure your program behaved correctly?	Lots of testing. In part, in irb for snippets of code, but mostly through running my program in ruby, occasionally printing extra information to see results.
Do you feel like you used consistent indentation throughout your code?	I tried...
If you had more time, what would you have added to or changed about the program?	I would have simplified the way I checked for numbers... My method was convoluted and left options such as 3.0.0 as valid. Would eliminate needing to check negatives, etc. (I refactored this morning and will submit an updated version... Not yet with parentheticals.) Today I would have started with a simpler thing like user_input.to_f.to_s == user_input || user.to_i.to_s == user_input. I got tired. I also would have setup parentheticals along the lines of Option B in the comments on line 142

[tildeee]

Calculator

What We're Looking For

Feature	Feedback
Takes in two numbers and an operator and performs the mathematical operation.	x
Baseline
Readable code with consistent indentation.	two spots in code where indentation was a little off
Extras

[tildeee]

Let's loop back together soon, your code doesn't run for me

[vertige]

Sounds good. The first or second commit? I tried to edit the second one in place instead of fully copy and pasting all of the code, so if it's the second one, I very well might have missed somethings :/

…

Sent from my iPhone

On Aug 14, 2017, at 08:03, dee ***@***.***> wrote: Let's loop back together soon, your code doesn't run for me — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[tildeee]

@vertige yup, your first commit runs. We'll look into a better way to submit code that may have helped with this (using git, lecture on Wednesday), but in general be careful about what you submit-- we'll only be checking the latest commit.

[vertige]

OK, I just check and my new one runs, so it was probably a copy/paste error :/ Sorry! I know now. I thought, since the second commit was much later in the day, it wouldn't count. Should I not resubmit later in a day (would that be considered a late submission?) and just wait until after your feedback to make updates for myself? Thanks!

…

On Mon, Aug 14, 2017 at 8:56 AM, dee ***@***.***> wrote: @vertige <https://github.com/vertige> yup, your first commit runs. We'll look into a better way to submit code that may have helped with this (using git, lecture on Wednesday), but in general be careful about what you submit-- we'll only be checking the latest commit. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#30 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYhkAz17NYknc0h_uMmG1rj4VkBBj9dSks5sYG4jgaJpZM4O00rL> .

[tildeee]

We check pull requests before the deadline for submission,
and we check the latest commit for giving feedback