3 ms·
The code is only part of the specification. It does rarely document the actual requirements to a degree you can rely on for decision making. Sure, the code shou
by polycaster 18d ago
The code is only part of the specification. It does rarely document the actual requirements to a degree you can rely on for decision making. Sure, the code should speak for itself, but it mostly speaks about the WHYs of the implementation, not the reasoning behind the actual requirement. I found that OpenSpec actually helps a lot in this regard.
- mafro 18d agoI challenge you to use a frontier LLM to analyse your code and specs and verify if they are meaningfully aligned. Code almost never speaks to the WHY; ADRs will help there. Code never captures requirements, but it does reflect actual system behaviour, which is a specification.