trajanmcgill / engineerstudy Goto Github PK

Base repeat frequency on time taken to answer?
Define "repeat" as exact repeat? Or repeat of base configuration but with different details?

For instance:

• Sticking to common real-world scenarios vs. adding unusual ones
• Yelling at you to hurry up
• Throwing more questions at you (queuing them up) while you're working on existing ones
• Component-by-component walk-through mode

Fails on Linux or other case-sensitive file systems.

(no crosslays to floor 6, etc.)

Initial approach: come up with a random order but ask all questions before repeating any

• Basic walk-through for simple scenarios
• Work for all scenarios without splits
• Fix whatever got broken about switching quizzes
• Handle section breaks
• Handle scenarios with splits
• Include section breaks in all appropriate places
• Handle all the quizzes

Currently only allows a rounded answer up to 0.5 off of the true value. Instead allow rounding either up or down from any value between two whole numbers.

Right now code errors tend to produce an infinite loop, because of how the failures lead to restarting the quiz. This makes debugging hard and UI experience inscrutable when an error sneaks in.