Quote of the Day
If you enjoy programming, philosophy, math, or any number of geeky topics, you're in the right place. Every day, I'll post a random quote from my extensive collection of Kindle highlights. Quotes do not necessarily reflect my views or opinions. In fact, part of my epistemic process is to consume a wide variety of contradictory material.
11/22/2020
I am wiser than this man; it is likely that neither of us knows anything worthwhile; but he thinks he knows something when he does not; whereas when I do not know, neither do I think I know; so I am likely to be wiser than he is to this small extent, that I do not think I know what I do not know.
— Plato and Benjamin Jowett (Translator), Dialogues on the Trial & Death of Socrates
11/21/2020
…people mistakenly think about interests, I pointed out. They don’t realize they need to play an active role in developing and deepening their interests.
— Angela Duckworth, Grit
11/20/2020
For nearly all of history, people’s lives have been governed primarily by ignorance. … Failures of ignorance we can forgive. If the knowledge of the best thing to do in a given situation does not exist, we are happy to have people simply make their best effort. But if the knowledge exists and is not applied correctly, it is difficult not to be infuriated. … It is not for nothing that philosophers gave these failures so unmerciful a name—ineptitude.
— Adam Barr, The Probelem With Software
11/19/2020
A common misconception about bitcoin transactions is that they must be “confirmed” by waiting 10 minutes for a new block, or up to 60 minutes for a full six confirmations. Although confirmations ensure the transaction has been accepted by the whole network, such a delay is unnecessary for small-value items such as a cup of coffee. A merchant may accept a valid small-value transaction with no confirmations, with no more risk than a credit card payment made without an ID or a signature, as merchants routinely accept today.
— Andreas M. Antonopoulos, Mastering Bitcoin
11/18/2020
…it is often necessary for the software requirements gathering process to be (a) iterative (it is difficult to be sure at first glance which requirements are relevant to the software), and (b) interactive (software requirements gatherers must interact with requirements gatherers from other disciplines to divide up the requirements properly).
— Robert L. Glass, Facts and Fallacies of Software Engineering
1970 post articles, 394 pages.