[1] https://www.law.cornell.edu/uscode/text/28/part-II/chapter-3...
If you look at code as in, only syntax and its meaning for the language, I can see how folks might reason along the lines of 'law is similar enough to code. You are saying what can and can't be done'
However, code is rarely only its syntax. Its meaning is contextual, often to the business of which it applies, and would have no real meaning outside of that context, and context may change at any given time, which means reinterpreting the code, replacing the code etc.
That is what law in practice, is what code is in practice. Its syntax is very technical, but its meaning is entirely dependent upon its applied context.
I been thinking alot about this lately, and understanding the sociological implications of code in an organization (or in more extreme cases, society) has really changed my point of view of how to build software
If I were to translate this into code, it would mean that variables that were constant will sometimes still change value. It would mean that operations on data would differ depending on the scope in which the operations were applied. And it would mean that certain variables that were closer to the base address (more money) would operate differently than variables stored in distant memory offsets [2].
[1] https://en.m.wikipedia.org/wiki/Plaxico_Burress#:~:text=On%2...)
[2] https://en.m.wikipedia.org/wiki/Trial_and_sentencing_of_Robe...
If this were really true, there would be zero appellate cases (and probably not even trial cases, as the clear and only correct resolution would be apparent to all parties without a trial which would only add expense) in these areas, and yet... That's very much not the case.
If law, even in these areas, is “code”, it is so more in the sense of the Pirates Code in Pirates of the Carribean, not computer software.