Task library BCOST
Project scope 10 tickets / 3 phases
Total focused work estimate 25h + setup
Suggested stack TypeScript · S3-compatible storage · CSV 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 BCOST-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice cost attribution, lifecycle modeling, and safe retention controls.
What the team gains Produce reviewable storage-cost options with recovery and data-retention consequences.
Before you start Create synthetic object inventories and a local object-store double; author fictional unit prices as explicit assumptions. Delivery agreement Deliver an offline cost model and local policy rehearsal; delete no real cloud objects.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Describe objects, ownership, and cost assumptions.
PHASE 2 Evaluate retention and transfer controls safely.
PHASE 3 Compare options and expose uncertainty.
Attribute storage Describe objects, ownership, and cost assumptions.
BCOST-101 Entry ticket; project setup still required Estimated field mix
Data engineering 60% Cloud infrastructure 40% BCOST-102 Depends on BCOST-101 Model lifecycle changes Evaluate retention and transfer controls safely.
BCOST-103 Depends on BCOST-101 Estimated field mix
Storage systems 50% Cloud infrastructure 30% Site reliability 20% BCOST-104 Depends on BCOST-103 Estimated field mix
Cloud infrastructure 40% Storage systems 40% Security 20% BCOST-105 Depends on BCOST-102, BCOST-103 Estimated field mix
Cloud infrastructure 50% Storage systems 30% Site reliability 20% BCOST-106 Depends on BCOST-104 Estimated field mix
Security 50% Storage systems 30% Cloud infrastructure 20% BCOST-107 Depends on BCOST-102 Estimated field mix
Performance engineering 40% API design 30% Security 30% Review savings proposals Compare options and expose uncertainty.
BCOST-108 Depends on BCOST-105, BCOST-106, BCOST-107 Estimated field mix
Cloud infrastructure 50% Performance engineering 30% Storage systems 20% BCOST-109 Depends on BCOST-108 Estimated field mix
Cloud infrastructure 60% Site reliability 40% BCOST-110 Depends on BCOST-109 Estimated field mix
Site reliability 50% Cloud infrastructure 30% Storage systems 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.