CST 338 Week 1
Solving the CodingBat challenges required a structured approach: learning the problem first, breaking it down into logical steps, and finally coding up a solution based on Java's in-built functions. Planning was optimal, while blithely firing code at the problem created inefficiencies and unnecessary complexity. Using replaceAll() for list modifications and streams for non-destructive changes improved my solutions and made them more efficient. Edge conditions like empty lists or single-character strings sometimes led to unexpected crashes, requiring multiple attempts to sort out my code. Most issues required 1-2 attempts, but tough ones, like ensuring "xyz" wasn't followed by a period, required 4-5 attempts. This exercise as a whole reminded me of the importance of thinking ahead, using Java's functional programming features, and recognizing patterns in order to debug more efficiently.
Comments
Post a Comment