asgard1024
Joined 13 years ago
Joined 13 years ago
Addendum: It might be true that in the nation as in the household, you should be aware if you are entering an external contract with someone, like borrowing money. But the question of internal debt between the citizens of the nation cannot be reduced to household economy, there is no such thing as an austere husband lending money to his wife.
I think social credit systems are wrong, the moral behavior shouldn't be tradeable. But let's face it, almost all societies have them, and they have many flaws.
Not to mention that it has a little bit of a scent of white man's burden.
And BTW, I do believe in universality of human rights, I don't care what the consensus is. While I agree with Bregman, I think it is kind of a moot point (as any argument from nature), because the values we have (or rather decisions we make) are much more a function of the environment we live in.
I believe that you always test two implementations. For example, if I have a test case for a function sin(x), then I compare with the calculator implementation, from which I got the result. So if the tests are to be comprehensive (and automatically executed), then they have to be another implementation of the same program, you can't avoid it, and you can't avoid to (potentially) have bugs in it.
Now, the advantage is that the test implementation can be simpler (in certain cases); or can be less complete, which means less bugs, but also (in the latter case), less comprehensive testing.
In any case, you're validating the assumptions. The assumptions come from how the test implementation works (sometimes it is just in your head). And to express them formally, of course, that's the whole point.
For example, if you're given an implementation of sin(x) to test with, you can express formally the assumption that your function should give a similar result.
By formalizing this assumption, you can then let the computer create the individual test cases; it is a superior technique than to write test cases by hand.
Interestingly, I personally find them easier to write. I actually find classic unit tests hard to write, probably because I am painfully aware of the lack of coverage.
While with property-based testing, I start from the assumption I have on what the code should do. Then the test basically verifies this assumption on random inputs.
Doing unit test with the given input seems to me backwards - it's like a downgrade, because I always start from what kind of assumption I have and based on this I choose the input. And why not encode the assumption, when you already have it in your mind anyway?
This might also be relevant: http://number-none.com/blow/john_carmack_on_inlined_code.htm...
So when somebody creates an IOU trusted enough so it could be resold, they have effectively created "money" according to the above definition, because now that IOU can be traded _independently_ of the thing it was originally exchanged for.
I think what confuses lot of people about this is that creation of money is a 3-sided transaction, and we are conditioned to think of a market economy as a sequences of 2-sided transactions.
Also, what I find very funny, some libertarians want to impose government to only create money backed by a commodity, like a gold standard. Yet their fundamental axiom is to allow any two parties to enter (almost) any contract, in particular, allow them to create and resell IOUs. However, if the government has to enforce any contract that two parties can come up with, this is already giving too much freedom for the money to be created regardless of the actual commodities in existence, and regardless what the government does.
So Trump is trying to make a deal with Snowden - find some dirt on Democrats (Obama administration) during election, and I will pardon you.
However, Snowden is most likely not a spy, so no way this is gonna happen.
No way! IBM mainframe (zSeries) is the gold standard for backward compatibility in IT.