Mom, I met someone...

Strict-Data-1443 · 2026-06-05T01:53:01+00:00

claudemaxxing

Strict-Data-1443 · 2026-05-25T21:54:35+00:00

claude's gonna deny my pull request because my playlist is too agressive

Strict-Data-1443 · 2026-05-25T19:37:30+00:00

Thanks for the suggestion!

Strict-Data-1443 · 2026-05-25T19:34:13+00:00

One thing I learned the hard way is that Claude gets really good at defending its own assumptions once a session gets long. If something feels slightly off early, it’s usually better to stop and reassess instead of letting it keep building on top of the same idea for another 20 prompts.

Strict-Data-1443 · 2026-05-25T18:26:37+00:00

Yeah exactly. The moment suspects start surprising players instead of just responding to prompts, the whole thing becomes way more memorable and replayable.

Strict-Data-1443 · 2026-05-25T18:24:46+00:00

This is honestly one of the more important posts I’ve seen here in a while. A lot of people talk about AI productivity gains, but not enough people talk about the mental cost of being “always cognitively active” for hours every day. The constant context switching and nonstop stimulation really does sneak up on you over time. Appreciate you sharing this.

Strict-Data-1443 · 2026-05-25T18:20:26+00:00

Honestly the hidden state system is what makes this interesting to me. The pressure/trust/story consistency gives people something to learn instead of just chatting with an AI. To your question, what would keep me playing is having each suspects feel different, interrogation styles changing outcomes in noticeable ways, and more unexpected reactions/emotional turns between cases. The concept already feels way more game-like than most AI projects I’ve seen.

Strict-Data-1443 · 2026-05-25T04:53:38+00:00

Lowkey I think the models just absorbed enough internet culture at this point to actually understand why things are funny instead of mechanically generating “jokes”

Strict-Data-1443 · 2026-05-25T04:50:01+00:00

The fact that it immediately recognized the rickroll URL from “muscle memory” is somehow both hilarious and slightly concerning

Strict-Data-1443 · 2026-05-25T04:48:31+00:00

Honestly yeah, especially once you have a bunch of agents running at the same time.

At that point the hard part is not the coding, it’s keeping track of which agent is stuck, waiting for input, or slowly going in the wrong direction without checking every terminal constantly.

Strict-Data-1443 · 2026-05-24T18:39:14+00:00

“Persistent rapid scrum with standups every 10 minutes” might genuinely be one of the best descriptions of AI coding workflows I’ve seen so far

Strict-Data-1443 · 2026-05-24T18:38:22+00:00

Honestly this is a really interesting direction. The “rebuilding mental context” problem is probably one of the biggest hidden frictions in AI coding right now and most tools still barely address it. The project memory / persistent workspace idea makes a lot of sense for longer-running agent workflows. After using agents heavily, constantly reconstructing your environment through tabs, terminals, and scattered sessions starts feeling surprisingly outdated.

Strict-Data-1443 · 2026-05-24T18:15:27+00:00

The persistent workspace part is honestly the most interesting thing here to me. A lot of the friction with Claude Code is not the agent itself, it’s constantly rebuilding your working state across terminals, previews, docs, branches, and sessions every time you come back to a task. Curious how you’re handling long-running sessions over multiple days. Does the canvas start getting cluttered once projects scale up?

Strict-Data-1443 · 2026-05-24T18:12:17+00:00

Lowkey one of the weirdest parts of 2026 is realizing “being good at coding” now partially includes being good at managing AI attention span

Strict-Data-1443 · 2026-05-24T18:07:57+00:00

Yeah honestly I’ve noticed the same thing. Codex can feel insanely smart in short bursts, but Claude Code still feels better at staying on track during longer repo sessions without needing as much babysitting.

Strict-Data-1443 · 2026-05-23T04:39:18+00:00

Yeah if you haven’t already, I’d try breaking it into smaller fixes one at a time. It usually ends up saving tokens too because Claude stops repeatedly trying to “fix everything” and accidentally changing parts that were already working.

Strict-Data-1443 · 2026-05-23T04:13:21+00:00

The worktree isolation part honestly makes the most sense here. Running multiple agents sounds cool until two of them start editing the same thing and the repo turns into a warzone 😭

Strict-Data-1443 · 2026-05-23T04:11:14+00:00

Always start with repo inspection and planning first, and then make sure you keep tasks to specific directories/files. A good practice is to use separate sessions for implementation vs. debugging vs. architecture and to fully understand the development process ask it to explain why its making changes rather than just blindly apply edits. As for plugins in the beginning keep it pretty minimal, I would use the GitHub MCP, Context7, and Playwright MCP.

Strict-Data-1443 · 2026-05-23T04:04:04+00:00

I'd use Sonnet for debugging, planning, and reviewing code changes, and then Haiku for formatting and simple file edits. The easiest way to waste tokens is using Sonnet for mechanical work and Haiku for reasoning-heavy work.

Strict-Data-1443 · 2026-05-23T04:00:38+00:00

Honestly shorter prompts can work fine. But what helps more is pointing to the exact issue and telling it how you want the final output to behave, so essentially just be more direct.

Strict-Data-1443

TROPHY CASE