# original

This is intentionally messy starter code.

## Why it is messy

- mixes file I/O, business rules, time, and logging in one method
- uses raw strings and generic objects instead of stronger primitives
- hard-codes reward logic inline
- depends directly on `new Date()` and `fs`
- mutates loaded state directly

## Suggested drill targets

- characterize current completion behavior
- break the file-system or clock dependency with a seam
- extract the points or badge decision into a pure function