To be fair, this person clearly said it was a "gut" feeling, and it is also ok to be wrong about things, since being corrected on saying a wrong thing is a wonderful way to learn.
Perhaps she knew that we would read her words, all of these centuries later, and see her for the bright, creative human being that she was. I hope she would take some solace knowing that we of the future see her condemnation as unjust, stupid and evil.
You mean like some kind of organisation designed to regulate the behaviours of businesses and individuals over the long term such that the general population isn't exploited or abused by the few, and tragedy of the commons style problems can be avoided?
They're a freight-forwarder branding themselves as a software company, competing with the likes of DHL, DSV and 100s of other smaller organisations. In short, they have a very viable business model, but freight forwarding is a cut-throat industry.
This is not generally the case. Practically speaking, big O notation is almost always bounded. The clojure vector implementation has a maximum count of 2^32, therefore the behaviour at infinity is O(SomeException)
You know this would mean that a change to a vector under 32 elements is O(n) right? (Which it isn't quite in all cases, because the actual implementation is a bit more complex)
But this doesn't apply to hashset because hashmaps are sparse, and stored as pairs, meaning that they're effectively base 16. Also the clojure implementation of sets is just hashmaps where the key is the same as the value.
An order of magnitude is not necessarily a factor of 10. Otherwise we would always just say, "factor of 10" which has fewer syllables. The difference between O(logn) to O(1) is often referred to as an order of magnitude. As is O(logn) to O(n).
To drill down into this, adding or removing from a vector or hashset in clojure is O(logn). This also means that random access is also O(logn).
Most operations on clojure persistent data structures are an order of magnitude less efficient than they are on the mutable equivalents, excepting a full copy which free due to it being unnecessary.
It's referring to metaprogramming. Lots of large programs end up full of DSLs and config files with bespoke parsers and code generators, which are largely inferior (in that they are bloated, bespoke and less expressive) to the metaprogramming tools available in Common Lisp.
You explicitly said logging is a form of "unit test" which has a very specific meaning and a log is not it. Observing a log can obviously be part of an assertion in a test be it manual or whatever, but an assertion is not a unit test.
A log statement isn't a unit test in the same way that apples aren't trees. A unit test is a discrete, runnable program that asserts some state about your program to be true, whereas a log is just some subsystem of your overall program that prints some output with no pass/fail condition.
You may have a unit test that makes assertions about logs though? I would definitely expect somebody that isn't a junior programmer to understand this.
That's not immutability, that's "log shipping". And if an organisation doesn't have the capability to delete personal data from it's backups, and it operates in Europe, chances are that it's in violation of GDPR and could be subject to millions of Euro's in fines.
GDPR and the right to having your personal data deleted certainly puts a bit of a stopper on using an immutable database for anything personally identifying.
The wisdom of, "private sector is more efficient than government" only applies when there are market incentives for efficiency: Specifically, there must be competing private businesses to lower costs, and the market consumers must not suffer from extreme negative consequences (e.g. death or homelessness) for refusing to participate.
There is ample opportunity to strawman the advice in this book and invent scenarios where it does not apply.
I'd say that it is something of a cultural phenomenon of our times that we get these angry criticisms of opinions rather than acceptance and tolerance of views different to our own. I think we'd all be better off if instead of looking for reasons to invalidate opinion pieces and etiquette advice, we value them as opportunities to better understand other people's thinking. There is not much use getting upset about these kinds of things because it's not going to be in our power to change them anyway.
It's never too late to learn the meaning of a new word. Why just yesterday I was reading The Count of Monte Cristo, where the author used "felicity" in a context I'd not seen before. Fortunately in my very pocket was a powerful device that includes a dictionary unsurpassed in the history of mankind, and thus my brief ignorance was swiftly overcome! Perhaps the author meant to exclude me? Oh dear...
You see wind instruments outside of orchestras all the time though. The main reason for the domination of guitar and piano is economic: you can play more notes at once and therefore have played richer sound with fewer players. You can split the gig money across less people. It really has nothing to do with the number of wind players that can transpose.
Firstly because it makes me laugh, but also it's because it's actually gatekeeping other people's language that is excluding and antisocial. I firmly believe that we ought to accept the language that others use when the speakers intention is clear, even if they "don't speak good". The uneducated don't deserve scorn by default just because nobody rapped them across the knuckles when they used "coz" instead of "because". And that's ignoring even that many of these grammatically incorrect but often used phrases come from minority groups and shitting on people for using them is actually a subtle avenue for (probably unintended) racism.
I enjoy collecting little things like this to annoy the grammar gatekeepers. Why say "regardless" when "irregardless" means the same thing but also annoys prescriptivists? "Ironical" instead of "ironic" and "less" instead of "fewer".
Now that I know, "comprised of" fits in this category, it's definitely going to be a part of the everyday lexicon.
Musicians need to know the sharps and flats in different keys in order to transpose, and musicians need to be able to play something they have rehearsed accurately, and musicians need to be able to play all across a large range.
Testing scales tests all of these things, and more simultaneously. I fail to see the problem. If you're as good at sight-reading as you say, you can just read the scales off the sheet music and play them all perfectly the first time, so what's the problem?