5 ms·
> I add to my team’s CLAUDE.md multiple times a week. This concerns me because fighting tooling is not a positive thing. It’s very negative and indicates how i
by goalieca 10mo ago
> I add to my team’s CLAUDE.md multiple times a week.
This concerns me because fighting tooling is not a positive thing. It’s very negative and indicates how immature everything is.
- bcherny 10mo agoYou might be misunderstanding what a CLAUDE.md is. It’s not about fighting the model, rather it’s giving the model a shortcut to get the context it needs to do its work. You don’t have to have one. Ours is 100% written by Claude itself.
- seunosewa 10mo agoThat's not the same thing as adding rules by yourself based on your experiences with Claude.
- jedberg 10mo agoThe Claude MD is like the documentation you hand to a new engineer on your team that explains details about your code that they wouldn't otherwise know. It's not bad to need one.
- thfuran 10mo agoBut that documentation shouldn’t need to be updated nearly every other day.
- jm4 10mo agoIt does if it’s incomplete or otherwise doesn’t accurately convey what people need to know.
- thfuran 10mo agoAnd something is terribly wrong if it is constantly in that state despite near daily updates.
- kxrm 10mo agoIf you are consistent with how you do your projects you shouldn't need to update CLAUDE.md nearly every day. Early on, I was adjusting it nearly every day for maybe a couple of projects but now I have very little need to make any adjustments. Often the challenge is users aren't interacting with Claude Code about their rules file. If Claude Code doesn't seem to be working with you ask it why it ignore a rule. Often times it provides very useful feedback to adjust the rules and no longer violate them. Another piece of advice I can give is to clear your context window often! Early in my start in this I was letting the context window auto compact but this is bad! Your model is it's freshest and "smartest" when it has a fresh context window.
- nrds 10mo agoIt takes a lot of uncached tokens to let it learn about your project again.
- Bjartr 10mo agoConsider that every time you start a session with Claude Code. It's effectively a new engineer. The system doesn't learn like a real person does, so for it to improve over time you need to manually record the insights that for a normal human would be integrated by the natural learning process.
- newsoftheday 10mo agoReminds me of that Nicole Kidman movie Before I Go to Sleep.
- handfuloflight 10mo agoSleep time compute architectures are changing this.
- majewsky 10mo agoYes, that's exactly the problem. There's good reasons why any particular team doesn't onboard new engineers each day, going all the way back to Fred Brooks and "adding more people to a late project makes it later".
- bdangubic 10mo agothere are many tools available that work towards solving this problem
- Marsymars 10mo agoI certainly could be updating the documentation for new devs very frequently - the problem with devs is that they don't bother reading the documentation.
- PunchyHamster 10mo agoand the other problem - when they see something is wrong/out of date, they don't update it...
- Gud 10mo agoWhy not?
- bitwize 10mo agoHave you never looked at your work's Confluence? Worse, have you never spent time at a company where the documentation wasn't frequently updated?
- thfuran 10mo agoDo you have nothing but onboarding material on yours and somehow still need to update it several times a week?
- udfalkso 10mo agoSame thing happens every time a new hire joins the team. Lots of documentation is stale and needs updating as they onboard.
- filoeleven 10mo agoBut that documentation shouldn’t need to be updated nearly every other day.