News for hackers. Stuff that matters.
Re:When Figma Starts Designing Us by sillyfluke on Tuesday July 08, 2025 @06:54AM (#44498856)
>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.

Re:When Figma Starts Designing Us by screye on Tuesday July 08, 2025 @10:31AM (#44500355)
No, I meant requirements.

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

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

Re:When Figma Starts Designing Us by sillyfluke on Tuesday July 08, 2025 @01:40PM (#44502258)
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.

Re:When Figma Starts Designing Us by SR2Z on Wednesday July 09, 2025 @08:00AM (#44508935)
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.