Task library ABOOK
Project scope 10 tickets / 3 phases
Total focused work estimate 31h 30m + setup
Suggested stack TypeScript · PostgreSQL · REST 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 ABOOK-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice resource allocation, interval conflicts and durable workflows.
What the team gains Review scheduling correctness and recovery before exposing scarce capacity.
Before you start Build synthetic technicians, slots and booking records. Use an injectable clock and separate clients for concurrency probes. Delivery agreement Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Make time and availability rules unambiguous.
PHASE 2 Handle simultaneous actions and durable transitions.
PHASE 3 Reconcile state and explain cancellations.
Define availability Make time and availability rules unambiguous.
ABOOK-101 Entry ticket; project setup still required ABOOK-102 Depends on ABOOK-101 Estimated field mix
Backend 50% Database engineering 50% ABOOK-103 Depends on ABOOK-101, ABOOK-102 Protect reservations Handle simultaneous actions and durable transitions.
ABOOK-104 Depends on ABOOK-102 Estimated field mix
Database engineering 60% Backend 40% ABOOK-105 Depends on ABOOK-104 Estimated field mix
Backend 60% Database engineering 40% ABOOK-106 Depends on ABOOK-104, ABOOK-105 Estimated field mix
Database engineering 60% Backend 40% ABOOK-107 Depends on ABOOK-105 Operate the calendar Reconcile state and explain cancellations.
ABOOK-108 Depends on ABOOK-105, ABOOK-106 Estimated field mix
Backend 50% Database engineering 30% Site reliability 20% ABOOK-109 Depends on ABOOK-106, ABOOK-107 Estimated field mix
Privacy engineering 50% Backend 30% API design 20% ABOOK-110 Depends on ABOOK-105, ABOOK-108, ABOOK-109 Estimated field mix
Quality engineering 40% Backend 30% Distributed systems 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.