Heal
30-Day AI Detox Plan for Engineers
Small rituals, no-AI challenges, and reflection prompts that rebuild your relationship to craft. One day at a time.
This is not a 30-day challenge where you stop using AI entirely. That is not the goal, and for most engineers it is not realistic. The goal is something quieter and more sustainable: rebuilding your relationship with your own craft. Remembering what it feels like to think without scaffolding. Recovering the confidence and ownership that may have quietly eroded.
The practices here are small. Most take 5–15 minutes. None require you to radically change how you work. What they require is consistency and honesty with yourself. They compound. What feels arbitrary in week one often feels like a fundamental part of how you work by week four.
Track your progress using the day tracker at the bottom of each week. It saves to your browser — no account, no data sent anywhere.
The daily skeleton (every day of the 30)
Morning — 5 minutes
Set a single intention
Before opening any IDE or AI tool, write one sentence: What do I actually want to accomplish today? Not what's in the backlog — what you, as a thinking person, want to understand or build. Even if the honest answer is "get through the day," write it. The practice of asking the question matters more than the answer.
During work — rolling
Notice your reflexes
Each time you open an AI tool, pause for three seconds and ask: Am I opening this because it's the right tool for this moment, or am I opening it because reaching for it is automatic? You do not have to change the behavior. Just notice it. For now.
Evening — 5 minutes
Write one thing you understood today
One sentence. Something you understand now that you didn't understand this morning. It can be small — a function, a concept, a behavior you traced. The practice of articulating your own learning is what makes it real and yours. Compounded over months, this becomes a record of growth that exists entirely inside you.
Week 1: Noticing
Days 1–7 · Build awareness before you change anything
Do not try to change your behavior this week. Just watch it. The goal of week one is to become genuinely curious about your own AI use patterns — when you reach for AI, why, and how it feels after. Observation is the foundation. You cannot change a pattern you have not clearly seen.
Days 1–2
Log your AI interactions for one full workday
Keep a simple running note (paper or file) of every time you use an AI coding tool. Note the time, what you used it for, and a one-word description of how you felt after: satisfied, hollow, relieved, uneasy, neutral. By end of day two, you have a data set. Look at it honestly.
Day 3
Reflection prompt
Days 4–5
The 3-second pause rule
Before every AI query this week, pause three seconds. In those three seconds: can you sketch the beginning of an answer yourself? If yes — try it first. Write one line before prompting. Then prompt if you still want to. You may find you need the AI less than you thought. You may find the three seconds is its own kind of useful.
Day 6
Read something technical directly
Read 15 minutes of actual documentation — not an AI summary, not a blog post, the source documentation or a real book. Notice how this feels different from AI-mediated reading. Slower, probably. But also differently satisfying.
Day 7 — Week 1 check-in
Weekly reflection questions
Write honest answers to these:
- "What did I notice about my AI use this week that I hadn't seen clearly before?"
- "Was there a moment when I solved something myself that I would have usually prompted for? How did that feel?"
- "What domain of my work feels most AI-dependent right now? Is that by choice or by default?"
Week 1 tracker (tap to mark complete):
Week 2: Unaided Practice
Days 8–14 · Discover what you actually know
This week you will start doing deliberate AI-free technical work. Not much — just one contained problem per day, or a portion of your work that you choose to complete without assistance. The goal is not to prove you can code without AI. The goal is to find out what you know, and to experience what solving something yourself feels like again.
Expect this to feel slow at first. That slowness is not failure. It is what real thinking feels like when it has not been practiced in a while.
Day 8
One AI-free micro-task
No-AI Challenge
Write one small function — 10 to 30 lines — completely without AI assistance. No Copilot suggestions, no ChatGPT, just you and the language reference if you need it. It does not need to be elegant. It just needs to be entirely yours. Sit with whatever comes up.
Days 9–10
The 20-minute thinking window
Each morning this week, spend the first 20 minutes of your workday without opening any AI tool. In those 20 minutes: read your code, think about what you are trying to build, write notes or pseudocode. Then work however you choose for the rest of the day. Those 20 minutes are yours.
Day 11
Debug something without help
No-AI Challenge
Find a bug — in your current work, or in a toy project — and debug it entirely without AI assistance. Use logs, print statements, the debugger, your own reading of the code. Notice the process: the frustration, the false starts, and if you get there, the particular satisfaction of having figured it out yourself. That satisfaction is what you are here to recover.
Days 12–13
Reflection prompt
Day 14 — Week 2 check-in
Weekly reflection questions
Write honest answers to these:
- "What did I find out I could do that I wasn't sure I could?"
- "How did it feel to debug or build something without AI? Frustrating, satisfying, both?"
- "Which skills feel rustier than I expected? Which surprised me by being intact?"
Week 2 tracker:
Week 3: Rebuilding Authorship
Days 15–21 · Make something that is fully yours
Week three is about reclaiming psychological ownership of your work. The specific goal: at least one piece of work this week where you wrote the first draft, made the key design decisions, and can explain every line. Not necessarily AI-free — just genuinely authored by you first.
Days 15–16
Write before prompting
For any significant piece of code this week — a new feature, a refactor, a design decision — write a first draft in plain text or pseudocode before you involve AI. Even two paragraphs of what you are trying to do and why. Then use AI if you want. Compare what you designed to what AI produces. The gap is useful information.
Day 17
Claim one domain
Pick one area of your codebase or technical stack — one you care about — and decide to work in it AI-free for the rest of the week. This is your domain. You will understand every decision in it. You will build it slowly enough to think clearly. It does not have to be large. One module, one service, one small library. Yours.
Days 18–19
No-AI challenge: the kata
No-AI Challenge
Complete one programming kata or small challenge entirely without AI — without looking up solutions, without Copilot, with documentation only if needed. Choose something slightly outside your comfort zone. The productive struggle is the point. Thirty minutes, honest effort, whatever the result.
Days 20–21 — Week 3 check-in
Weekly reflection questions
Write honest answers to these:
- "Is there code I shipped this week that feels genuinely mine? What makes it feel that way?"
- "How does work feel different when you are the author rather than the reviewer?"
- "What would it look like to maintain this level of ownership going forward — without abandoning useful tools?"
Week 3 tracker:
Week 4: Integration
Days 22–30 · Design the practice that lasts
The goal of week four is not to complete 30 days and stop. It is to design the ongoing practice that becomes part of how you work. The 30-day plan ends. The craft practice does not.
Days 22–24
Build something small, complete, and yours
No-AI Challenge — The Capstone
In three days, build one small thing entirely without AI: a CLI tool, a small web page, a script, a data transformation. Anything with a clear scope, a real problem to solve, and a beginning-to-end authorship that is completely yours. Use documentation. Use forums if stuck. No AI. The goal is to have something at the end that you built, understand, and feel genuinely proud of.
Days 25–27
Design your personal AI use charter
Write it down: when does AI serve you, and when does it cost you? This is not a set of rules — it is your own honest framework based on what you have learned in the last four weeks. Two or three sentences per category is enough:
Days 28–29
Maintenance practices for after Day 30
These are the three practices that have the most evidence behind them for maintaining what you have rebuilt:
- One AI-free problem per week — any size, any domain
- One direct documentation read per week — not a summary, the source
- One reflection question per day — What do I understand today that I didn't understand yesterday?
Day 30 — Final reflection
The full-circle questions
Take 15 minutes for these:
- "How do I feel about my own technical capability now compared to day one? What changed?"
- "Is there a piece of work from this month that I feel genuinely proud of in the specific way I was hoping to feel?"
- "What is my ongoing relationship with AI tools going to look like — intentional, not reflexive?"
- "What would I tell an engineer at the beginning of this 30-day plan that I wish I had known?"
Week 4 tracker:
After Day 30
The goal was never abstinence. You are not trying to go back to 2022. You are trying to have a relationship with AI tools that you chose, rather than one that chose you.
The daily skeleton — morning intention, afternoon noticing, evening learning log — is worth keeping indefinitely. It costs 10 minutes a day and compounds into something real over months.
The rest can adapt to your situation. Some weeks you will use AI more. Some weeks less. What has changed is the intentionality: you know why you are using it, what it costs, and what to protect.
That is the craft. That is what you came here for.
Tools to support the practice
Continue exploring: