unrust

Help center

How to use Unrust

Unrust gives you a timed, unassisted snapshot of six core coding skills, plus an adaptive loop to practice them. Here's how each piece works, and how to reach us.

The four experiences

1 · The Diagnostic

A short, unassisted (AI-off) measurement — about 14 minutes, one or two questions per skill dimension. It produces a six-spoke profile and a single headline where any one rusty spoke pulls the number down. It's longitudinal: retakes rotate to fresh questions of the same shape, so your trend is comparable over time without being memorizable. You can take it anonymously and claim the result when you sign up.

2 · Practice

The adaptive loop that supports regular practice. Spaced repetition surfaces what is due — either a mixed daily queue across all dimensions, or a focused workout to work on one category. Practice is walled off from the diagnostic, so training never contaminates your measurement.

3 · Library

Browse the entire drill bank by category, difficulty, language, or name, preview the code, and attempt anything on demand — no schedule required.

4 · Skills & Mastery

Every skill sits on a ladder — Cold → Warming → Solid → Sharp — that decays if you stop and is built so it can't be farmed: it takes spaced repetitions across distinct drills to climb, not one memorized answer repeated.

The six skills we measure

Recall

Reconstruct code from memory — the API, the idiom, the incantation.

Tracing

Predict what a snippet prints by executing it in your head.

Find the Flaw

Spot the one defect between a function and its stated intent.

Debugging

Locate the broken line and name the root cause.

Idiom / Quality

Choose the cleanest, most idiomatic equivalent.

AI-slop Detection

Catch the plausible-but-wrong line an AI would happily write.

Languages

Set a default language for your account — JavaScript, TypeScript, or Python today, with more on the way. It filters the whole experience: diagnostic, practice, and library all reframe to your language, so you can do everything without ever being ambushed by a language you don't work in.

Your metrics are tracked per language. Switch to a language you've never practiced and it starts at zero; switch back and your earlier mastery is restored untouched — your Python rust and your JavaScript rust are measured honestly and separately. On any drill offered in more than one language, a per-question dropdown lets you answer it in a sibling language, crediting the one you actually used.

Scoring and editorial method

Who publishes the material

Unrust maintains the product and publishes these guides. Authorship is attributed to Unrust rather than an unnamed expert panel. Software may assist drafting and checks; that is not independent expert validation. Send corrections or questions about an example to support@unrust.dev.

How examples are checked

The worked examples are original public teaching material. Every published language snippet and developer use case has executable checks for its displayed observations or before-and-after behavior under the stated input assumptions. Primary language references are linked where relevant. Passing these checks establishes the example's behavior, not the reliability of an assessment instrument.

What the diagnostic score represents

Short tasks sample recall, tracing, debugging, reading against a contract, idiom and review of plausible code. Responses are graded automatically against each task's fixed answer key; no open-ended written explanations are collected or judged. Per-skill results are combined with a mean that gives weaker measured areas more influence. Missing measurements and uncertain results should be read as such, not filled with a claimed ability score.

Calibration and limits

Band boundaries and weighting choices are provisional product decisions. This page does not claim a completed independent validation study or a representative population norm. A sitting cannot establish that AI caused a result, distinguish decay from unfamiliarity, or predict interview success. Compare compatible retakes in the same language with their uncertainty; practice results are kept separate from the diagnostic trend.

Privacy and measurement

We use Umami analytics to understand which public resources lead to completed diagnostics, practice and paid access. A session cookie keeps only the first approved public landing path and a broad source such as search or direct. Search terms, answers, source code, email addresses and payment credentials are excluded from these analytics events. So is every query string, except the campaign labels on a link you followed (utm_source and the like), which are kept only as plain lowercase tags. Your browser sends no account identifier with these events; events our server records for a signed-in account may use a hashed account identifier to group them without sending the account ID itself.

On page visits we may also measure loading speed (such as LCP), responsiveness (INP) and visual stability (CLS). A sample holds the metric values and the page path, and may include a mobile or desktop category, the navigation type and a measurement ID that is new for each metric and page visit. That ID only helps avoid counting one measurement twice; it is not a persistent account identifier. We do not collect the underlying element selectors or detailed performance entries.

On our public pages (the home page, pricing, help, guides, the blog and the like) we may also keep heatmap data and a session replay for some visits made while signed out. Heatmap data is where on the page a click landed and how far the page was scrolled. A replay is how the page looked, where the pointer moved and what was clicked; whatever is typed into a field is masked in the browser before anything is sent, and no replay is made while the page's address carries anything other than campaign labels. The diagnostic, results, sign-in, payment, account, practice and support pages are never recorded, and neither is any page while you are signed in. Replays and heatmaps are kept on our own Umami instance.

The chat on our public pages takes a message without an account. We keep the message, the page it was sent from and a random ID in a cookie on your browser, so you can read our reply there; never an IP address, device details or an email address. The chat is never part of a replay. If you sign in, the conversation moves to your account. A conversation we've answered closes after 30 days without a reply, and a closed one is deleted 90 days after it closes.

All of this respects Do Not Track, Global Privacy Control and the browser's Umami opt-out preference, and automated browsers are not measured. Payment analytics preserve the privacy choice received at checkout and report a purchase only after server confirmation, with its plan and price and never a wallet address or transaction. These measurements are best-effort and may be absent when tracking is blocked. Contact support@unrust.dev with questions about your data.

Frequently asked

Is it really unassisted?

Yes — the diagnostic is designed for an AI-off condition. It is a mirror, not a gate: the point is to see how your unassisted performance looks today.

What do the score bands mean?

They group performance in this sitting into provisional product bands. These are not validated population percentiles or hiring grades. Read comparable retakes with their uncertainty, rather than treating a single number as a verdict.

Does practice change my diagnostic score?

No. Practice and the diagnostic are deliberately separated. Practice moves your per-skill mastery; only the diagnostic moves the longitudinal trend.

How do languages work?

You pick a default language for your account (JavaScript, TypeScript, or Python today; more coming). It filters the whole experience, and your metrics are tracked per language — switching to a new language starts it fresh and switching back restores your earlier progress untouched.

Can I answer a question in a different language?

On any drill that exists in more than one language, a dropdown lets you answer that specific question in a sibling language — and it credits the language you actually answered in.

Why did a right answer earn 0 XP?

Most often the skill wasn't ready for review yet, and that includes a skill that already earned XP in an earlier session today. Spacing is what builds memory, so XP follows it. The note under the answer says why, and when the skill wasn't ready it shows the day it counts again.

Why does a wrong answer earn XP?

XP records that you showed up for a rep that was ready, not whether you got it right. Accuracy still shows on the done screen, and a wrong answer still updates your mastery.

Do I have to practise every day?

No. Each week, two days off are free rest days, and a third uses a banked streak freeze. Five forge days out of seven meets the week.

I'm going away for a while. What happens to my streak?

Plan a break on your streak page: up to 28 days at a time, starting tomorrow at the earliest. Break days never count against you.

Does the diagnostic count toward my streak or XP?

No. The diagnostic is a measurement and stays outside the game.

What does the number of forge days mean?

It's the number of days you forged in your current run. Rest days and freezes keep the run going without adding to the number.

Can I turn the game off?

Yes: Settings → Game & celebrations → Game layer → Off, or Minimal for just the week ring. Practice works exactly the same.

My run ended. Can I repair it?

Yes. If your first forge day after the end falls on one of the next two days, make it a double session: 6 reps that count, or every rep that could count when fewer were ready. The run then carries on with its count, and the days in between keep a seam on your calendar. A first forge day with fewer reps starts a new run as usual. One repair every 14 days, and a protected day never costs you one.

What are badges?

Marks of effort from your streak record: your first, fourth and twelfth met weeks, runs of 7, 30, 100 and 365 forge days, and two surprises. They come from the same record as your calendar, so they never disagree with it, and they earn no XP.

What does a shared card show?

A shared card shows your forge days or a badge and nothing else. Anyone with the link can see it for about a year.

A day on my calendar looks wrong.

Tap it to see the reason. If it still looks wrong, email support@unrust.dev and we'll take a look.

Contact us

New here? Take the diagnostic to see where your unassisted skills stand.