There's always Simon Tatham's Portable Puzzle Collection. Most of them take about 5 minutes to solve, which can fill in the time when you're waiting for something else.
Confirming a bug should mean creating a comprehensive set of tests that fail until the bug is fixed. This has two advantages.
First, it means the developer will not overlook something. If a bug takes a long time to fix, the developer may forget to do everything, that is, to do all the side cases. Having pre-written tests increases the likelihood of a complete fix.
Second, the tests can be added to the official test suite. That way, any future development will not re-introduce the bug.
Authored Comments
There's always Simon Tatham's Portable Puzzle Collection. Most of them take about 5 minutes to solve, which can fill in the time when you're waiting for something else.
https://www.chiark.greenend.org.uk/~sgtatham/puzzles/
Confirming a bug should mean creating a comprehensive set of tests that fail until the bug is fixed. This has two advantages.
First, it means the developer will not overlook something. If a bug takes a long time to fix, the developer may forget to do everything, that is, to do all the side cases. Having pre-written tests increases the likelihood of a complete fix.
Second, the tests can be added to the official test suite. That way, any future development will not re-introduce the bug.