CST338: WEEK 1 - Understanding Java

In approaching the Codingbat problems, my method was to plan everything out and do each section in increments. By breaking down each problem into manageable steps and frequently running the code, I was able to track my progress and identify potential issues early on. This approach allowed me to build upon successful components and refine my solutions step by step.

For example, the problem requiring the detection of two 2's or two 4's in an array, but not both. I began by developing a solution for detecting two 2's, and once this was working correctly, I worked on a solution to detect two 4's. By creating more boolean expressions and using the XOR operator, I was able to create a solution that met the problem's requirements.

I learned that a trial-and-error approach wasn't effective for me, especially when dealing with seemingly straightforward problems. While some prompts were indeed simple, others required closer attention to detail. If I rushed through the problem statement or overlooked subtle requirements, I would end up with an incorrect solution. Without a clear plan in place, I would have to start over, wasting time and effort. This experience taught me the importance of taking the time to carefully read and understand the problem requirements, even when they seem simple

I also had some challenges due to my limited familiarity with Java's built-in methods. Initially, I relied heavily on loops to find specific indexes, only to discover the indexOf method later on. I also found that some problem prompts were a bit confusing, leading to misunderstandings and incorrect solutions. 

Overall, my experience with Codingbat highlighted the importance of careful planning and having a deep understanding of Java. I'm excited to continue learning and exploring all that Java has to offer.