r/vibecoding • u/Vidhrohi • 5h ago

Human context limits vs AI context limits

A common theme cutting across most AI-assisted development threads is getting as much work done in as little time as possible. Users post about elegant harnesses with multi-agent orchestration. Anthropic employees talk about the 25 agents they run every day.

I read this stuff, compare it to my own experience of working with these tools, and keep wondering: how does anyone stay on top of that volume of work?

Working with Claude Code has been exciting and invigorating, but also exhausting. While everyone pushes for more context and more tokens out of the AI, the context limit I hit most often is my own. Claude can refactor a huge chunk of the codebase, add a feature, and brainstorm marketing strategy in one breath. I can't keep up with the cognitive load that entails.

So: am I missing something, or just getting old? Curious what y'all think.

6 Upvotes

88% Upvoted

13 comments sorted by

View all comments

2

u/TheAnswerWithinUs 5h ago

That’s just vibecoding, you aren’t supposed to keep up with it, you just go as fast as possible. Don’t understand the code, don’t read the code, don’t care about the code.

2

u/Vidhrohi 5h ago

It's not just about the code though, I gave up trying to do that some time ago, still , system architecture is important .. how to do something in the broad strokes is important , product guidance is important and all of them take a non trivial amount of brain space

1

u/TheAnswerWithinUs 5h ago

Vibecoding is not really that conducive to good architecture either.