To complete this activity, you must submit the following (described below): "So what if my code is messy? It works just fine!" Grindlehook grumbles at you. "Sure, it can only be called once before it breaks, but you just need to be careful with how you use it. Focus on making your own code work!"
Like most goblins, your senior colleague Grindlehook is not a very good programmer. Unfortunately, he has worked for the Goblin Bank for many centuries, and he has a nasty temper. As the new hire, it's your job to integrate Grindlehook's code into the new Goblin Magical Loan System (GMLS), which will approve loans to wizards starting new businesses. The only catch is that you cannot change Grindlehook's code, even though it's critical to the system.
The GMLS gets a user's name and their desired loan amount, does some magical calculations based on the alignment of the stars, and indicates whether the loan is available. All of this is done through the most powerful interface known to wizards: the console.
Your learning goals are as follows:
1. Read and respond to real unit tests
2. Move data through a large program with multiple functions
3. Differentiate between printing, returning, inputted data, and parameters
4. Work with a "black-box" function (only knowing its inputs and outputs)