Tutor profile: Anthony H.

Describe SOH-CAH-TOA and what it's used for.

SOH-CAH-TOA is an acronym that helps us remember how to solve for the length of a side of a right triangle if we know the measurements of others and just one of the angles. Sine = Opposite/Hypotenuse, Cosine = Adjacent/Hypotenuse, and Tangent = Opposite/Hypotenuse. We can solve for any one of the above measurements including the angle by plugging the appropriate numbers into the formula matching the information we know. "Opposite" refers to the side length that is across from the angle we know, and "Adjacent" refers to the side touching the angle. We can solve for the sine, cosine, and tangent of the angle using our calculators and using algebra, solving for the unknown side.

What is the order of operations and why does it matter?

The order of operations can be broken down into a vey simple acronym, PEMDAS. It can be memorized as, "Please Excuse My Dear Aunt Sally", or however you prefer. In sequence, it stands for Parenthesis, Exponents, Multiplication, Division, Addition, Subtraction. This refers to how each segment of an algebraic expression or equation should be calculated. For example, an expression like (2+2)^2 - 3 can be broken into parts. Parentheses are considered first, so we solve the expression inside of them. This gives us (4)^2 - 3. Based on the OOO, next is exponents. 4^2 gives us 16, which leaves us with 16 - 3. Since the there is no M,D, or A to consider, this leaves us with the last step in the process, subtraction! 16 - 3 = 13. The Order of Operations matters because it lays out the process we need to go about to solve an algebraic expression. If we decided to solve this in an order we just preferred, we would have a totally different answer.

What are some mistakes you've learned from while writing code or testing software?

One of the biggest mistakes I've learned from is getting discouraged when things don't go right the first time. Coding, testing, or almost anything relating to software can sometimes be a struggle, especially because a majority of the time, the way you go about a problem must be precise. However, it's about how you learn from those struggles and bounce back that have made me into the software engineer and even person I am today. It's very important to stay committed to a task and not give up, because the outcome is almost always worth the work put in.