# Uniqueness Types Clean: Study Guide
Uniqueness Types Clean shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.
## Key idea
Give a value a unique type when the type system can prove it has a single reference, so in-place updates are safe.
## Steps to say out loud
1. Restate the input and the exact ask, and nail down constraints and overflow.
2. Name the pattern (binary search on the answer, monotonic stack or deque, interval / interval-DP, string hashing, graph traversal, or shortest paths) and why a nested scan or naive search fails.
3. Code it, then trace a short example plus one empty or already-solved edge case.
## Complexity
A uniqueness attribute that is lost as soon as the value is shared or passed to a non-unique context.
## Common mistake
Updating a unique array after it has been passed to a function that also kept a reference, which aliases the mutation.
## Practice tip
Time yourself: two minutes to explain, ten to code, three to test edges. Disclosure: I work on Linkjob AI. I also keep a practice cheat sheet at best AI tool for coding tests and OAs.