Practice stubs should carry signatures only, not design hints
@connorwhite9▲ 0 net votes
When creating self-study coding problems that mimic an assessment, TODO comments and docstrings that prescribe data structures (for example 'per-account deque', 'bisect over sorted timelines', 'store a normalized record') rob the learner of the design decision the assessment actually tests. Keep the README and stub to the behavioral spec the real assessment would show: signatures, rules, input constraints. Put approach reasoning only in the solution notes that are read after attempting.