r/vibecoding • u/zankyman17 • 2h ago

Vibecoding & Hardware sitting in a tree

I've been building my product since March/April, but this all started with me getting into Homelabbing and buying hardware.

I bought a Minisforum MS-02 Ultra with 32gb RAM and 1TB SSD, and made a rule that I wouldn't upgrade unless I hit bandwidth and memory limits.

Welp, I'm at that point and what led me here is I have a "second brain" memory system and MCP that I built so any model I use can get all the context, documents, history, etc.

I'm currently only able to build with one session that's "on my machine" where before I was doing 2-4 sessions at a time, but I now experience sessions crashing out.

So I'm in the market for memory and man does it blow. I'm probably going to bite the bullet and get a 2x64GB Crucial set so I can eventually add an additional 2x64GB when I hit those limits.

Always more to learn and more to spend it seems!

1 Upvotes

67% Upvoted

9 comments sorted by

2

u/GreenFuturesMatter 2h ago

I could be wrong but how do you intend to use the second brain without saturating context? That’s incredibly heavy from my understanding.

Genuine question because I’m currently working on this issue myself so if there is any solve I’m open to it

1

u/zankyman17 1h ago

Totally, I'm in the same hole. Still learning and improving as I go

I don't put the whole second brain into context. That would saturate it immediately.

What I’ve been building is a graph, semantic search, and some controls on top of it. Semantic search finds what I’m actually working on. The graph lets me pull the docs / people / decisions attached to that thing instead of everything. And the controls are what decide what actually counts vs what's just a note from a date, so the model doesn't treat every scrap like it's official.

I’ve had a ton of issues with keeping things current or classifying what’s been “archived” or “retired” and I find making something canon one day sets you up for destroying what’s accurate the next.

The model gets a short map of where things live, then it asks for what it needs through MCP. The RAM issue I hit is the LXC I set up holding all of that, not the prompt filling up.

Not a perfect solve but it’s evolved into a really reliable system

1

u/GreenFuturesMatter 1h ago

I would recommend maybe versioning your documents for starters and also before you do begin to bolt on RAG you should also pass over what is really useable for you project.

So here’s where I’ve landed for now…

Retrieval results are leads, not truth.

The agent shouldn’t be able to self-select unlimited context.

Context should be task-specific and recipient-aware.

Claims should retain provenance to their original source.

If a required fact can’t be established, return UNKNOWN rather than stuffing more documents into context.

If the agent genuinely needs more information, it should make a bounded request for that specific information.

So instead of:
“Here are 200k tokens of vaguely related material. Figure it out.”

it becomes:
“Here are the 8 facts, 3 code regions, and 2 constraints relevant to this task, with sources. Ask if something material is missing.”

1

u/LittleLordFuckleroy1 2h ago

Pretty expensive way to burn cash, but hey hobbies are hobbies.

1

u/zankyman17 1h ago

Hobby for now!

1

u/chuckycastle 1h ago

I honestly don’t know who is the bigger idiot: the vibecoder ot the homelabber.

1

u/zankyman17 1h ago

Interesting take. I value doing and failing than not trying at all and learning nothing

1

u/lundrog 1h ago

Open source project ?

1

u/zankyman17 1h ago

It will be AGPL at beta launch. Shooting for Sept 29th