3 ms·
> if you nail everything down hard, the specs get unwieldy - large and overly detailed That's a rather short-sighted way of putting it. There's no way that th
by zozbot234 9mo ago
> if you nail everything down hard, the specs get unwieldy - large and overly detailed
That's a rather short-sighted way of putting it. There's no way that the spec is anywhere as unwieldly as the actual code, and the more details, the better. If it gets too large, work on splitting a self-contained subset of it to a separate document.
- lelanthran 9mo ago> There's no way that the spec is anywhere as unwieldly as the actual code, and the more details, the better. I disagree - the spec is more unwieldy, simply by the fact of using ambiguous language without even the benefit of a type checker or compiler to verify that the language has no ambiguities.
- skydhash 9mo agoPeople are keen to forget that programming languages are specs. And a good technique for coding is to build up you own set of symbols (variables, struct, and functions) so that the spec become easier to write and edit. Writing spec with natural language is playing russian roulette with the goals of the system, using AI as the gun.