Practice

What practice is

Coding problems you solve in the browser and a judge that actually runs them - what the parts are, what costs nothing, and what signing in adds.

Finding a problem

The filters on the problem list, what the acceptance rate means, why a topic page is worth browsing, and how to get an unsolved one at random.

The solver

The layout of a problem page, why the editor holds only your function, how your draft survives a refresh, and what each of the three tabs is for.

Running and submitting

What Run checks and what Submit checks, how to try your own input, what gets kept, and what the daily allowance actually limits.

Verdicts and test cases

What each verdict means, why you see every case rather than only the first failure, which two verdicts are our fault, and when an old Accepted goes stale.

Languages and limits

The five languages you can solve in, the time and memory your code gets, why Java starts with less of the budget, and the one thing TypeScript does differently.

Hints and the Approach tab

Hints are free and ladder one at a time; the Approach tab is the author's walkthrough - and the one place on the page a Big-O is allowed to appear.

Asking AI for help

The three things Revquix AI will do on a problem, what it costs before you press it, and the four things it deliberately will not do.

How fast is my solution

The percentile beside an accepted submission, the growth analysis that runs it at four input sizes, and why neither of them ever prints a Big-O.

Your practice record

The solved ring, the streak, the activity graph shared with your projects, and why we never show your progress as a percentage.

Tracks

Ordered paths through the problem catalogue - how the counts work, what Continue picks, and what happens to a problem that is withdrawn after you start.

Writing a problem

Authoring a coding problem end to end - the signature, examples, reference solution, the checks that must pass before it publishes, and what review looks at.