+ usaco bronze: (basic) complete search + +
++ Implementation wise, two-pointers boundary conditions trip me up. + Spend more time on problems statements and go for the easiest + solution. +
++ cowntact tracing was the absolute + worst. I misinterpreted the problem constraints (i.e. thought hoof + shakes in last \(k\) time units, not last \(k\) shakes) then failed + to identify all parts of my code that had erroneous logic. + Then I did this 3 times over. +
++ Once a crux observation/error is realized, reexamine all parts of + the code/plan and see how they're impacted. ++
+ usaco bronze: simulation + +
++ These problems are relatively easy but exposed my poor + implementation abilities. A lack of implementation implies a lack of + understanding. Specifically, I encountered the following problems: +
+-
+
- + Base cases and calculations—initializing state and + transitions along with exit conditions. Oftentimes I simply + misinterpret the simulation (take your time), fail + to outline specific criteria, and don't walk through edge cases. + For example, + speeding ticket + took me forever (>20 minutes) to model the ideal \(O(n)\) + solution. Initial states and base cases took me forever, when I + should've just modeled the transitions explicitly, considering + start/end states separately rather than getting overwhelmed by + everything at once. + +
- + Overcomplicating/wasting time on solutions that aren't + necessitated by lax constraints. I further get confused (although + my black-box ability is improving) on problems with many moving + parts. + +