WEB LEARNING
How I actually use Claude, and what I'm still figuring out
· By Jethro Frane · 2 min read
My real experience using Claude for my videos, my projects, and my work, including the parts I'm still figuring out.
I didn't start with a plan. I started with a mess. My work was spread across different folders: videos, my portfolio, and software projects. Every time I opened a new chat, I had to explain everything again. That got tiring fast.
So I started giving Claude more context. Rules in a file. Notes on what I was working on. Then I found out I wasn't the only one using AI tools. Other apps were touching the same folder too, and that's when it got confusing.
The habit that saved me
Two tools can change the same file without you noticing. Now I write down who is working on what before I touch anything. It sounds boring, but it's the habit that keeps things under control.
Where it fits my life best
My video work is where Claude fits best. I keep it as its own project, with its own rules. When I mixed video and code in my head, everything felt heavier. Separating them made both easier.
My website is different. I'm more careful there. I read the work, check it, and only then decide what goes live.
What still bugs me
- Usage limits. Claude Pro and Claude Code share the same limit, so long sessions run out faster than I expect.
- Accuracy. It doesn't always get things wrong, but sometimes it sounds sure when it isn't. So I still double-check facts before I use them.
- How much to hand over. I don't know yet how much I can let it do on its own before I need to review each step.

What I'm still figuring out
I'm still learning when to let it work by itself and when to stop and look. I also don't know yet if it really saves me time. I need more real use before I can say that.
For now, I'm taking it one project at a time and writing down what I learn. That's the honest version of where I am.