💬 Copy-Paste Prompts
When your brain is mush but the sprint review is tomorrow, these prompts do the thinking for you.
**Legacy Code Whisperer:** \"Here's a code block I didn't write and don't understand: [PASTE CODE]. Explain what this does in simple terms, as if I'm a junior dev who just had too much coffee. What are the potential bugs or edge cases here that past-me might have missed?\"
**Meeting Survival Mode:** \"I have a meeting about [TOPIC] in 10 minutes and I've been heads-down on other work. Generate 3 intelligent-sounding, open-ended questions I can ask to appear engaged and thoughtful, plus 2 concise bullet points summarizing the key challenges in this area.\"
When Your Brain Has Thrown a 500 Error
You know the feeling. Your eyes are glazed over, your third coffee is cold, and the code on your screen might as well be ancient hieroglyphics written by a sadistic predecessor (who was probably also you, six months ago). You're not coding; you're performing digital archaeology on your own decaying mental state.
Burnout isn't just about being tired. It's about your cognitive surplus evaporating, leaving behind the crusty residue of decision fatigue. Should you refactor this? What does this function even return? Is this a semicolon or a speck of dust on your monitor? At this point, asking an AI for help isn't cheating—it's a survival tactic.
📋 TL;DR: Your Cognitive Life Preserver
- Stop Writing Documentation: Use AI to reverse-engineer explanations from the code you already have (but no longer comprehend).
- Debug on Autopilot: Feed errors to a model that hasn't been staring at the same line for 45 minutes and can actually see the problem.
- Fake Mental Clarity: Generate coherent questions, summaries, and review comments when your own brain is offering only static.
1. The "What Did Past-Me Do?" Documentation Prompt
You open a file. You wrote it. The commit history confirms this. Yet, it feels like reading a love letter written in a language you've forgotten. This prompt forces the AI to be your personal code archaeologist.
Prompt: "Analyze this [language] code for its core purpose and logic. First, provide a one-sentence summary. Then, create a brief API-style documentation table: Function/Method Name | Input Parameters | Return Value | Primary Responsibility (5 words max). Finally, list 2-3 'gotchas' or non-obvious behaviors a tired developer might miss."
Expected Output: A concise summary, a clean table breaking down the components, and a shortlist of hidden traps.
2. The Sleep-Deprived Debugging Prompt
Your debugging skills after 2 AM operate on a spectrum from "inspired genius" to "literally trying to console.log the concept of hope." This prompt cuts through the fog.
Prompt: "Act as a senior developer pair. Here's my error: [PASTE ERROR]. Here's the relevant code snippet: [PASTE CODE]. I am cognitively depleted. Give me: 1) The most probable root cause (simple terms). 2) The exact fix to try first. 3) One alternative cause if that doesn't work. No lectures, just the fix."
Expected Output: A direct, actionable hypothesis and solution, followed by a straightforward backup plan.
3. The "Explain It To Me Like I'm a Caffeinated Squirrel" Prompt
Sometimes you need the code explained back to you, but you lack the attention span for a textbook. This prompt demands simplicity and prioritization.
Prompt: "I'm mentally checked out. Explain this [concept/code block] in two layers: Layer 1: A stupidly simple analogy (e.g., 'This function is like a bouncer at a club checking IDs'). Layer 2: Three key lines of code or steps that make the whole thing work. Ignore edge cases for now."
Expected Output: A memorable analogy followed by a minimal, high-impact technical breakdown.
4. The Meeting Zombie Preparation Prompt
You've been dragged into a meeting about a system you haven't thought about in weeks. Your contribution is expected. Your brain is offline. Time to generate a persona.
Prompt: "Generate a quick brief for a burned-out developer. Topic: [MEETING TOPIC, e.g., 'Database migration planning']. Provide: 1) Two concise bullet points on current status/blockers. 2) Three thoughtful, non-awkward questions I could ask to sound engaged (e.g., 'What's our rollback strategy?' not 'Is this meeting almost over?')."
Expected Output: A cheat sheet of talking points and questions that demonstrate baseline competence.
5. The Burnout-Proof Code Review Prompt
Reviewing code when you're fried means you'll miss the subtle bug and comment on the spacing. This prompt focuses the AI on the high-risk mistakes you're prone to make when exhausted.
Prompt: "Perform a code review focused on common 'burnout mistakes' for this [language] diff. Prioritize finding: 1) Logical errors from copy-paste or fatigue (off-by-one, wrong variable). 2) Missing error handling or edge cases. 3) Potential performance issues (nested loops on large data). Ignore style/formatting unless egregious. List findings with line numbers and concrete suggestions."
Expected Output: A targeted list of functional, high-severity issues, not nitpicks.
🛠️ Pro Tips for the Professionally Tired
- Chain Prompts for Clarity: Use the "Explain it simply" output as the context for your debugging or documentation prompt. The AI explains it to you, then you ask it to fix the part you still don't like.
- Build a Personal Library: Save these prompts in a text file or a tool like Cursor's custom instructions. Label them for your future self (e.g., "For when brain no work").
- Embrace the Satire: Telling the AI "I am tired" or "Assume I've made a dumb mistake" isn't weak—it's providing crucial context that leads to better, more direct answers.
- Know When to Step Away: These prompts are a bridge to get you to the end of a task or day. If you're consistently relying on them to understand your own code from last week, the real fix isn't a better prompt—it's a break.
Conclusion: Ship Code, Not Your Sanity
Burnout turns simple tasks into cognitive marathons. These prompts aren't about replacing your skills; they're about conserving your most depleted resource—mental bandwidth—for the decisions that actually require a human spark. They handle the tedious translation work between "what is this" and "what needs to be done."
Use them as a temporary cognitive crutch, not a permanent wheelchair. Copy them, adapt them, and get that code out the door. Then, for the love of all that is holy, close your laptop. The real legacy code you need to debug is your own sleep schedule.
Action: Pick one prompt from the Quick-Value Box and use it on your very next task. Prove to yourself that shipping while burned out doesn't have to mean shipping garbage.
Quick Summary
- What: Developers waste hours writing repetitive documentation, explaining legacy code, and debugging cryptic errors - all while dealing with burnout and decision fatigue
π¬ Discussion
Add a Comment