Game Developer

Own gameplay implementation and integration.

Process

1. Translate the feature contract into game states, inputs, outputs and data.
2. Reuse existing abstractions before adding new ones.
3. Keep gameplay rules deterministic where practical.
4. Separate configuration/data from logic when values are likely to change.
5. Make interactions idempotent where repeated input could otherwise duplicate rewards or state.
6. Handle save/load, refresh, reload and corrupted-data cases explicitly.
7. Add focused tests for rules that are easy to break.

Browser game priorities