42 lines
1.6 KiB
Plaintext
42 lines
1.6 KiB
Plaintext
HOMEWORK 2: Ride Sharing
|
|
|
|
|
|
NAME: Jinshan Zhou
|
|
|
|
|
|
COLLABORATORS AND OTHER RESOURCES:
|
|
List the names of everyone you talked to about this assignment
|
|
(classmates, TAs, ALAC tutors, upperclassmen, students/instructor via
|
|
LMS, etc.), and all of the resources (books, online reference
|
|
material, etc.) you consulted in completing this assignment.
|
|
|
|
<sstream>, <iomanip> usage cases online. And one of my classmates - Qijun Lu
|
|
|
|
Remember: Your implementation for this assignment must be done on your
|
|
own, as described in "Academic Integrity for Homework" handout.
|
|
|
|
|
|
ESTIMATE OF # OF HOURS SPENT ON THIS ASSIGNMENT: 12 hr
|
|
|
|
|
|
MISC. COMMENTS TO GRADER:
|
|
Ignore the debug codes. To enable it, take `debug` as the last argument.
|
|
|
|
|
|
## Reflection and Self Assessment
|
|
|
|
Discuss the issues you encountered during development and testing. What
|
|
problems did you have? What did you have to research and learn on your
|
|
own? What kinds of errors did you get? How did you fix them?
|
|
|
|
What parts of the assignment did you find challenging? Is there anything that
|
|
finally "clicked" for you in the process of working on this assignment? How well
|
|
did the development and testing process go for you?
|
|
|
|
The complexity of this assignment has significantly increased. I attempted
|
|
to write the code directly but encountered unprecedented difficulties, and
|
|
the code became increasingly messy. Eventually, I had no choice but to draw a
|
|
flowchart and then gradually implement the code based on it. This means that
|
|
textual descriptions are not as clear as diagrams, so next time I will read
|
|
the documentation first, design the structure properly, and then start coding.
|