Explain This Algorithm

Practice coding interviews the right way. Paste the problem — it nudges you toward the solution with hints, only revealing the answer once you've actually tried.

Got dropped into a framework you've never used? Name it and what you know — get the mental model, the core concepts, and the 20% you need to be productive today.

Dropped into unfamiliar code? Paste it. Get the map — what it does, how it flows, and where the bodies are buried — before you touch a thing.

Some things just won't stick. Paste the concept — get a few analogies that make it click and stay, plus where each one breaks down so you're not misled.

Want to play a song you love? Tell it the song and your instrument and level — get a plan to actually learn it without quitting in week one.

Want to learn something fast? Name it — it gives you the 20% of concepts that get you 80% of the way, in the order to actually learn them.

Reading isn't learning — doing is. Name the topic and level — get practice problems that build from easy to hard, with worked solutions only after you try.

Wish you could pick a specialist's brain? Name the kind of expert and your topic — it answers as a knowledgeable practitioner in that field, so you can ask anything.

Practicing but not improving? Tell it your instrument, level, and time — get a routine that builds real skill instead of just noodling the same five things.

Music theory always sounded like math? Tell it what you want to understand — get it explained in plain language tied to actual songs you know.

Real understanding comes from working it out, not being told. Name the topic — it teaches by asking you questions that lead you to the answer yourself.

Hit a concept that won't click? It explains at exactly your level — no baby talk, no jargon wall — then checks you actually got it.

Always wanted to try something but it feels intimidating? Name the hobby — get a beginner's path: what to get, what to learn first, and how to not quit in week two.

Want to reason like a lawyer, a designer, an investor, an engineer? Name the role — get the mental models and questions they use, so you can apply them yourself.

A mock interviewer that runs you through a real system design round, interrupts like the real thing, and scores you at the end. Brutal on purpose.

Building against an API that isn't ready? Describe the endpoint — get realistic mock JSON (success and error cases) so you can build the front end now.

Saw a photo you want to recreate but don't know how? Describe it and your camera — get the settings, lighting, and composition to actually pull it off.

Stuck? Explain the problem to it out loud. It asks the questions that make you find your own bug — and only steps in when you're truly stuck.

Paste a dense paper or report. Get what it actually claims, whether the evidence holds up, and the three things that matter — minus the jargon.

Worried about what your kid's exposed to online but don't know how to talk about it? Tell it their age — get an age-right conversation and the boundaries that actually help.

Mealtime is a battle and they'll only eat beige food. Tell it what they will eat — get meals that sneak in nutrition without a standoff at the table.

Say what you want in plain English, get clean SQL back — plus the gotchas (nulls, dupes, slow joins) you'd only find in production at 2am.

Your query's slow and the EXPLAIN output is gibberish. Paste it — get what's actually happening, the bottleneck, and the index or rewrite that fixes it.

You know you should. Paste the function — get the test cases that actually catch bugs, including the edge cases you'd forget at 6pm.