Team Best Practices
Twenty practices that keep Rust teams fast, aligned, and kind to future hires.
//
Busca en todas las páginas de la documentación
Twenty practices that keep Rust teams fast, aligned, and kind to future hires.
Time-to-first-PR under five days: Measure onboarding; fix tooling blockers immediately.
Buddy system week one: Daily 15-minute check-in, not passive Slack channel.
Single toolchain pin: rust-toolchain.toml matches CI MSRV 1.97.0.
Onboarding doc in repo: docs/onboarding.md is canonical, not wiki-only.
Toolchain checklist completed day 1: Before assigning feature work.
Codebase orientation diagram: Every hire draws request flow; buddy validates.
Conventions doc linked in PR template: Reduces repeated style comments.
Review checklist for soundness: unsafe, unwrap, blocking async, SQL injection.
CI mirrors local hooks: fmt, clippy -D warnings, test, --locked build.
Small first merged PR: Proves pipeline works for this human.
Log onboarding gaps as doc PRs: Same-week fixes for next hire.
ADR for Rust platform choices: Tokio, sqlx, error strategy, workspace layout.
rust-rules or team rules crate/docs: Codify repeated review comments.
Quarterly dependency hygiene sprint: cargo update, advisories, deny policy.
Incident learnings update cookbooks: Link postmortem to troubleshooting pages.
Agent skills documented: When to invoke Axum, async, unsafe review skills.
No heroics on call: Runbooks in repo; shadow before solo rotation.
Explicit MSRV bump process: RFC or ticket with CI and consumer impact.
Celebrate refactors that delete code: Negative LOC is a team win.
Retro onboarding after every hire: Update checklists within one week.
Two engineers plus one planned hire justifies lightweight ADRs.
Recorded architecture walks, written defaults, async-friendly review SLAs.
Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.
Revisado por Chris St. John·Última actualización: 16 jul 2026