Task library CLIVE
Project scope 10 tickets / 3 phases
Total focused work estimate 22h 45m + setup
Suggested stack TypeScript · Server-sent events · PostgreSQL adapter · React 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 CLIVE-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice event projection, replay and freshness communication.
What the team gains Inspect whether dashboards remain trustworthy through network interruptions.
Before you start Create synthetic incident revisions and a local append-only event stub. Provide controllable disconnect, replay and retention fixtures. Delivery agreement Use local fixtures; this board is not an emergency-response system.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define event identity and projection.
PHASE 2 Make replay and mutation coherent.
PHASE 3 Handle slow clients and explain freshness.
Specify live events Define event identity and projection.
CLIVE-101 Entry ticket; project setup still required Estimated field mix
Real-time systems 60% Data engineering 40% CLIVE-102 Entry ticket; project setup still required Estimated field mix
Accessibility 70% Frontend 30% CLIVE-103 Depends on CLIVE-101, CLIVE-102 Estimated field mix
Real-time systems 60% Distributed systems 40% Recover transport gaps Make replay and mutation coherent.
CLIVE-104 Depends on CLIVE-103 Estimated field mix
Real-time systems 60% Networking 20% Distributed systems 20% CLIVE-105 Depends on CLIVE-104 Estimated field mix
API design 50% Real-time systems 30% Storage systems 20% CLIVE-106 Depends on CLIVE-104, CLIVE-105 Estimated field mix
Distributed systems 50% Real-time systems 30% Database engineering 20% CLIVE-107 Depends on CLIVE-103, CLIVE-106 Estimated field mix
Frontend 60% Real-time systems 40% Operate bounded streams Handle slow clients and explain freshness.
CLIVE-108 Depends on CLIVE-106 Estimated field mix
Performance engineering 50% Real-time systems 30% Site reliability 20% CLIVE-109 Depends on CLIVE-105, CLIVE-108 Estimated field mix
Frontend 60% Real-time systems 40% CLIVE-110 Depends on CLIVE-109 Estimated field mix
Privacy engineering 60% Real-time systems 20% Site reliability 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.