CST 338 Weekly Journal #1
Weekly Journal When I worked on the Coding Bat challenges, I tried to break each problem down first so I really understood the inputs, outputs, and any conditions. Before jumping into the code, I’d usually have a plan in my head or jot something down just to map out what I was going to do and figure out what would help most, like loops, if statements, or string methods. Doing that upfront made it easier to write the code and avoid mistakes. Once I had something written, I tested it with different inputs, especially edge cases, to make sure it covered everything. What helped the most was taking my time to break the problems down and using built-in methods to keep my code clean and simple. The times I rushed into coding without a clear plan, I usually ended up running into issues that I had to go back and debug. Most of the problems I solved in 1-2 tries, but a few took more because I missed an edge case or made a small logic error. Overall, it reminded me how important it is to p...