Today, 03:00 PM
I can appreciate how some people like to trace back and look at the US Constitution and figure out where it went wrong.
Unfortunately, that approach will never work.
I have had to revise programs in excess of 10,000 lines of code before. This is well in excess of the length of the constitution. In a few cases, I had to perform some pretty deep surgery to a) get to the root of the problem, b) fix the problem, and c) make sure it still runs correctly. I would end up reading through and understanding the whole thing prior to trying to make a change. So I have a bit of experience in taking a huge, complex document that does something, and changing it, sometimes fundamentally. Here are some things to consider.
1) When modifying a program, there are a ton of other rules and other structure involved. You have to know the byte size of an integer on the platform you're working on. You have to know how to terminate lines of code. You have to know what documentation scraper you're using and how to format for it (and this is completely irrelevant to its actual function).
It's the same way in the US Constitution. It's a short program, sure. Written in 18th century code. If you change the byte size of an int in a program, pretty soon all sorts of unpredictable things start happening. Same as if you redefine the words "among" and "invasion".
One tiny change in one of the non-explicit rules has big effects and they are never beneficial.