# Coding skills guides for developers

> Practical guides for code recall, tracing, debugging, comprehension, idiomatic code, AI-code review, and unassisted coding.

- Canonical HTML: [https://unrust.dev/guides](https://unrust.dev/guides)
- Markdown representation: [https://unrust.dev/guides/index.md](https://unrust.dev/guides/index.md)

## Guides

- [What is unassisted coding?](https://unrust.dev/guides/unassisted-coding/index.md): Unassisted coding means solving a task without AI, autocomplete, or external answers for a defined period. Learn what it measures and how to use it.
- [What is code recall, and how do you practice it?](https://unrust.dev/guides/code-recall/index.md): Code recall is the ability to reconstruct small pieces of code from memory. Learn what to practice, what not to memorize, and how to test it.
- [What is code tracing?](https://unrust.dev/guides/code-tracing/index.md): Code tracing is the habit of simulating execution step by step. Learn how to trace values, references, loops, and branches without running the program.
- [How do you debug code without AI?](https://unrust.dev/guides/debugging-without-ai/index.md): A practical debugging loop for developers who want to reason through a failure before asking an AI assistant or search engine for a fix.
- [How do you read code against its contract?](https://unrust.dev/guides/reading-code-against-a-contract/index.md): Learn how to compare implementation with intent, find mismatched assumptions, and catch bugs that clean-looking code can hide.
- [What is idiomatic code?](https://unrust.dev/guides/idiomatic-code/index.md): Idiomatic code uses familiar, clear patterns for a language and codebase. Learn how to judge it without turning style preferences into dogma.
- [How do you review AI-generated code?](https://unrust.dev/guides/reviewing-ai-generated-code/index.md): A practical review checklist for AI-generated code: verify the contract, inspect boundaries, run focused tests, and understand every change before shipping.
- [How do you review retry logic safely?](https://unrust.dev/guides/reviewing-retry-logic/index.md): Review retry logic by checking retryable failures, idempotency, attempt budgets, backoff, jitter, and the outcome a caller sees when retries stop.
- [How do you review an access-control code change safely?](https://unrust.dev/guides/reviewing-access-control-changes/index.md): Review access-control changes by mapping the subject, action, resource, context, enforcement point, and denied-path evidence before approval.

Browse situational resources: [Developer use cases](https://unrust.dev/use-cases/index.md)

Browse language-specific resources: [Practice by language](https://unrust.dev/languages/index.md)