8000 GitHub - arkgast/rustylab · GitHub
[go: up one dir, main page]

Skip to content
arkgastPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

< 10BC8 svg data-component="Octicon" aria-hidden="true" focusable="false" class="octicon octicon-eye mr-2" viewBox="0 0 16 16" width="16" height="16" fill="currentColor" display="inline-block" overflow="visible" style="vertical-align:text-bottom">0 watching

Forks

Latest commit

 

History

72 Commits

Folders and files

Repository files navigation

RustyLab

A structured, deadline-driven path from re-learning Rust to senior Rust engineering, and from there to blockchain engineering on Polkadot, Solana and Stellar.

Every concept is learned the same way: predict what a snippet prints, run it and see the gap, then solve katas and run them, pass the gate, explain your answers.

The plan at a glance

  • 17 stages, 83 tasks, 5 phases, plus a closed-book exam at the end of every stage
  • 3 focused hours a day, Monday to Saturday; Sunday is spaced repetition
  • 189 study days (~567 h); dates and progress are local, in ROADMAP.md (see Setup)
  • A task is done only when its review passes: automated gate, rubric ≥ 80, oral check
Phase Stage You will be able to...
I · Fluency 1 Rust refresh write basic programs from memory; see moves and borrows
2 Collections, closures & iterators process data with pipelines; pick deterministic collections
3 Error handling design typed errors; never panic on bad input
4 Traits & generics model domains with traits, newtypes and associated types
II · Depth 5 Lifetimes & memory reason about where data lives and for how long
6 Crates, API design & testing ship library-quality APIs with property tests and benchmarks
7 Concurrency write race-free parallel code; prove parallel equals sequential
8 Async build tokio services with timeouts, cancellation and backpressure
9 Macros read and write declarative and procedural macros
III · Systems 10 Unsafe, no_std & WASM write sound unsafe code; run sandboxed WASM contracts
11 Encoding & cryptography build canonical codecs, Merkle proofs and signed transactions
IV · Protocol 12 A runtime from scratch build a deterministic blockchain runtime end to end
13 Execution models & security exploit and fix the classic smart-contract bugs; audit your own code
V · Chains 14 Polkadot SDK write, test, benchmark and migrate FRAME pallets
15 Solana write native and Anchor programs; test them with LiteSVM / Mollusk
16 Stellar & Soroban write and deploy Soroban contracts
17 Senior capstone read production chain code, contribute upstream, defend a final project

Setup

Needs Rust 1.89 and Python 3. Dates and progress are personal, so none of them are in git: ROADMAP.md and .study/ are gitignored and exist only on your machine. Create them once, with your start date:

cargo x init 2026-11-09    # schedule the course from this date
cargo x plan               # start, proposed finish, hours per day, intensity
cargo x status             # what is due next

What cargo x init does

cargo x init [--force] [YYYY-MM-DD] reads the task headings and day counts in curriculum/stage-*.md and schedules every task on study days (Monday to Saturday, 3 hours each) from the start date. A Sunday start moves to Monday. It writes:

File Contents On a rebuild
ROADMAP.md every row ⬜ todo with its due date, the progress block replaced
.study/plan.json start, proposed finish, study days, intensity replaced
.study/session.md, .study/queue.md, .study/log/ blank tutor state created only if missing, never overwritten

Without a date it reuses the start in .study/plan.json, or today if there is no plan yet. Your journals, code and tutor state are never touched.

Changing the start date

  • Nothing started yet (every row ⬜): cargo x init <new date>.
  • A row has progress (🔨, ✅ or 🔁): init refuses with ROADMAP.md has progress; refusing to rebuild it. cargo x init --force <new date> rebuilds anyway and discards every status, done date, score and the slip count. Use it only before real progress, for example when /study marked the first task 🔨 but you want to start on another day. After it, /study marks the current task started again.
  • Real progress and you are behind: do not rebuild. Late finishes already shift every later row (see the slip policy in curriculum/README.md).

The same rules apply after editing the stage specs (adding a task, changing its days): rebuild with init while nothing has started.

Moving to another machine

Copy ROADMAP.md and the whole .study/ folder (plan, session cursor, recall queue, tutor logs): they exist nowhere else. The schedule always assumes 3 hours Monday to Saturday; plan.json records that, but changing it there does not reschedule anything.

Commands

cargo x is this repo's npm run: an alias in .cargo/config.toml for the small xtask crate. cargo x help lists everything.

Command What it does
cargo x status What is due next and how late you are
cargo x plan Your dates and intensity
cargo x probe Rerun the tutor's snippet (--release for the release profile)
cargo x play Run your playground, scratch/src/bin/playground.rs
cargo x run S1-T1 Run your katas (short form cargo x S1-T1; program args after --)
cargo x gate S1-T1 fmt, clippy, fixed tests, your tests, runner build
cargo x journal S1-T1 Answer the journal step by step; stop anytime, rerun to continue
cargo x after 3 The date 3 study days from today

Probe or playground? The probe belongs to the tutor and is overwritten by every probe, so anything you want to keep goes in the playground, which the tutor never overwrites. Both live in the gitignored scratch/ crate, created on first use, so a broken experiment can never fail your gate.

A study day

/study                      # opens today: 2-3 recall questions, then probes or build
                            #   a probe: predict, it runs, you see the gap
cargo x probe        # rerun the tutor's snippet after you change it
cargo x run S1-T1        # your katas (⏳ = todo!())
cargo x play   # your scratch file
cargo x gate S1-T1       # fmt, clippy, fixed tests, own tests
cargo x journal S1-T1       # guided, one question at a time; the close message seeds it
/review S1-T1               # oral check + rubric; the only thing that moves the roadmap
/study close                # or just say "done": logs the day, queues tomorrow's recall

In chat: hint · skip · show me (costs points) · break · done

Sunday: /study runs only repetition. Rest 10-20 minutes after every close; sleep is where today's misses become tomorrow's recall.

Full rules, rubric and integrity policy: curriculum/README.md.

Repository layout

Path What it is
ROADMAP.md Local, gitignored tracker: status, due dates, scores (written only by scripts/roadmap.py: init, /study, /review)
scratch/ Local, gitignored crate: the tutor's probe and your playground
xtask/ The cargo x command
curriculum/ Stage specs and the rules of the game
tasks/ Your exercises (src/), runners (examples/), fixed gate tests (tests/)
labs/ Separate crates for later stages (async, macros, WASM, runtime, chains)
journal/ Your notes and checkpoint answers per task
.study/ Local, gitignored: your plan, today's session, the recall queue, per-task logs (created by cargo x init, then written by /study and /review)
scripts/ run.sh, gate.sh, roadmap.py, clock.sh (session clock the tutor checks for the break cue)
docs/ ADRs, audits and write-ups you produce along the way

Earlier experiments (calculator, guessing_game, state_machine) are archived on branch archive/legacy-projects.

Rust toolchain: 1.89 (edition 2024).

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

0