You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
Click the Edit button when you're ready to start adding your answers.
To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
Please use the following gist to capture your thoughts, goals, priorities, etc. as outlined by each question. You will be using these questions to help give your mentor a better idea of who you are and want to become as a developer! Please note, this is meant to be a starting point for building your norms with your mentor - you may need to adjust scheduling expecations, communication expectations, etc. when you start working with your mentor!
1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.1. Click the Edit button when you're ready to start adding your answers. Type your answers directly into this document.1. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
There's a lot of discussion online about recursion, but most of it missed the mark as I've been studying the topic.
So instead of the usual things that get said when trying to teach recursion, I'm going to say a couple things that help me:
Yes, recursion is calling a method inside of itself; however....
The parameter/argument that's passed into the 2nd method call must change the input...typically by reducing the original parameter by one, or by half (or some other amount)
It helps to think of Ruby as "pausing" the 1st call, and then "starting" the second call....and then "pausing" the 2nd call, and starting the 3rd call...etc