Driving Rusta course in Rust judgment
Score 0

Driving Rust

Eight levels. Each one ends with a sentence you can say to a coding agent that you could not say before — and a diagram you could redraw on a whiteboard.

Read under 60 wordsLook at the pictureSay how sure you areCommitWatch what your call causes

The route

Levels 1–5 are Rust judgment. Levels 6–8 are Solana and tokens. Nothing is locked — but they build.

The map

Level 115–20 min

The Bargain

What Rust charges, what it pays, and when the borrow checker is right to refuse your design.

Not started
Level 220 min

When Rust, When Not

The decision surface, drawn against your own stack. Aimed at a belief you hold; be ready to lose it.

Not started
Level 320–25 min

The Shape of a Good Rust Codebase

Errors as architecture, traits versus enums, newtypes, illegal states, and the smells an agent will hand you.

Not started
Level 425 min

The Questions Your Agent Will Ask

Owned or borrowed, sync or async, dyn or generic, channel or lock, one crate or many. What each answer commits you to.

Not started
Level 520 min

The Boundary

PyO3, WASM, CLI, sidecar. Sizing the carve is the whole skill: too small and marshalling eats the win, too large and you rewrote the system.

Not started
Level 620 min

Accounts, Not Objects

Solana’s model as it actually is: stateless code over accounts somebody paid for. Where the Postgres analogy breaks.

Not started
Level 720–25 min

Do You Need a Token?

The honest filter: what a token buys that a Postgres row does not, applied to your real projects. Negative verdicts included.

Not started
Level 825 min

Architecting the Program

Signers, validated accounts, arithmetic, upgrade authority, and the capstone: the brief you would hand a Rust agent.

Not started

The ledger

Every concept this course covers, the level that teaches it, and the one-line decision rule it produces. Rules unlock as you clear levels. This is the page to keep.

ConceptLevelDecision rule
When Rust
The band: when a project wants a Rust elementL2
Rust already in your Python stackL2
The anti-cases: IO-bound services, résumé-driven Rust, no maintainerL2
Ownership
Move semanticsL1
Borrowing as a design critic, not a ruleL1
Clone / Copy and the cost of cheap duplicationL1
Owned type vs borrowed view (String / &str)L4
Lifetimes as an API commitmentL3
Modelling
Traits vs enums — open vs closed extensionL3
Trait objects vs genericsL4
The newtype habitL3
Making illegal states unrepresentableL3
Failure
Option and Result — absence and failure in the type systemL3
Error architecture: thiserror at library edges, anyhow at application edgesL3
unwrap / expect as a load-bearing claimL3
Panic vs recoverable, and who decidesL3
Concurrency
Send and SyncL4
Arc<Mutex<_>> vs channels vs actorsL4
Sync vs async and the colour problemL4
"Fearless concurrency" is a compile-time claimL4
Boundaries
Crates and workspaces as module boundaries with teethL4
The public API surface is the thing to reviewL3
unsafe — meaning, legitimacy, and its real costL5
FFI: PyO3, WASM, CLI, sidecar — sizing the boundaryL5
Project economics
Zero-cost abstraction — what it promisesL4
Compile time as a project-management costL4
Dependency weight, semver and MSRVL3
What the type system lets you not testL3
Driving agents
One error strategy chosen up frontL3
Workspace boundaries as the unit of delegationL4
clippy and rustfmt as enforced conventionsL3
You review the public surface; the rest is detailL3
Solana: the model
Accounts, not objectsL6
Rent and rent-exemptionL6
Account sizing and reallocL6
Determinism: no floats, no wall clock, no networkL6
Solana: authority
SignersL8
Program-derived addresses and program-owned authorityL6
Mint authority and freeze authorityL7
Upgrade authority — keep or dropL8
Solana: composability
Cross-program invocationL8
The instruction surface as a public APIL8
Compute-unit and transaction-size limitsL6
Oracles and off-chain truthL6
Solana: tokens
SPL Token vs Token-2022L7
Decimals and supply as permanent decisionsL7
The four things a token buys, each tested against a database rowL7
Solana: failure modes
Missing signer checksL8
Unvalidated accountsL8
Arithmetic overflowL8
ReinitialisationL8
Audit economicsL8

Your licence

It updates as you go. Calibration is the number that matters: how well your confidence matches your accuracy.

Rank comes from levels cleared. Calibration comes from the stake you set before each call — betting Certain and being wrong costs nearly double, and a hunch that pays is worth less.

Everything lives in this browser's storage. Nothing is uploaded anywhere.