Explain This Codebase Like I Just Joined

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.

Don't pick a stack you'll fight for years. Describe what you're building and your skills — get a real recommendation with trade-offs, not hype.

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.

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.

An algorithm or concept that won't click? Name it — get it explained with a plain analogy, a walkthrough, the complexity, and when you'd actually use it.

Stuck between two technical approaches and second-guessing? Lay them out — get the real trade-offs for YOUR situation and a clear recommendation, not 'it depends.'

Find the holes before someone else does. Paste your code — it runs an OWASP-style security review and tells you what an attacker would try first.

The code you'll forget in a month. Paste it — get comments that explain the WHY, not the obvious, so future-you (or your team) isn't lost.

Describe what you want to match in plain words. Get the regex, every piece explained, and test cases — so you actually trust it before you ship it.

Paste the function you're embarrassed by. Get it cleaner and readable with the exact same behavior — plus a note on what was wrong so you stop doing it.

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.

A config file full of settings you're scared to touch. Paste it — get what each part does, which knobs are safe to change, and which will break things.

Got the logic in plain steps but not the syntax? Write it out however you think — get clean, working code in your language, with the logic preserved.

Designing an API and want it to not be a regret in six months? Describe what it does — get clean endpoints, naming, and the edge cases you'd forget.

"fixed stuff" is not a commit message. Paste your diff or describe the change — get a clear commit message your future team will actually thank you for.

Porting code to a new language or framework? Paste it — get the converted version plus the traps that don't translate one-to-one.

The thing every dev skips. Tell it what your project does — get a README people can actually follow: what it is, how to run it, and why it exists.

"Works on my machine" — famous last words. Describe your app — get a Dockerfile and setup that runs the same everywhere, explained so you understand it.

Naming things is half of programming and you're stuck. Paste the code or describe it — get clear, consistent names that make the code read itself.

It works but it's slow. Paste it — get where the real bottleneck is, the optimized version, and whether the speed-up is even worth the complexity.

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

Paste the stack trace that means nothing to you. Get what actually broke, why, and the most likely fix — in plain English.

Test's red and you don't know if it's the code or the test. Paste both — get whether the test is wrong, the code is wrong, and exactly what to fix.

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.