Codeforces Short Round 01¶
This pack is for Codeforces-style short-round shipping: one fast banker, one compact constructive slot, one hack-sensitive feasibility slot, and one optional late model.
Who This Is For¶
Use this pack if:
- you already know the core families here in isolation
- your main Codeforces losses come from slow shipping or weak anti-hack habits
- you want a short, repeatable block that feels closer to a live CF round than a long archive grind
Entry Gate¶
Try this pack only if these already feel like review:
- Constructive
- Prefix Constraints
- 2-SAT for the optional late slot
At minimum, these should no longer feel like first exposure:
Pack Shape¶
- Type:
Codeforces short-round shipping drill - Topic mix:
constructive + feasibility + adversarial checking + late-slot graph modeling - Problems:
4 - Suggested time:
2-2.5 hours
Topics Under Test¶
- banker-first ordering in a short round
- fast construction without overexplaining the entire proof to yourself
- anti-hack discipline on feasibility-heavy code
- knowing when to park an optional late slot instead of burning the whole round on it
Suggested Order¶
| Slot | Problem | Topic | Why it is here |
|---|---|---|---|
| 1 | Same Parity Summands | constructive banker |
Fast first ship: small statement, quick parity split, and low setup cost. |
| 2 | Build the Permutation | constructive / witness building |
Typical CF mid-early slot: easy to overcomplicate if you do not lock one clean construction fast. |
| 3 | Prefix Sum Addicts | feasibility / anti-hack |
Strong slot for practicing boundary checks, impossible cases, and “looks right on samples” traps. |
| 4 | The Door Problem | 2-SAT |
Optional late slot: compact graph transform, but only worth opening after the earlier ships are stable. |
How To Run It¶
- spend
8-10 minutesreading all4slots - classify each as:
ship nowone idea awaypark- solve in the suggested order unless you can justify swapping
1and2 - after each supposedly-finished slot, spend
3-5minutes on one anti-hack pass: - smallest legal case
- impossible or parity boundary
- duplicate / degenerate family
- do not open slot
4if slot3still has a vague correctness story
This pack is about shipping and hardening, not about starting the fanciest slot earliest.
Allowed Refreshers¶
Debrief¶
After the pack, log:
- first slot that should have shipped earlier
- first bug or fear that was really an anti-hack miss, not a theorem miss
- whether slot
4was opened too early, too late, or at the right time - one concrete next action:
- topic revisit
- implementation clinic
- constructive / validator-first clinic
- upsolve worksheet
Go Back Next¶
- if slot
1or2was weak, revisit Constructive ladder - if slot
3was weak, revisit Prefix Constraints ladder and Anti-Hack Workflow - if slot
4was weak, revisit 2-SAT ladder - if the whole block felt strategically bad, reopen Codeforces Playbook