Task library CTIMER
Project scope 10 tickets / 3 phases
Total focused work estimate 22h 45m + setup
Suggested stack TypeScript · Fake clock · Vitest Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with CTIMER-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice timer semantics, cancellation and bounded scheduling.
What the team gains Inspect predictable edge resource use and honest execution status.
Before you start Implement injected wall and monotonic clocks. Create synthetic jobs with controllable completion and failure. Delivery agreement Use deterministic clock advancement; emulator timing does not qualify physical realtime behavior.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Separate elapsed deadlines from calendar schedules.
PHASE 2 Prevent overlap and stale callbacks.
PHASE 3 Handle restart and overload deliberately.
Define time semantics Separate elapsed deadlines from calendar schedules.
CTIMER-101 Entry ticket; project setup still required CTIMER-102 Depends on CTIMER-101 CTIMER-103 Depends on CTIMER-101, CTIMER-102 Control job execution Prevent overlap and stale callbacks.
CTIMER-104 Depends on CTIMER-103 CTIMER-105 Depends on CTIMER-103, CTIMER-104 Estimated field mix
Embedded and edge 70% Performance engineering 30% CTIMER-106 Depends on CTIMER-104, CTIMER-105 Estimated field mix
Embedded and edge 70% Site reliability 30% CTIMER-107 Depends on CTIMER-103, CTIMER-106 Estimated field mix
Embedded and edge 70% Storage systems 30% Recover scheduler state Handle restart and overload deliberately.
CTIMER-108 Depends on CTIMER-105, CTIMER-107 Estimated field mix
Embedded and edge 60% Performance engineering 40% CTIMER-109 Depends on CTIMER-101, CTIMER-108 Estimated field mix
Embedded and edge 50% Performance engineering 30% Site reliability 20% CTIMER-110 Depends on CTIMER-107, CTIMER-109 Estimated field mix
Developer tooling 50% Embedded and edge 50% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.