Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phoebe - Ampers #21

Open
wants to merge 72 commits into
base: master
Choose a base branch
from
Open

Phoebe - Ampers #21

wants to merge 72 commits into from

Conversation

pmanni02
Copy link

Hotel

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe a design decision you had to make when working on this project. What options were you considering? What helped you make your final decision? One design decision was whether or not I needed a Room class. After creating a Room class during Wave 1, I realized that I probably would not need a Room class. However, I kept it in case I might need it. This decision worked out until I started working on the cli. Making/starting the cli revealed issues with my code. One major issue (which required lots of late changes) were the instance variables of the Room clas. If I could start over, I would try having Reservations within a Room instance instead of the other way around.
Describe a concept that you gained more clarity on as you worked on this assignment. Overall design. Design diagrams helped me anticipate many potential issues. Additionally, with the exception of the changes mentioned in the question above, my design process allowed for flexibility with changes.
Describe a nominal test that you wrote for this assignment. One nominal test was making sure a block hash could be created.
Describe an edge case test that you wrote for this assignment. One edge case test was passing an invalid number of rooms for a block into my method for making blocks.
How do you feel you did in writing pseudocode first, then writing the tests and then the code? I feel I did pretty good. The pseduocode really helped with planning where to start. I could have done more pseudocode near the end of wave 3. It may have helped me avoid the major changes needed at the last minute.

pmanni02 added 30 commits March 5, 2018 13:04
blocks.each do |block|
block_start = block[:start_date]
block_end = block[:end_date]
room_objs = block[:rooms]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While these variables look nicer, its not actually better to create these local variables that you're only using once rather than using the original variables. You should only use local variables if you'll be using them for a larger purpose.

@kariabancroft
Copy link

Hotel

What We're Looking For

Feature Feedback
Design
Demonstrated classes having a single responsibility Yes. You did a nice job separating things out into their separate classes. Also, nice use of private methods.
Demonstrated loose coupling Yes
Methods demonstrate a good use of encapsulation, inputs and outputs Yes-looks good
Wave 1 requirements Yes
Wave 2 requirements Yes
Wave 3 requirements Yes

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