Programs are a socially constructed artifact that help communicate and express a model (which is perpetually locked in people's heads with variance across engineers; divergence is addressed as the program develops). Determining what should or should not be done is a matter of not just domain knowledge, but practical reason, which is to say prudence, which is a virtue that can only be acquired by experience. It is an ability to apply universal principles to particular situations.
This is why young devs, even when clever in some local sense, are worse at understanding the right moves to make in context. Code does not stand alone. It exists entirely in the service of something and is bound by constraints that are external to it.
The classic text is Nielsen and Chuang's "Quantum Computation and Quantum Information" [0]. Whatever else you choose to supplement this book with, it is worth having in your library.
Nielsen and Chuang has the clearest exposition of quantum mechanics I've seen anywhere. Last year I was trying to learn quantum mechanics, not necessarily quantum computation, just out of a general interest in theoretical physics. I started with physics textbooks (Griffiths and Shankar) but it only really "clicked" for me when I read the first few chapters of Nielsen and Chuang.
No, although the popular uses of the word “religion” are notoriously vague and ill-defined, so you would have to elaborate.
Natural law ethics grounds morality in human nature. A good action accords with the telos of human nature. An evil one frustrates it. Aristotle is perhaps the best known defender of it on purely rational grounds.
"Laying the foundations for integral calculus and foreshadowing the concept of the limit, ancient Greek mathematician Eudoxus of Cnidus (c. 390–337 BC) developed the method of exhaustion to prove the formulas for cone and pyramid volumes.
"During the Hellenistic period, this method was further developed by Archimedes (c. 287 – c. 212 BC), who combined it with a concept of the indivisibles—a precursor to infinitesimals—allowing him to solve several problems now treated by integral calculus. In 'The Method of Mechanical Theorems' he describes, for example, calculating the center of gravity of a solid hemisphere, the center of gravity of a frustum of a circular paraboloid, and the area of a region bounded by a parabola and one of its secant lines."
"Bhāskara II (c. 1114–1185) was acquainted with some ideas of differential calculus and suggested that the "differential coefficient" vanishes at an extremum value of the function.[18] In his astronomical work, he gave a procedure that looked like a precursor to infinitesimal methods. [...] In the 14th century, Indian mathematicians gave a non-rigorous method, resembling differentiation, applicable to some trigonometric functions. Madhava of Sangamagrama and the Kerala School of Astronomy and Mathematics stated components of calculus. They studied series equivalent to the Maclaurin expansions of [redacted] more than two hundred years before their introduction in Europe. [...] however, were not able to 'combine many differing ideas under the two unifying themes of the derivative and the integral, show the connection between the two, and turn calculus into the great problem-solving tool we have today.'"
Programs are a socially constructed artifact that help communicate and express a model (which is perpetually locked in people's heads with variance across engineers; divergence is addressed as the program develops). Determining what should or should not be done is a matter of not just domain knowledge, but practical reason, which is to say prudence, which is a virtue that can only be acquired by experience. It is an ability to apply universal principles to particular situations.
This is why young devs, even when clever in some local sense, are worse at understanding the right moves to make in context. Code does not stand alone. It exists entirely in the service of something and is bound by constraints that are external to it.