| ▲ | ex-aws-dude an hour ago | |
It makes me wonder if it could be solved with better context management A real developer builds up global context of the whole project over time, you always hold the overall architecture in your head Whereas with agents there is a still a lot lost between sessions Its similar in a sense that a new developer to a project does more hacky local solutions whereas the senior on the team knows when the architecture needs to change as part of a fix | ||
| ▲ | user43928 an hour ago | parent | next [-] | |
I think it's rather a problem with the training pipeline incentivizing correctness and endlessly defensive code over simplicity and maintainability of the implementation. The problem with context I see primarily in mixing up user intent and hard requirements with random half-correct notes some other agent left in the comments. | ||
| ▲ | Unproven4275 38 minutes ago | parent | prev | next [-] | |
> Whereas with agents there is a still a lot lost between sessions Are y'all using AI agentic frameworks? I don't have a lot of issue with anything being lost between sessions, I have active memory and context management and have my agents write up documentation for each project to pick up where they left off or to hand it off if needed. | ||
| ▲ | philipwhiuk an hour ago | parent | prev [-] | |
> It makes me wonder if it could be solved with better context management There's a reason that repos are now bloated with AGENTS.md files that try to cram context in as pre-text. And that there's so many vibe-coded context/memory aggregation frameworks. It's an AI-hard problem. | ||