Quotes

Becoming a good engineer is about collecting experience. Each project, even small ones, is a chance to add new techniques and tools to your toolbox. Where this delivers even more value is when you can solve problems by pairing techniques learned on one project with tools learned working on another. It all adds up.

Most people are theists not because they were 'reasoned into' believing in God, but because they applied Occam's razor at too early an age. Their simplest explanation for the reason that their parents, not to mention everyone else in the world, believed in God, was that God actually existed. The same could be said for, say, Australia.

I never am really satisfied that I understand anything; because, understand it well as I may, my comprehension can only be an infinitesimal fraction of all I want to understand about the many connections and relations which occur to me, how the matter in question was first thought of or arrived at, etc., etc.

Every time an engineer evaluates a language that isn’t “theirs,” their brain is literally working against them. They’re not just analyzing technical trade offs, they’re contemplating a version of themselves that doesn’t exist yet, that feels threatening to the version that does. The Python developer reads case studies about Go’s performance and their amygdala quietly marks each one as a threat to be neutralized. The Rust advocate looks at identical problems and their Default Mode Network constructs narratives about why “only” Rust can solve them. We’re not lying. We genuinely believe our reasoning is sound. That’s what makes identity based thinking so expensive, and so invisible.

I cannot think it unlikely that there is such a total book on some shelf in the universe. I pray to the unknown gods that some man—even a single man, tens of centuries ago—has perused and read this book. If the honor and wisdom and joy of such a reading are not to be my own, then let them be for others. Let heaven exist, though my own place may be in hell. Let me be tortured and battered and annihilated, but let there be one instant, one creature, wherein thy enormous Library may find its justification.

Explanations are not offered gratuitously, just because (say) ice happens to float. I can explain nothing to you unless I first draw your attention to patent inadequacies in your knowledge: discontinuities in the relations between objects, or the presence of anomalies you cannot account for with your laws. You will remain deaf to my explanations until you suspect yourself of falsehood...Explanations establish islands, even continents, of order and predictability. But the regions were first charted by adventurers whose lives are narratives of exploration and risk. They found them only by mythic journeys into the wayless open.

[...] i was too busy with work to read anything, so i asked chatgpt to summarize some books on state formation, and it suggested circumscription theory. there was already the natural boundary of my computer hemming the towns in, and town mayors played the role of big men to drive conflict. so i just needed a way for them to fight. i slightly tweaked the allocation of claude max accounts to the towns from a demand-based to a fixed allocation system. towns would each get a fixed amount of tokens to start, but i added a soldier role that could attack and defend in raids to steal tokens from other towns. [...]

They danced down the streets like dingledodies, & I shambled after as I've been doing all my life after people who interest me, because the only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones that never yawn or say a commonplace thing, but burn, burn, burn...

But it is sad to lose touch with whole branches of physics, to see scientists cut off from each other. Dispersion theorists do not know axiomatic field theory; cosmologists do not know nuclear physics. Quantum mechanics is hard to explain to a chemist...and yet the best theoretical chemists really ought to know quantum mechanics. Specialization of science also robbed us of much of our passion. We wanted to grasp science whole, but by then the whole was something far too vast and complex to master. Only rarely could we ask the deep questions that had first drawn us to science.

Whether you’re an AI-programming skeptic or an enthusiast, the reality is that many programming tasks are beyond the reach of today’s models. But many decent dev tools are actually quite easy for AI to build, and can help the rest of the programming go smoother. In general, these days any time I’m spending more than a minute staring at a JSON blob, I consider whether it’s worth building a custom UI for it.

Every day someone becomes a programmer because they figured out how to make ChatGPT build something. Lucky for us: in many of those cases the AI picks Python. We should treat this as an opportunity and anticipate an expansion in the kinds of people who might want to attend a Python conference. Yet many of these new programmers are not even aware that programming communities and conferences exist. It’s in the Python community’s interest to find ways to pull them in.

Every day more than 1 trillion events are written into a streaming ingestion pipeline, which is processed and written to a 100PB cloud-native data warehouse. And every day, our users run more than 150,000 jobs against this data, spanning everything from reporting and analysis to machine learning and recommendation algorithms.

We experimented with different async DB approaches, but settled on synchronous at FriendFeed because generally if our DB queries were backlogging our requests, our backends couldn't scale to the load anyway. Things that were slow enough were abstracted to separate backend services which we fetched asynchronously via the async HTTP module.

Since Jevons' original observation about coal-fired steam engines is a bit hard to relate to, my favourite modernized example for people who aren't software nerds is display technology. Old CRT screens were horribly inefficient - they were large, clunky and absolutely guzzled power. Modern LCDs and OLEDs are slim, flat and use much less power, so that seems great ... except we're now using powered screens in a lot of contexts that would be unthinkable in the CRT era. If I visit the local fast food joint, there's a row of large LCD monitors, most of which simply display static price lists and pictures of food. 20 years ago, those would have been paper posters or cardboard signage. The large ads in the urban scenery now are huge RGB LED displays (with whirring cooling fans); just 5 years ago they were large posters behind plexiglass. Bus stops have very large LCDs that display a route map and timetable which only changes twice a year - just two years ago, they were paper. Our displays are much more power-efficient than they've ever been, but at the same time we're using much more power on displays than ever.

Responders will tell you that broadcasters are condescending talking heads who think they're too good for the community. Broadcasters wish responders would take their nonsensical patter to a chat room, where they could natter on in privacy. Everyone agrees that members of the other group are total jackasses who don't know how to use Twitter.

Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time; premature optimization is the root of all evil.

History tells us how in that past time When all things happened, real, Imaginary, and dubious, a man Conceived the unconscionable plan Of making an abridgement of the universe In a single book; and with infinite zest He towered his screed up, lofty and Strenuous, polished it, and spoke the final verse. About to offer his thanks to Fortune, He lifted up his eyes and saw a burnished Disc in the air and realized, stunned, That somehow he had forgotten the moon.

The fourth and last voyage [of Swift's Gulliver's Travels] shows clearly that beasts are more worthy than men...In conclusion, it says: 'I am not in the least provoked at the sight of a lawyer, a pickpocket, a colonel, a fool, a gamester, a politician, a whore-master. . .' Certain words, in that good enumeration, are contaminated by their neighbors. ...The other is the most splendid verbal abuse I know, an insult so much extraordinary if we consider that it represents its author's only brush with literature: 'The gods did not allow Santos Chocano to dishonor the gallows by dying there. He is still alive, having exhausted infamy.'...The most fleeting mention of Chocano is enough to remind anyone of the famous insult, obscuring with malign splendor all reference to him.

...There I begin to shape the old handle With the hatchet, and the phrase First learned from Ezra Pound Rings in my ears! "When making an axe handle the pattern is not far off." And I say this to Kai "Look: We’ll shape the handle By checking the handle Of the axe we cut with—" And he sees. And I hear it again: It’s in Lu Ji’s Wên Fu, 4th century A. D. "Essay on Literature"—in the Preface: "In making the handle Of an axe By cutting wood with an axe The model is indeed near at hand." My teacher Shih-hsiang Chen Translated that and taught it years ago And I see Pound was an axe Chen was an axe, I am an axe And my son a handle, soon To be shaping again, model And tool, craft of culture, How we go on.

But in terms of the responsibility of journalism, we do have intense fact-checking because we want it to be right. Those big stories are aggregations of incredible journalism. So it cannot function without journalism. Now, we recheck it to make sure it's accurate or that it hasn't changed, but we're building this to make jokes. It's just we want the foundations to be solid or those jokes fall apart. Those jokes have no structural integrity if the facts underneath them are bullshit.

In 1836 he married his cousin Virginia Clemm, who was thirteen years of age; she died of tuberculosis in 1847. [Edgar Allen] Poe died in a hospital in Baltimore; during the fever of his death agony he relived an atrocious episode from his book The Narrative of Arthur Gordon Pym of Nantucket. His life was short and unhappy, if unhappiness can be short.

Performance analysis indicates that SQLite spends very little time doing bytecode decoding and dispatch. Most CPU cycles are consumed in walking B-Trees, doing value comparisons, and decoding records - all of which happens in compiled C code. Bytecode dispatch is using less than 3% of the total CPU time, according to my measurements. So at least in the case of SQLite, compiling all the way down to machine code might provide a performance boost 3% or less. That's not very much, considering the size, complexity, and portability costs involved.

Many people, and even a few companies, have contributed code to SQLite over the years. I have legal documentation for all such contributions in the firesafe in my office. We are able to track every byte of the SQLite source code back to its original creator. The project has been and continues to be open to outside contributions, as long as those contributions meet high standards of provenance and maintainability.

But there is one reason to suspect that an appropriate increase in size, together with other comparatively minor changes in structure, might lead to a large increase in intelligence. The evolution of modern man from non-tool-making ancestors has presumably been associated with and dependent on a large increase in intelligence, but has been completed in what is on an evolutionary scale a rather short time—at most a few million years. This suggests that the transformation which provided the required increase in intelligence may have been growth in size with relatively little increase in structural complexity—there was insufficient time for natural selection to do more...To ask oneself the consequence of building such an intelligence is a little like asking an Australopithecine what kind of questions Newton would ask himself and what answers he would give...I suspect that if our species survives, someone will try it and see.

The living come with grassy tread To read the gravestones on the hill; The graveyard draws the living still, ...So sure of death the marbles rhyme, Yet can't help marking all the time How no one dead will seem to come. What is it men are shrinking from? It would be easy to be clever And tell the stones: 'Men hate to die And have stopped dying now forever.' I think they would believe the lie.

Calmly we walk through this April’s day, Metropolitan poetry here and there, In the park sit pauper and rentier, The screaming children, the motor-car Fugitive about us, running away, Between the worker and the millionaire Number provides all distances, It is Nineteen Thirty-Seven now, Many great dears are taken away, What will become of you and me (This is the school in which we learn ...) Besides the photo and the memory? (... that time is the fire in which we burn.) The great globe reels in the solar fire, Spinning the trivial and unique away. (How all things flash! How all things flare!) ...Time is the school in which we learn Time is the fire in which we burn... Avid its rush, that reeling blaze! Where is my father and Eleanor? Not where are they now, dead seven years, But what they were then? No more? No more? From Nineteen-Fourteen to the present day, Bert Spira and Rhoda consume, consume Not where they are now (where are they now?) But what they were then, both beautiful; Each minute bursts in the burning room, The great globe reels in the solar fire, Spinning the trivial and unique away. (How all things flash! How all things flare!) What am I now that I was then? May memory restore again and again The smallest color of the smallest day: Time is the school in which we learn, Time is the fire in which we burn.

To make the analogy explicit, in Software 1.0, human-engineered source code (e.g. some .cpp files) is compiled into a binary that does useful work. In Software 2.0 most often the source code comprises 1) the dataset that defines the desirable behavior and 2) the neural net architecture that gives the rough skeleton of the code, but with many details (the weights) to be filled in. The process of training the neural network compiles the dataset into the binary — the final neural network. In most practical applications today, the neural net architectures and the training systems are increasingly standardized into a commodity, so most of the active “software development” takes the form of curating, growing, massaging and cleaning labeled datasets.

Often a person uses some folk proverb to explain a behavioral event even though, on an earlier occasion, this same person used a directly contradictory folk proverb to explain the same type of event. For example, most of us have heard or said, “look before you leap.” Now there’s a useful, straightforward bit of behavioral advice—except that I vaguely remember admonishing on occasion, “he who hesitates is lost.” And “absence makes the heart grow fonder” is a pretty clear prediction of an emotional reaction to environmental events. But then what about “out of sight, out of mind”? And if “haste makes waste”, why do we sometimes hear that “time waits for no man”? How could the saying “two heads are better than one” not be true? Except that “too many cooks spoil the broth.” If I think “it’s better to be safe than sorry”, why do I also believe “nothing ventured, nothing gained”? And if “opposites attract”, why do “birds of a feather flock together”? I have counseled many students to “never to put off until tomorrow what you can do today.” But I hope my last advisee has never heard me say this, because I just told him, “cross that bridge when you come to it.” The enormous appeal of clichés like these is that, taken together as implicit “explanations” of behavior, they cannot be refuted. No matter what happens, one of these explanations will be cited to cover it. No wonder we all think we are such excellent judges of human behavior and personality. We have an explanation for anything and everything that happens. Folk wisdom is cowardly in the sense that it takes no risk that it might be refuted.

Here I like to quote Valéry, who said a person is a poet if his imagination is stimulated by the difficulties inherent in his art and not if his imagination is dulled by them. I think very few people can manage free verse—you need an infallible ear, like D. H. Lawrence, to determine where the lines should end.