# Quantitative Type Theory Usage: Walkthrough

Quantitative Type Theory Usage shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.

## Key idea

Annotate each binder with a usage quantity (0, 1 or omega) so linear, affine and unrestricted variables share one type theory.

## 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

Type checking is syntax directed once quantities are known; inference of quantities is a separate integer linear problem.

## Common mistake

Allowing a linear variable to be used in both branches of a case without adding the usages, which duplicates it.

## 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 real-time AI interview assistant for live interviews.