I do write code. Code only exists as a high level abstraction that codifies logic and allows us to talk about the function of the silicone without getting bogged down in details. The utility of code depends entirely on the context of the people looking at it (eg. different code works better for a small shop of experienced devs vs a large scale enterprise vs a FOSS project).
I can show you a for loop and talk in simple English about what it’s doing or write a formal proof showing that it meets the problem parameters. I could show you the compiled ASM and we would struggle to have the same conversation even with the exact same functionality. Same math, different syntactic sugar.
The process of building software is where humans will always be needed (identify the human meat space problems, define features, manage risk and cost, set delivery expectations, etc). The specifics of how we create the code within that process isn’t as crucial.
“code is just math with syntactic sugar”
Wow!
Tell me you don’t write code wihout telling me you don’t write code.
I write code, and I see the point they’re making. It has the same feel as “chemistry is just applied physics” and such.
I mean I guess I agree insofar as math at some point becomes art.
A good proof can carry beauty in its elegance, simplicity and in its phsical expressions.
But coming from the original comment, this completely contradicts the whole argument.
I do write code. Code only exists as a high level abstraction that codifies logic and allows us to talk about the function of the silicone without getting bogged down in details. The utility of code depends entirely on the context of the people looking at it (eg. different code works better for a small shop of experienced devs vs a large scale enterprise vs a FOSS project).
I can show you a
forloop and talk in simple English about what it’s doing or write a formal proof showing that it meets the problem parameters. I could show you the compiled ASM and we would struggle to have the same conversation even with the exact same functionality. Same math, different syntactic sugar.The process of building software is where humans will always be needed (identify the human meat space problems, define features, manage risk and cost, set delivery expectations, etc). The specifics of how we create the code within that process isn’t as crucial.