A free 30-day printable recovery journal for software engineers. Daily prompts, weekly reviews, habit trackers, and reflection space. Work through it at your own pace — no account needed.
30 Days to Reclaim Your Craft
For Software Engineers
clearing-ai.com · AI Fatigue Recovery Resource
5 questions · 90 seconds · Instant results. Find out which tier of AI fatigue you're in and get a personalized recovery plan.
clearing-ai.com →
The first week is about seeing clearly. Not solving, not changing — just noticing. What patterns have developed? What have you lost? What remains? This week builds the honest foundation everything else rests on.
One word to describe how you're feeling right now:
What's the one thing that made today hard?
Did you use AI to do something you could have done yourself?
Did you experience the "Sunday Night Reckoning" this past week? (That specific dread of the week ahead)
What triggered it most?
Today's no-AI experiment (describe what you did without AI today, even briefly):
Rate your skill confidence right now (1 = "I barely know what I'm doing" / 10 = "I can solve anything")
What specific skill feels most eroded right now?
What's one thing you used to enjoy about coding that you don't feel anymore?
How many times today did you reach for AI before trying something yourself?
The last time you had a genuine breakthrough (solved something hard, learned something new without help) — what was it?
What blocked you from having that feeling more recently?
Has AI made you faster, or has it made you feel busier without feeling better?
What's one thing you shipped in the last month that you couldn't explain in detail?
This week, I'm grateful for:
How has your sleep been this week?
Do you wake up dreading your inbox or Slack more than you used to?
Describe your relationship with AI tools right now in one sentence:
After one week of noticing: what's the pattern you see in yourself?
What's one thing you want to change in Week 2?
Rate this week honestly (1 = I didn't engage / 10 = I showed up fully):
Biggest realization this week:
Most surprising thing I noticed:
The AI habit I most want to change:
How my body feels most days:
Who I could tell about this (if anyone):
One thing I'm committed to in Week 2:
Overall energy trend this week:
Now that you can see the patterns, it's time to create space. This week is about intentional, structured disconnection. Not a detox. Not a punishment. Just: what happens when you give your brain time without a copilot?
What's your current relationship with your AI tool? (Describe in one phrase)
Did you try any no-AI time yesterday? If so, for how long?
When you don't reach for AI immediately, how does it feel?
Have you set any AI boundaries yet? (Time of day, types of tasks, etc.)
What would an AI boundary look like for you? (Write it down as if you're setting it):
What are you most afraid will happen if you reduce AI use?
Today's experiment: Try to solve one problem without AI, no matter how long it takes. What was the problem?
How long did it take vs. what AI would have taken?
How did it feel to struggle with it?
Do you feel ownership over the code you're shipping?
What would "full ownership" of your work feel like?
What's one task you'd like to do entirely by hand this week?
Rate your concentration/deep work capacity this week:
What's the longest uninterrupted coding session you've had this week?
What keeps interrupting you most? (Be honest)
Have you talked to anyone about what you're experiencing?
If you could explain it to one person in your life, what would you say?
Week 2 pattern: What's different from Week 1?
Did any no-AI experiment produce a moment of genuine satisfaction?
Rate this week (1–10):
Hardest moment this week:
Best moment this week:
AI boundary I'm actually keeping:
Skill I exercised without AI:
Physical/emotional state:
One commitment for Week 3:
Focus/concentration this week:
The reduction has created space. Now: what do you want to put there? This week is about intentional reconnection — not with AI, but with why you started coding in the first place. The craft. The challenge. The satisfaction of a hard thing, solved.
Why did you start coding? (The real reason, not the interview answer)
Do you still feel that way?
What's one coding-related memory that made you feel proud? (Any era)
What does "good engineering" mean to you, separate from velocity?
When's the last time you wrote code you were genuinely proud of?
What made it different from recent work?
Do you feel seen by your team/peers/manager right now?
What would "being seen" look like for you at work?
The last week is about integration — taking what you've learned, what you've named, what you've rebuilt, and making it stick. This isn't about "fixing" AI fatigue. It's about building a sustainable relationship with your work that works for you.
Rate your confidence in your technical skills right now (1-10):
What's one skill you've been avoiding practicing because AI handles it?
If you had a 2-hour block of uninterrupted deep work today, what would you work on?
Have you experienced 'flow' at any point this week?
What conditions would make flow more likely for you?
What's something you've learned in the last 6 months that you retained?
What's something you feel like you should know but don't?
Today's learning experiment (no AI, learn something new):
Week 3 reflection — Has your relationship with AI changed this week?
Rate this week (1-10):
Skill I'm rebuilding:
Flow experience this week:
Relationship with craft:
Team/workplace dynamic:
Physical state (sleep, energy, mood):
Commitment for Week 4:
Overall trajectory:
What does a healthy relationship with AI look like for you, personally?
What would you tell a junior engineer about AI fatigue if you could?
What's one boundary you're committed to keeping long-term?
What signs of AI fatigue do you still notice?
How has your self-trust changed since Day 1?
What's one thing you're genuinely curious about in your work right now?
Rate your overall energy this week:
Do you want to keep working as a software engineer?
What would make you say 'yes, this is the right work for me'?
What does 'recovery' mean to you now, after 25 days?
What are you most proud of from this journal?
What surprised you most?
If you could redo the last month with this journal from the start, what would you do differently?
What from this journal will you keep doing after day 30?
How are you feeling about the next 30 days?
Write a letter to yourself from 3 months from now. What do they want to tell you?
What's one commitment you're making for the next 30 days?
Final reflection — Name the most important thing you learned through this process:
What do you want people to know about AI fatigue if they haven't experienced it?
Rate your overall state right now vs. Day 1:
Day 30 — What will you do tomorrow that's different from Day 1?
One sentence to close this journal:
Would you recommend this journal to another engineer?
Final energy rating:
Signs you're recovering from AI fatigue:
Not sure if it's burnout or something deeper? Take the AI Fatigue Quiz at clearing-ai.com — it won't diagnose you, but it might give you language for what's happening.
988 — Suicide & Crisis Lifeline (US, call or text)
741741 — Crisis Text Line (text HOME anywhere)
findahelpline.com — Global mental health resources by country
All resources are free. No account. No tracking. No catch.
Newsletter not set up yet? Get added manually:
📧 Email hello@clearing-ai.com"You are not a worse engineer than you were two years ago.
You are a differently-positioned engineer.
The work now is to decide which parts you want to keep
— and which parts AI should hold."