CST 338 Weekly Journal #1

 Solving the Coding Bat challenges required a methodical approach, starting with breaking down each problem to clearly understand the inputs, outputs, and any specific conditions. I often planned out a basic solution structure in my mind or on paper before coding, focusing on what tools were most suitable, like loops, conditionals, or string operations. This planning helped streamline the coding process and minimized errors. After writing the initial solution, I tested it with diverse inputs, particularly edge cases, to ensure it handled all scenarios.

What worked best was taking time to break down each problem and use built-in methods that kept the code concise and effective. When I rushed into coding without fully planning, I occasionally encountered issues that required additional debugging. Most challenges took 1-2 tries, but a few required more attempts to address overlooked edge cases or logical errors. Overall, the process reinforced the importance of planning and testing thoroughly to create reliable solutions.