Task library BLOADSHED
Project scope 10 tickets / 3 phases
Total focused work estimate 27h + setup
Suggested stack TypeScript · HTTP · Redis 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 BLOADSHED-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice overload behavior, admission control, and fair performance experiments.
What the team gains Create predictable failure and degradation behavior under declared capacity constraints.
Before you start Build a bounded local service and synthetic open-loop workload generator with controllable dependency delays. Delivery agreement Deliver local controls and measurements; no live load generation.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define essential outcomes and bounded workload assumptions.
PHASE 2 Limit queues and isolate optional work.
PHASE 3 Compare policies and verify return to normal operation.
Characterize overload Define essential outcomes and bounded workload assumptions.
BLOADSHED-101 Entry ticket; project setup still required Estimated field mix
Site reliability 60% System design 40% BLOADSHED-102 Depends on BLOADSHED-101 Estimated field mix
Performance engineering 70% Quality engineering 30% Protect service capacity Limit queues and isolate optional work.
BLOADSHED-103 Depends on BLOADSHED-102 Estimated field mix
Site reliability 40% Platform engineering 40% Performance engineering 20% BLOADSHED-104 Depends on BLOADSHED-101, BLOADSHED-103 Estimated field mix
Site reliability 40% Performance engineering 30% Networking 30% BLOADSHED-105 Depends on BLOADSHED-103, BLOADSHED-104 Estimated field mix
Backend 40% Site reliability 30% Networking 30% BLOADSHED-106 Depends on BLOADSHED-103 Estimated field mix
API design 50% Site reliability 50% BLOADSHED-107 Depends on BLOADSHED-103, BLOADSHED-104 Estimated field mix
Performance engineering 40% Platform engineering 40% Site reliability 20% Validate recovery Compare policies and verify return to normal operation.
BLOADSHED-108 Depends on BLOADSHED-102, BLOADSHED-105, BLOADSHED-106, BLOADSHED-107 Estimated field mix
Performance engineering 60% Site reliability 40% BLOADSHED-109 Depends on BLOADSHED-108 Estimated field mix
Site reliability 60% Platform engineering 40% BLOADSHED-110 Depends on BLOADSHED-109 Estimated field mix
Site reliability 70% API design 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.