A ramp for experienced devs: what's the same, what's different, and the idioms that make you look native.
claudechatgptintermediate
The prompt
I already code. Get me productive in {{new language}} fast.
Languages I know well: {{list}}
What I need to build in it: {{context}}
Give me: 1) THE MAP — what transfers directly from what I know, so I don't relearn basics. 2) THE GOTCHAS — where my instincts from {{known language}} will actively mislead me (memory, types, concurrency, error handling). 3) THE IDIOMS — the 5-6 things that make code look native here vs. translated-from-my-old-language. 4) A TINY PROJECT that forces me through the core concepts, with what to notice. 5) The one tooling/setup thing that trips up newcomers. Skip 'what is a variable.'
776 copies
Why this works
Experienced devs don't need basics — they need the gotchas where old instincts mislead and the idioms that separate native code from translated code; that's the fast path the tutorials never take.
Shared by Sam Kowalski — Full-stack dev. Debugs out loud so you don't have to.
You are a senior engineer doing a patient code review.
Here's my error:
{{paste the full error message}}
Here's the relevant code:
{{paste the smallest chunk that reproduces it}}
Respond in exactly this order:
1. ROOT CAUSE — one sentence, no hedging.
2. THE MINIMAL FIX — smallest possible diff, shown as before/after.
3. THE MISCONCEPTION — what I likely misunderstood for this bug to exist, explained like I'm smart but new to this corner of the language.
4. THE SMELL TEST — one thing to check elsewhere in my codebase where I've probably made the same mistake.
Do not refactor unrelated code. Do not add features.
You are the most thorough reviewer on my team — kind, but nothing gets past you.
Here's my diff:
{{paste your diff or changed files}}
Context: {{what this change is supposed to do}}
Review it:
1. CORRECTNESS — bugs, edge cases, race conditions. Rank by severity; say "solid" if it's solid.
2. NAMING & CLARITY — the 3 spots a stranger would misread first.
3. THE QUESTION — what will a reviewer inevitably ask about this diff? Draft my answer.
4. TESTS — the one test that's missing and would catch a real regression.
Skip style nitpicks a linter would catch.
I'm stuck in git. Help me fix it without losing work.
What happened / what I want: {{describe — wrong branch, bad commit, need to undo, merge conflict, detached head...}}
Output of git status (and git log if relevant):
{{paste}}
Give me: 1) WHAT STATE I'm actually in, plainly. 2) THE SAFE FIX — exact commands in order, with what each does and why. Prefer non-destructive options; clearly flag anything that discards work before I run it. 3) HOW TO VERIFY it worked. 4) THE HABIT that prevents this next time. Assume I'll paste your commands literally — don't hand-wave.