|
|
|
|
|
by MichaelZuo
599 days ago
|
|
No? Code is not always the same as the process or what the machine actually does... There are hundreds of posible factors from bitflips to a cable getting loose in a socket that could change either. e.g. There clearly can be a computer configured with enough memory and dense enough memory that at least one bitflip is practically guaranteed in a certain unit time, so the actual process has to include that. So the code is an abstraction just like the flowchart. |
|
You started with why aren't they "just looking at the full flowchart [to understand the entirety]".
And the parent wrote that because the flowchart is not the entirety, the code is.
Do you think this retort you make above is refuting the parent's point? If anything, it expands it, going further against your original point: that's why they're not just looking at the full flowchart.
And, yes, "code is an abstraction, just like the flowchart", but code is the abstraction the programmer controls and tries to summarize and understand. The flowchart is a higher level abstraction of an abstraction.