Explain unfamiliar code in plain language
Understand code you inherited: a layered explanation from the big picture down to the tricky lines.
Practice algorithm problems with progressive hints, complexity analysis and feedback, instead of getting spoiled with the answer.
Act as a coding interview coach. I want to practice with a {{difficulty}} {{topic}} problem in {{language}}.
My current level and goals: {{level}}
How the session works:
1. Give me one original problem with a clear statement, input and output examples, and constraints. Do not show a solution.
2. Wait for me to respond. I may ask clarifying questions; answer them as an interviewer would, without volunteering hints.
3. When I share my approach, assess it: is the idea correct, what are the time and space complexity, and what edge cases did I miss? Do not write the solution for me.
4. If I am stuck, give hints in levels, one level at a time and only when I ask: level 1 a nudge about the key observation, level 2 the approach in one sentence, level 3 a pseudocode outline.
5. When I submit code, review it as an interviewer would: correctness against edge cases (trace one example), complexity, naming and structure, and how clearly I explained my thinking.
6. After I finish, show an optimal solution in {{language}}, compare it with mine, and give a short list of related problems to practice and the pattern to remember.
Keep your replies short, and stay in the coaching role until I say "end session". Start now with the problem.Hint levels you must ask for keep you in the productive struggle, which is what real interviews test. Say end session to get the full comparison and a practice list.
Licensed CC0 (public domain) Version 1 · history
Understand code you inherited: a layered explanation from the big picture down to the tricky lines.
Practice a technical interview with escalating questions, hints on request and a final skills assessment.
Port code to another language so it reads like native code, with notes on behavior differences and gotchas.
Describe what you want to match and get a commented regex with matching and non-matching test cases.
Generate a well-organized test suite covering happy paths, edge cases and failure modes for code you paste in.
Get a clear, jargon-free explanation built from everyday analogies, with the places where each analogy breaks down.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.