I'm Officially on a Mission to Become a 'Claude God'
Published: November 17, 2025 • 4 min read
Yes, I know, the title is a bit dramatic, but it tells no lies. I truly am on a mission to becoming unbelievably good at using Claude to optimize my development processes.
As part of my SDR Era, I am taking on a lot of projects. I have ideas flowing through my head like water and I want to execute on all of them with speed without sacrificing the quality of my work. I also want to create English and French videos for every single project I create. And guess what? I have only 26 days left until the official termination of my SDR Era.
I need to act fast, and the best way to do that is to optimize the tools I currently have access to for their best performance. This will require a lot of learning as well as a lot of trial and error, but I am here for every bit of the journey.
Why I'm Sharing This Journey
One of the reasons I love and enjoy writing is that it helps me clarify my thoughts and solidify whatever I am learning. So, little by little, I will share in blog posts all the cool tips and tricks I am learning on my way to becoming a Claude God.
For every blog post where I share what I am learning, I will provide either one short quick tip or one long big tip. However, each of them will be very useful.
Getting Started with Claude in the Terminal
Now for starters, if you haven't installed Claude in your terminal yet, you should probably check out the quickstart guide to get started.
Now, let's start with one quick tip for today:
Claude God Tip #1: Never Start Fresh Again
The Amateur Mistake
When amateurs like the version of me 23 days ago (definitely not the current version of me) use Claude, after ending a session with the keyboard combination Ctrl+C+C, when we return to the project to continue the work we started, we simply type the claude command again.
The problem with this is that now you have started a whole new instance of Claude (or Claude conversation) that has no understanding of what changes, plans, or decisions you made in the previous instance. It has absolutely no context and you have to start afresh to instruct it.
The Manual Workaround
Now you can definitely instruct Claude to track all its changes using a prompt like this:
"Create a file CLAUDE_CONTEXT.md with:
- Current task: [what I'm working on]
- Files modified: [list]
- Next steps: [what needs to be done]
- Important notes: [gotchas, decisions made]
Update this file after each major change."
However, to save the hassle of creating and updating a CLAUDE_CONTEXT.md which can slow down your execution speed, you can simply use one of the following flags with the claude command.
The Pro Move: Using Flags
claude --continue
The --continue flag tells Claude to continue working on the last task you previously terminated without you having to re-explain everything. It automatically resumes your most recent conversation for the current project.
This is such a simple, basic tip, yet it can save so much time knowing that you don't have to worry about closing your current Claude context and then re-explaining everything.
claude --resume
There is another related flag you should know about:
The --resume flag is similar to the --continue flag except it lets you choose what conversation you want to continue from a list of past sessions using a conversation picker or by entering a session ID. This is useful if you had started multiple Claude sessions in the same project directory and each one manages different changes to your project.
When to Use Which
Use --continue when:
- You have one main claude conversation/session and want to pick up exactly where you left off
- You just interrupted work briefly and want to resume immediately
- You're working on a single focused task
Use --resume when:
- You've been working on multiple different features in the same project with different claude conversations/sessions
- You want to revisit a specific past conversation/session
- You need to switch between different workstreams
What's Next in the Claude God Series
Anyways, while this is very simple, I hope you learned something new today. I'm already preparing the blog post for the next Claude God tip and I am so excited to share that, so stay tuned!
Spoiler: The next tip involves something that will literally cut your debugging time in half. Trust me, you don't want to miss it.
Thanks for reading!