I fail to see what blockchain can provide in the realm of audit logging?
Fundamentally, you need to trust the systems which are logging events to log the correct events at the correct time. How does blockchain change this?
I fail to see what blockchain can provide in the realm of audit logging?
Fundamentally, you need to trust the systems which are logging events to log the correct events at the correct time. How does blockchain change this?
It always bothers me when it says "no smoking" first and then "safety first" second. If you are serious about safety first, put it first!
Or it is because Genesis is copy pasted together from two slightly different original sources. One where man and woman were created on the same day and one where Eve was created after Adam.
Chill people usually don't go straight to waving their constitutional rights in other people's faces at the first sign of any minor disagreement.
Why would it be redundant? You can’t even get past the main function before dealing with a char**
According to an unsourced claim on Wikipedia, "repetition is the essential comedic device"
Hire someone to manage my money.
“Hundred” in Germanic Europe used to be 120 before the Romans came and introduced their “century” with a value of 100. This is still known as “the long hundred”
12, 60, 120, 360 are the first superior highly composite numbers. https://en.m.wikipedia.org/wiki/Superior_highly_composite_number
These number divides neatly into integer parts in many ways for their size.
They are also the basis of many pre decimal counting systems, some of which are still around. 360 degrees in a circle. 12 hours in a day.
The Babylonian’s used base 60. We still do for time as you pointed out. The minute refers to a minute(as in small) part of something. The “second” is the “second minute”. Ie a minute divided into minutes. This system is also used for geodetic cordinates. Where we have arc minutes and seconds.
There are many reasons one might use inheritance. The one which is often first introduced by OOP proponents is creating a “is-a” relationships in some domain model where the goal is to somehow model “real life” with classes and objects.
This always ends badly in my experience. Not worth doing. Just consider the “rectangle square controversy” https://henrietteharmse.com/2015/04/18/the-rectanglesquare-controversy/. Inheritance as a domain modelling tool doesn’t really mean anything outside of textbooks talking about animals and vehicles.
One should understand how computers and programming work and model data in a way which makes sense for the concrete scenario. Look in any algorithms and data structures book. Nothing is ever explained and presented through object models. No UML diagrams needed.
But inheritance also bring actual concrete functionality. In particular dynamic single dispatch. If you need dynamic single dispatch, inheritance is good. That being said, I think that parametric polymorphism (“generics” in OOP terminology) is a better solution than subtype polymorphism in almost all cases. Although languages build around OOP and inheritance sometimes make it too inconvenient to use.
Twix are chocolate bars which comes wrapped two identical pieces in one wrapper. OP can apparently tell the difference by taste which is absurd.
Is this real?
That would then be an entirely different situation?