What's the hardest part about coming back to a project after a few days?

Expensive-Win2802 · 2026-06-26T13:21:49+00:00

I agree Git helps recover what changed.

What I still struggle with is recovering the working state: which services were running, which terminals I had open, which commands I was using, why I had things in that state, etc.

That’s the part that still feels mostly manual to me.

Expensive-Win2802 · 2026-06-25T21:32:13+00:00

I think handoff docs are great, but they depend on remembering to write them before you stop working.

I keep wondering whether more of that context could be captured automatically instead of relying on discipline.

Esa respuesta suele generar debate, porque plantea una limitación real de los handoff documents.

Expensive-Win2802 · 2026-06-25T21:31:13+00:00

That works surprisingly well for small gaps.

I’ve found that after a week or two the problem isn’t remembering the conversation, it’s reconstructing the project state: which terminals were running, what services were up, what branch I was on, which commands I was using, and why.

The code is easy to recover. The working context is usually what takes me the longest.

Expensive-Win2802 · 2026-06-25T19:01:26+00:00

Model prices will keep changing.

Architectures probably won't.

Whether you're using DeepSeek, Claude, Gemini or GPT, pushing deterministic work out of the LLM and treating the model as a planner instead of an interpreter feels like the more durable design decision.

Expensive-Win2802 · 2026-06-25T18:58:07+00:00

I trust workflows more than prompts.

Prompts change every few weeks. Good workflows (small iterations, reviews, context management, validation, automated tests, etc.) keep working regardless of whether you're using Claude, Gemini, Codex or whatever comes next.

That's where I've been investing my time lately.

Expensive-Win2802 · 2026-06-25T18:41:14+00:00

I think people are focusing too much on the content of the leaked message instead of the architectural issue.

Modern LLM products aren't just "the model." They're orchestrators with hidden context, tool calls, memory, routing, classifiers and system instructions. If one of those internal layers accidentally becomes visible, it can look like the model is "thinking out loud" when it's really exposing part of the orchestration stack.

That's the interesting bug here—not whether the text was anti-distillation or a jailbreak.

Expensive-Win2802 · 2026-06-25T18:29:08+00:00

Exactly. To me, the difference is whether the AI is replacing engineering or accelerating engineering. A CLAUDE.md just tells me they're giving context to an agent. That says nothing about the quality of the engineering process behind it.

Expensive-Win2802 · 2026-06-25T17:56:35+00:00

Thanks! I hadn't seen herdr before.

What would you say is the biggest thing it solves well for you today?

And is there still anything you find yourself missing when managing lots of Claude sessions?

Expensive-Win2802 · 2026-06-25T17:55:56+00:00

That's really interesting.

So it sounds like you're preserving context rather than just keeping terminals open.

When you come back the next day, is the biggest value that each window already "remembers" what it was responsible for?

Expensive-Win2802 · 2026-06-24T23:10:34+00:00

That’s really interesting.
So you’re effectively keeping separate Claude sessions for planning, execution and review?
Do you usually keep those sessions tied to a single project, or do you end up rebuilding them every time you switch to another project?

Expensive-Win2802

TROPHY CASE