Quotessence
Home / Topics / Code Quotes

Code Quotes

Browse 1342 quotes about Code.

Related topics

Code Quotes

“Present in body and absent in spirit, he lies back on the couch, shamed by his own… potentials in his soul that will not be subdued. He feels himself inwardly subversive, imagining in his passivity extremes of aggression and desire that must be suppressed. Solution: more work, more money, more drink, more weight, more things, more infotainment.”

“Let’s establish a code for when you want to go all creeper on me. One knock means you’d like to come in. Two means you’re just stopping by to spy on me while I sleep.” His eyes travel from my face to my shirt (which happens to be his shirt) to my bare legs, lingering a breath too long before returning to my face. His gaze is warm. My legs are cold. Then he knocks once on the jamb. But it’s the smile that gets him in.”

“Their message will never be decoded, not only because there is no key to it, but also because people have no patience to listen to it in an age when the accumulation of messages old and new is such that their voices cancel one another out. Today history is no more than a thin thread of the remembered stretching over an ocean of the forgotten, but time moves on, and an epoch of millennia will come which the inextensible memory of the individual will be unable to encompass; whole centuries and millennia will therefore fall away, centuries of painting and music, centuries of discoveries, of battles, of books, and this will be dire, because man will lose the notion of his self, and his history, unfathomable, unencompassable, will shrivel into a few schematic signs destitute of all sense.”

“Their message will never be decoded… because people have no patience to listen to it in an age when the accumulation of messages old and new is such that their voices cancel one another out. Today history is no more than a thin thread of the remembered stretching over an ocean of the forgotten, but time moves on, and an epoch of millennia will come which the inextensible memory of the individual will be unable to encompass; whole centuries and millennia will therefore fall away, centuries of painting and music, centuries of discoveries, of battles, of books, and this will be dire, because man will lose the notion of his self, and his history, unfathomable, unencompassable, will shrivel into a few schematic signs destitute of all sense.”

“To face a life in these extremes, these men must live to a code of machismo that would wither the men of many cultures. Is it somehow required that, to hold your head high as a man among men, you must treat your life with such casual abandon? Or, I wondered, is it more than that? Is it tied to their overall spiritual view of life? By walking the thin line cast by the shadow of death, do they come to know life with an intimacy that the timid cannot?”

“The code is a metaphor that works well for the genetic code or the rules of a cellular automaton. The code is bad metaphor for the continuously changing states of neurons as they run through their algorithmic programs. Imagine looking for a code in space and time for rule 110, iteration 1,234, position 820-870. To study the mechanism that led to that state, we look at the point before, the relation of how it happened, in all available detail. Is that useful? In the case of the rule 110 automaton, the same rule applies everywhere, so the instance reveals something general about the whole. This is the hope of the biological experiment as well. But what happens if the rule changes with every iteration, as discussed for transcription factor cascades? To describe changing rules of algorithmic growth for every instance in time and space and in different systems is not only a rather large endeavor, it also suffers from the same danger of undefined depth. It is a description of the system, a series of bits of endpoint information, not a description of a code sufficient to create the system. The code is the 'extremely small amount of information to be specified genetically,' as Willshaw and von der Malsburg put it, that is sufficient to encode the unfolding of information under the influence of time and energy. The self-assembling brain.”

“Inheritance has recently fallen out of favor as a programming design solution in many programming languages because it’s often at risk of sharing more code than necessary. Subclasses shouldn’t always share all characteristics of their parent class but will do so with inheritance. This can make a program’s design less flexible. It also introduces the possibility of calling methods on subclasses that don’t make sense or that cause errors because the methods don’t apply to the subclass. In addition, some languages will only allow a subclass to inherit from one class, further restricting the flexibility of a program’s design. For these reasons, Rust takes a different approach, using trait objects instead of inheritance.”

“Swallowing, he entered the second code. Then there was a sound like a marble dropping on the floor - bouncing slowly, gradually getting faster as it dropped lower and lower… The thing was toying with him! Where was it? He strained his hearing, but all was again silent. He wanted to shout and scream obscenities at it, but he fought the impulse. It might not really know his location after all - and that would've led it right to him. It must be coming for him! It must be by the door by now, looking for a way in. Time was running out. He hastily keyed in the third and last code. Death the destroyer never is late!”

“Even in the unending abyss that seals eternity at both ends, if your function could compile to run on stray vacuum energy and, given an input, it once returned some particular string, it should, given that input, return that string again. > [object Object]”

“The only thing worse than not knowing why some code breaks is not knowing why it worked in the first place! It's the classic "house of cards" mentality: "it works, but I'm not sure why, so nobody touch it!" You may have heard, "Hell is other people" (Sartre), and the programmer meme twist, "Hell is other people's code." I believe truly: "Hell is not understanding my own code.”

“The thing about Web companies is there's always something severely fucked-up. There is always an outage, always lost data, always compromised customer information, always a server going offline. You work with these clugey internal tools and patch together work-arounds to compensate for the half-assed, rushed development, and after a while the fucked-upness of the whole enterprise becomes the status quo. VPs insecure that they're not as in touch as they need to be with conditions on the ground insert themselves into projects midstream and you get serious scope creep. You present to the world this image that you're a buttoned-down tech company with everything in its right place but once you're on the other side of the firewall it looks like triage time in an emergency room, 24/7. Systems break down, laptops go into the blue screen of death, developers miskey a line of code, error messages appear that mean absolutely nothing. The instantaneousness with which you can fix stuff creates a culture that works by the seat of its pants. I swear the whole Web was built by virtue of developers fixing one mistake after another, constantly forced to compensate for the bugginess of their code.”

“A Martial Artist may become A professional fighter but not every Fighter is capable of becoming A martial artist. Martial Arts are about restoration of physical and spiritual balance and fluidity; they are about observing restraints and 'setting example'. Every practice session is A reminder of the play of opposites (yin and yang), . . . .”