domains / families / research / fast-writing-style

fast-writing-style

separate

Use when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the storage cost it changes (write amplification, tail latency, endurance, crash consistency), double-blind wording, and disciplined use of the USENIX two-column page budget.

When to use

• revising a USENIX FAST paper
• stating a storage contribution on the first page
• framing evaluation as storage cost changes
• ensuring double-blind wording
• managing the USENIX two-column page budget
• auditing storage metrics and device evidence
• checking crash consistency and durability invariants

When not to use

• general systems demo papers
• throughput-bar benchmarks without storage cost framing

Skill page

Source