Hacker News new | past | comments | ask | show | jobs | submit
What about design decisions or code quality? Tests don't cover those.
I built a system that records numbered design decisions and numbered requirements as claude works in a Postgres database organised as a graph with links/interconnection between items.

It's an MCP server that Claude uses as we develop so there's a permanent record of everything and work is driven by requirements and decisions.

loading story #50541334
I've seen dozens of those, Claude even suggests building them, and they are all crap after a month. Just updating all the references of decisions becomes onerous. Make one change, it cascades everywhere, eventually all turns to utter crap. The gastown project failed in part due to agents inability to continuously carry context and it kept working on the information system instead of the problems. Good luck to you.
loading story #50540085
You could argue that the code quality is irrelevant since code is cheap now. Not saying I personally agree with this, I've just heard it.

Architecture and design decisions may be the only things that matter.

If it ain't testable or can't be automatically enforced with some other form of guardrails then it doesn't matter.