Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>Code is merely the leanest human-readable representation for loss-less specification of requirements.

I think you might have meant "loss-less specification of the current design." requirements are aspirational, and signifies the intent, code is the loss-less version of how the system will actually behave.



No, I meant requirements.

Stated otherwise: "Sufficiently advanced requirements are indistinguishable from code".

Abstracted requirements define outcomes. Fine-grained requirements define code.


I respectfully disagree.

The customer has given a requirement that states the variable <y> has to be calculated as y= x +1.

However, the code that exists has been implemented such that <y> is calculated as y= x - 1.

y=x-1 is how the current system behaves. However it conflicts with the actual requirement, which is y=x+1.


Regardless of whether or not the code is correct, it's still defining the behavior of the system.

If the customer would like to describe the ideal behavior of the system, the only way is to translate it into code.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: