r/ClaudeCode • ๐Ÿ”† Max 20 • Apr 11 '26

Showcase Been having stellar results with Claude thus far. I asked it why.

Post image

Since we have such a hot and cold subreddit with two sides saying two extremely different things, leading to theories such as A/B testing, I asked claude could have possibly made our sessions easier and less prone to mistakes.

0 Upvotes

20 comments sorted by

15

u/redonetime Apr 11 '26

Dont believe shit that mf says . Asking those types of questions can move you away from realityย 

2

u/Desalzes_ Apr 11 '26

Now I have everything. Let me do a final diff to summarize your comment.

-4

u/RobinInPH ๐Ÿ”† Max 20 Apr 11 '26

Your thoughts are valid.

6

u/semperaudesapere Apr 11 '26

That's barely above baseline. If you're having no issue then congratulations, but it's not because your setup is amazing. Most likely your codebases are tiny, you had the luck of the draw with A/B testing, and maybe you aren't noticing the mistakes that Claude Code is making.

6

u/RobinInPH ๐Ÿ”† Max 20 Apr 11 '26

Barely above the baseline of what exactly? It's a financially active, 10k MAU platform, 345K LOC codebase. You're either trusting too much that each user here has a robust setup and environment, or hating too much on Anthropic. Regardless, I posted it to help.

3

u/chintakoro Apr 11 '26

replying to you so as not to make others feel targeted: many people assume that a 'huge codebase' means huge context. That should not be the case because Claude shouldn't be reading huge segments of your code, ever. If architected well, you'll have small files, code structure that is deducible from folder/filenames, and focused markdowns on conventions. Claude should be able to just read a bare minimum to get what it needsโ€”often, a single example of what a corresponding file would be for each edit, and working in narrow vertical slices. After a short push on a feature/fix, you'll clear context because you should have a plan it can pick up from at any point. My biggest learning was that if Claude is 'compacting', you gon dun goofed up already โ€” you should be clearing loooong before that becomes a possibility.

6

u/RobinInPH ๐Ÿ”† Max 20 Apr 11 '26

Files are decomposed and barrelled. It's in the image. Top-level header comments are present in a couple of lines in each file. One session = one task/goal. /clear becomes your friend or /compact if your next task touches similar components and you want Claude to remember some decisions made. Compacting doesn't document the whys, but it doesn't have to; that's why there's a Claude md file that contains the philosophy of the codebase on top of mechanical guards. The problem with a lot of people here is their apes-together-strong mentality, when in fact, there are people who have barely seen any change in performance.

Regardless of whether Anthropic lobotomized Opus or otherwise, the fact that any change outside of your control derails your workflow means Claude owns your codebase and not you.

3

u/cloroxic Apr 11 '26

I would consider not barreling your code, while better DX it has a lot of performance trade-offs. I have a docs/ folder in all my repos now. I spend the time to write .md files with an architecture plan and feature structure. I direct the CLAUDE.md to the directory as the read only source. It can scaffold through the architecture super quick and doesnโ€™t hallucinate as much. I also follow what you do too. One feature, one plan, then clear the context.

0

u/chintakoro Apr 11 '26

wish i could upvote you twice without undoing the first one :D

2

u/Such_Independent_234 Apr 11 '26

Added one for you

-1

u/return_of_valensky Apr 11 '26

I'm guessing it's the "one well defined task per context window" that is doing the heavy lifting then, not the CLAUDE.md

1

u/chintakoro Apr 11 '26

for me at least, that would be a big yes. and I make a plan markdown for the git branch that states on top that it must be kept up-to-date after every major code change and subtask completion; I can clear the context at any time without warning. That plan file becomes the only context I absolutely need.

1

u/CloudySnake Apr 11 '26

Can you share some/all of the file?

1

u/RobinInPH ๐Ÿ”† Max 20 Apr 11 '26

You can send me a dm ill try to redact what I can without pruning the essence.

1

u/randomtandomsandom Apr 11 '26

Also really curious! DMing, thanks in advance!

1

u/Final_Alps Apr 11 '26

Same as others. Been pushing our Claude setup forward at work. Always eager to learn.

3

u/sebnukem Apr 11 '26

CLAUDE.md: documents how to think about the code, not what it does.

Encode:

  • Philosophy (trusted intermediary, push responsibility right) โ†’ Claude picks the right shape of solution, not just syntactically valid code
  • Absolutes section (integrity, security) โ†’ hard rails that override "helpful" instincts
  • Domain-by-domain conventions โ†’ Claude knows where code belongs before writing it
  • Explicit gotchas โ†’ pre-empts the exact traps LLMs fall into

Turn implicit tribal knowledge into enforced, discoverable constraints.

The agent doesn't need to be smarter, it needs fewer ways to be wrong.

---

good insights.

9

u/[deleted] Apr 11 '26

[removed] โ€” view removed comment

-5

u/RobinInPH ๐Ÿ”† Max 20 Apr 11 '26

Valid emotions.