621–625 of 625 posts
Earlier quoted context omitted.
If you don't have a record of questions asked/answered and rationale for decisions taken, I've noticed it's easy for subsequent feature plans to clash. Maintaining a line of consistency across each feature plan is a good thing.
I think thats what docs/comments are for, ask your agent to add/maintain them
Earlier quoted context omitted.
MCP server with RAG to feed it back to agents when they are working on a piece of code, and bob's your uncle
That sounds like word salad, not a clearly articulated solution to a well-understood customer problem.
This means that the agent will can have context of previous decisions, something that they currently struggle with as they are always starting from a blank slate.
Earlier quoted context omitted.
That sounds like word salad, not a clearly articulated solution to a well-understood customer problem.
In simpler terms - they create an MCP server, essentially an API that the coding agent can call, that can fill in context about previous decisions done by the coding agent earlier in development. Agent equivalent of asking someone who's been working there longer "why is this this way". This means that the agent will can have context of previous decisions, something that they currently struggle with as they are always…
I'm not making a judgement on the product but why is everything about selling shovels? I want to see "real" software and new innovative ideas that are developed and maintained using AI and not just shovels 'advertised' on HN every week. Show me the next blockchain or noSQL, or git! Everything is "I took a prompt and stapled it to another prompt and added framework".. and then. holds hand out "MONEY PLEASE!"