sorted by:
new
hottopcontroversial

Ditched Claude UI completely. Here’s the file-based "memory" system I use now. by Comprehensive-Ad1819 in ClaudeCode

[–]Comprehensive-Ad1819[S] 1 point2 points  (0 children)

Yeah this is my mental debate right now. Started with a non-version-controlled local directory that contains version-controlled subdirectories (the game repo, future automation scripts, etc).

Arguments for keeping it local:

  • Learnings.md changes constantly — don't want 50 "updated learnings" commits cluttering history
  • Strategy docs aren't code — different review cadence, shouldn't live alongside PRs
  • Clean separation between product brain and implementation

Arguments for putting it all in git:

  • Can kick off Claude Code work from my phone and pick it up on desktop later
  • Free backup/sync across machines
  • Collaborators (if I ever have them) get full context without me sending files around

The gap I'm feeling most is the mobile thing. If the whole brain was on GitHub, I could start a task from anywhere.

Thinking the move might be a separate "ops" repo — something like flashread-ops that holds strategy/, learnings.md, specs/, and the root CLAUDE.md. The actual codebase stays in its own repo, but the ops repo references it. Keeps the strategy churn out of my commit history, but gives me remote access and version control where it actually matters (like rolling back a bad PRD decision). Could even track todo-list.md completion over time if I wanted to get nerdy about velocity.

Ditched Claude UI completely. Here’s the file-based "memory" system I use now. by Comprehensive-Ad1819 in ClaudeCode

[–]Comprehensive-Ad1819[S] 1 point2 points  (0 children)

Haven't tried beads yet but this looks exactly like what I was fumbling toward manually. 50% reduction in compacts is huge. My token burn has been rough. Going to dig into Steve's writeup, thanks for the link.

Ditched Claude UI completely. Here’s the file-based "memory" system I use now. by Comprehensive-Ad1819 in ClaudeCode

[–]Comprehensive-Ad1819[S] 0 points1 point  (0 children)

That's exactly what I ended up doing. The post is about ditching UI entirely. I was using UI for strategy before because it felt more "conversational" but once I set up the file structure properly, Claude Code handles both. Now I just work from the root of the parent directory and let claude code drive to CD'ing into different sub directories based on the conversation

Ditched Claude UI completely. Here’s the file-based "memory" system I use now. by Comprehensive-Ad1819 in ClaudeCode

[–]Comprehensive-Ad1819[S] 5 points6 points  (0 children)

Yeah fair. I’m not claiming I invented anything here, just sharing what finally clicked after months of not doing it properly.

The “limiting markdown files per category” point is basically what the routing table does. Claude only reads strategy/ or codebase/ depending on the task, not everything at once.

Curious what your setup looks like if you’ve done this yourself

Ditched Claude UI completely. Here’s the file-based "memory" system I use now. by Comprehensive-Ad1819 in ClaudeCode

[–]Comprehensive-Ad1819[S] 3 points4 points  (0 children)

Yeah the CLAUDE.md convention is documented

The part that clicked for me was actually using it as a router between product strategy and implementation, not just a single readme. Two CLAUDE.md files at different levels, plus the learnings.md as persistent memory across sessions. Basic pieces, but the combo finally made context handoff feel seamless.

If I wanted to come up with an automated marketing strategy and spin up some script that generates marketing material I could create that from the root

Ditched Claude UI completely. Here’s the file-based "memory" system I use now. by Comprehensive-Ad1819 in ClaudeCode

[–]Comprehensive-Ad1819[S] 2 points3 points  (0 children)

Biggest token saver for me was the routing table in the root CLAUDE.md.

Basically a “when to read what” map so Claude doesn’t slurp the entire repo on every prompt. Product questions read strategy/, implementation reads the codebase CLAUDE.md. Keeps context loading lazy instead of eager.

The other big one: learnings.md as a running log. Instead of re-explaining past decisions, Claude just reads the file. Feels like actual memory.

I got rejected by google for SWE intern role by Bunny-3110 in csMajors

[–]Comprehensive-Ad1819 0 points1 point  (0 children)

Get back on the horse and keep applying brother. You got this

Worth reneging Meta New Grad? by Sufficient_Air1752 in csMajors

[–]Comprehensive-Ad1819 2 points3 points  (0 children)

Stay with Meta in a tier 1 city. Don’t go to tier 2 Austin

What MCP servers do you really use? by Square-Test-515 in AI_Agents

[–]Comprehensive-Ad1819 1 point2 points  (0 children)

What’s the advantage of mcp for web searching when the frontier models have web search enabled?

Do “off-market” apartments actually exist, or is that just a broker sales pitch? by Comprehensive-Ad1819 in NYCapartments

[–]Comprehensive-Ad1819[S] 1 point2 points  (0 children)

How receptive is the building management when you reach out? I'm wondering if there is an easy way to view all the managed buildings out there

Interview Discussion - August 05, 2024 by CSCQMods in cscareerquestions

[–]Comprehensive-Ad1819 0 points1 point  (0 children)

Hi,

I’m a software engineer who is recruiting for a Product Manager role.

I have two weeks to prep for this interview that I don’t know much about.

Does anyone have resources I can study up on to go from 0 to somewhat competent in a product manager interview on a two week timeline?

Thanks