Get used to using &#x27;grep&#x27; or &#x27;ack&#x27; to dig through a codebase to find things. For example, if your task is, &quot;Add a new button &#x27;Find Vendors&#x27; next to the &#x27;Find Clients&#x27; button on the Company Search report&quot;, I would:<p>1. grep for the string &#x27;Find Clients&#x27; to find the UI<p>2. Note the URL that it hits when you click it<p>3. grep for a unique fragment of that URL to find where the routes are stored. Make sure you grep for something &#x27;static&#x27;, so if the url is &#x27;&#x2F;search&#x2F;query.html?action=search_clients&#x27; you could grep for &#x27;query.html&#x27;.<p>4. The route should map to some code that implements it. grep for the controller or whatever else you find in the routes.<p>5. Once you&#x27;ve found the controller, something there should retrieve a list of clients. Find out how it&#x27;s hitting the database.<p>Then you should know enough to tack on a new button in the UI and modify the controller to hit the database in a different way. Something as simple as &#x27;grep&#x27; I never used in college or high school, but use all the time having needed it on the job for the past couple years.