✳flâneur — a map of the web's best reading

Why Eliot? — Eliot 1.14.0+0.g3584072 documentation

eliot.readthedocs.io · 750 words · saved by 1 readers

Suppose we turn from outside estimates of a man, to wonder, with keener interest, what is the report of his own consciousness about his doings or capacity: with what hindrances he is carrying on his daily labors; what fading of hopes, or what deeper fixity of self-delusion the years are marking off within him; and with what spirit he wrestles against universal pressure, which will one day be too heavy for him, and bring his heart to its final pause. The log messages generated by a piece of software ought tell a story: what, where, when, even why and how if you’re lucky. But most logging systems omit the all-important why. You know that some things happened, but not how they relate to each other. Most log messages in your program are going to involve actions: A marriage has a beginning and eventually an end. The end may be successful, presuming “until death do us part” is a form of success, or a failure. The same is true of all actions, much like function calls in Python are started and

Why Eliot? - Eliot 1.14.0+0.g3584072 documentation --> Docs >> Why Eliot? Edit on GitHub Why Eliot? ¶ Suppose we turn from outside estimates of a man, to wonder, with keener interest, what is the report of his own consciousness about his doings or capacity: with what hindrances he is carrying on his daily labors; what fading of hopes, or what deeper fixity of self-delusion the years are marking off within him; and with what spirit he wrestles against universal pressure, which will one day be too heavy for him, and bring his heart to its final pause. — George Eliot, Middlemarch The log messages

Explore this link on the map →

related reading