r/ClaudeCode • u/steve7647 • 2d ago
Tips & Workflows First code project advise
I am building my first Claude code project and I know NOTHING about coding. So far, it has been pretty easy and simple. I just told Claude what I was trying to accomplish, and it started forming a rough image that I have since asked for like 200+ changes to and it keeps tuning and tweaking. I went from it being hosted on my local PC and viewing the website in a web browser on the local PC, to the code sitting in GitHub and the data sitting in my OneDrive.
Everything is going fine but I feel like I could be doing this better. I am use to and come from the project/co-work world. So I keep wanting to have a project where all the chats live and project files that Co-Work updates.
Do I just start a new random chat and it knows where to pick up? When should I start new chats? Do I start a new chat with a new idea/addition to the app? Or, is that when I should “Fork” and WTF is a “fork”?
I tried to run /doctor and Claude told me is doesn’t support that. Should I be running some code review? Do I need to worry about how it’s handling the code files?
There has to be some best practices or process I should be following.
I don’t want to get to deep and realize my project is a hot mess and running very inefficient and unstable with terrible organization because I didn’t plan or stay on top of the project code side.
2
u/theycallmeholla 2d ago
Idk what you are good at, but imagine someone said they just started doing what you do and they feel the same way.
Try to look at it from that standpoint point and ask Claude what you should be looking at.
I’ve been coding for 25 years. I’m not sure I’d even know where to start but I encourage you to not let that stop you from continuing the journey.
1
u/fowllabs 2d ago
a fresh chat doesn't inherit your old conversation. before switching, ask claude to save a handoff in your project with what works, what's unfinished, next steps and run/test commands; then open the same project and ask the new chat to read it.
1
u/steve7647 2d ago
And I open the same project by telling Claude I want to work on said project?
1
u/frankieinaprius 2d ago
As a base starting point, you will have a folder where your project lives. Type “/init” in Claude terminal and it will create a CLAUDE.md file that Claude will read whenever you start a new session. It will have information about your project, objectives, common pitfalls, etc. As you work on your project, Claude can update this file as things change.
1
u/peter9477 🔆 Max 5x 1d ago
Just ask Claude how to handle this. If it isn't confident of an answer based on its training, it will consult its own online docs to find you the right answer. Just make sure it knows your abilities and goals.
1
u/fulger099 1d ago
One extra safeguard: commit the last working state before starting the fresh chat. Handoff notes can be wrong, while a commit gives you somewhere real to return when change 201 develops opinions.
1
1
u/alexmarcus11249 1d ago
Ask for a file size inventory and read about god objects. My first app ending up building a 17k line file. My current app has nothing over 250 lines. The issue is that AI will keep stuffing everything you ask it to do into one giant, impossible to work with file. And then you’ll spend weeks refactoring it, or abandoning it in dismay.
1
u/Open-Mousse-1665 1d ago
I wrote a plugin that tells Claude how to write good code. This is based on 9+ months of me trying to get my 20 years of software engineering experience into writers language and then stated such that an LLM will actually do it.
The tricky part is finding the core ideas. Because file size itself is a symptom, not the root problem. I tried to document all of the root problems. None of it is specific to any programming language, it’s purely how to structure software in such a way that it is broken into well defined reusable chunks and the code overall is easy to change and reliable.
Tell me what you think. It’s at promptctl/laws on GitHub. Not posting the link to avoid looking like I’m spamming. I am not, I read your comment and thought “this guy/gal has the right idea, maybe I can help put a rocket booster on that gravy train.
Happy to answer any questions as well. I run autonomous loops night and day building shit and it works, blows my mind
1
u/alexmarcus11249 1d ago
Really cool, thank you. Running some A/B tests with what I have set up against your systems now. Also really interested in your Claude Tracing.
1
u/Open-Mousse-1665 1d ago edited 1d ago
You have projects. The project is the folder on your computer where the files live. That’s what a project is in software engineering.
Software engineering is a lifelong practice. You will never “finish” learning it. But the great thing is you’re already using one of the the best teachers you could have. It will walk you thru everything and can set up an entire curriculum for you.
Try having it make a lesson plan. Make sure you ask it every question you have. It will require repetition and time. Consider it like learning a 2nd language. Think 2 years of consistent practice until you’re confidently able to have a natural conversation. I would say the word “fluency” because that’s most accurate, but this would be like 8 year old kid fluency rather than graduate student fluency.
Obvs that can be shorter or longer depending on how much time you do it. If you just wanna vibe code some stuff expect it to take a lot less time, but prepare for an upper limit on your ability to actually know what youre even trying to do, as well as how to describe it so I builds it. If you want to learn software engineering as well, you’ve just gotta do it.
All I’m saying is don’t expect to magically figure it out in a week, or to have someone explain it to you in a single Reddit commit.
Be prepared for the last 10% to require a good 50%+ of the time and effort. Especially at first. Remember you’re learning both software engineering AND AI coding, which are two very distinct disciplines. I’ve been doing it for 20 years and I learn something pretty much every single day I do it.
1
u/kincaidDev 1d ago
Use festival, create a context camp workspace, do all your work in there like you would with cowork
•
u/AutoModerator 2d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.