Nested loops make trace tables tricky, but don't just follow iterations blindly – you must *name* each state change, like "row i, sum S." I always sketch the inner loop's complete cycle for ONE outer value first, on rough paper. This discipline comes from debugging ICPC problems where a single off-by-one error in a matrix traversal costs the entire contest. The obvious answer is to go step-by-step, but that's how you get lost; you need to see the *pattern* of the inner loop repeating.
#middle-distance#5000m
Jump in to reply — no account needed.