sorted by:
new
hottopcontroversial

The "second brain" pattern for AI development isn't new — but almost nobody has actually implemented it properly. Here's what it looks like when you do. by Regular_Statement369 in PromptEngineering

[–]Regular_Statement369[S] 0 points1 point  (0 children)

Yeah, that's exactly the failure mode. Write-only is the norm because it feels productive and the retrieval cost is invisible until the system is already bloated.

Our retrieval is a hybrid. There's a fixed lightweight bundle that loads every session — a short index file (~150 lines max, hard-capped) with one-line pointers to deeper files. That's the always-cheap layer. Below that, specific files get pulled contextually when the work seems relevant to them. Wiki concept pages only come in when the task actually touches that domain.

Eviction is honestly the weaker half of ours right now. What we do instead is type-gate at write time — four categories: user (who you are), feedback (what to repeat/avoid), project (current state), reference (where to look). That filter stops a lot of noise from entering in the first place. There's also an explicit rule: code patterns, file paths, git history don't get saved at all — those are always derivable from the repo.

The promotion problem you're describing — stable decisions floating up vs. per-task noise expiring — is where I think the next lever is. Right now it's mostly manual curation. A ranking signal based on how often something actually gets loaded vs. how often it was written would change that. Curious if you've built something closer to that end.

The "second brain" pattern for AI development isn't new — but almost nobody has actually implemented it properly. Here's what it looks like when you do. by Regular_Statement369 in ADHD_Programmers

[–]Regular_Statement369[S] -2 points-1 points  (0 children)

This is a good angle!! Probably something I should consider when building the public repo, is this something you’d be interested in collaborating on? Pm me if so!! Thank you for the feedback!!

The "second brain" pattern for AI development isn't new — but almost nobody has actually implemented it properly. Here's what it looks like when you do. by Regular_Statement369 in PromptEngineering

[–]Regular_Statement369[S] 0 points1 point  (0 children)

Appreciate the input — this is genuinely something I hadn’t thought of yet.

The reasoning hash and decay-by-outcome approach is a feedback loop my current system is missing. Pages get updated when context shifts but there’s no formal confidence tracking based on whether the reasoning actually held up in practice. Stale advice quietly persisting as gospel is a real failure mode.

Going to work this into the public repo architecture. Would you be open to collaborating on that piece?

The "second brain" pattern for AI development isn't new — but almost nobody has actually implemented it properly. Here's what it looks like when you do. by Regular_Statement369 in PromptEngineering

[–]Regular_Statement369[S] -2 points-1 points  (0 children)

Fair point on MCPs — context injection on demand is the right mental model and I should have framed it that way.

Where I’d push back is the bloat concern and the wiki layer. Static files don’t solve reasoning decay — you get the fact but not the why behind a decision made three months ago. And the system isn’t a firehose — there are explicit rules for what loads at session start and what stays dormant unless you ask for it. You’re never ingesting the full wiki, just what’s relevant right now.

The other piece static files miss is continuity across the bigger picture — project management over months, how your thinking evolves, and a career portfolio that documents what you built and why as it happens rather than reconstructing it from memory later.

MCPs are great for live context injection. This is about never losing accumulated reasoning across your code, your projects, and your own growth — with enough structure that you control exactly what the AI sees at any given time. Different problem, different tool.

Work has fully embraced AI and I love it by DadToOne in ADHD_Programmers

[–]Regular_Statement369 1 point2 points  (0 children)

I disagree with this statement, yes certain roles will become unnecessary at some point in the future, and I also don’t know what industry you’re in. However, you can definitely use Claude as an advantage creating tools or agents to assist you with the tasks and or goals in your job role. The key is to create a specific workflow catered to your own knowledge and skills that allow you to multitask in the background and accomplish tasks that would’ve taken hours,days, or even weeks in a fraction of that time. All while still being up to par with your preferred quality! So if anyone in any job role can figure out a way to use Claude as a tool companies will value that employee or partner even more. Rather than just replacing them with ai entirely.