Skip to content

Lindsay - Ride Share - Edges#36

Open
elle-terch wants to merge 2 commits into
Ada-C10:masterfrom
elle-terch:master
Open

Lindsay - Ride Share - Edges#36
elle-terch wants to merge 2 commits into
Ada-C10:masterfrom
elle-terch:master

Conversation

@elle-terch

Copy link
Copy Markdown

ride share

Congratulations! You're submitting your assignment.

Comprehension Questions

Question Answer
What did your data structure look like at first? Did this structure evolve over time? Why? I originally had way too many layers in my data structure. It evolved as I started writing code and realized that some of the layers were unnecessary to answer the questions (ex. I originally had a layer for rider data).
What was your strategy for going through the data structure and gathering information? I started by typing out all of the data into Numbers. This let me see things a bit more visually so I could understand exactly how to target certain arrays or hashes.
What was an example of something that was necessary to store in a variable? What was the scope of each of that variables? Why? I created a variable called total_rides that lived within an each statement. This variable equaled total rides by driver. So each time the method iterated over a different driver, the variable would changed based on data in that driver's hash only. So while the variable changed values, it stood for the same thing throughout the code block.
What kinds of iteration did you use? Did you use .map? I used .each iterations for everything. I did not use .map but I can see places where that would have made more sense.
Were some calculations easier than others? Why? As the questions progressed, I had to pass through deeper layers of data. This made the calculations trickier to think through. By the last two questions, I was passing the array containing all data so I had to use nested .each methods.

@droberts-sea

Copy link
Copy Markdown

Good work overall! I appreciate the way you used methods to break up your functionality - this makes your code very easy to read. Keep up the hard work!

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