Code Documentation Quotes

I will love you if I never see you again, and I will love you if I see you every Tuesday. I will love you as the starfish loves a coral reef and as kudzu loves trees, even if the oceans turn to sawdust and the trees fall in the forest without anyone around to hear them. I will love you as the pesto loves the fettuccini and ats the horseradish loves the miyagi, and the pepperoni loves the pizza. I will love you as the manatee loves the head of lettuce and as the dark spot loves the leopard, as the leech loves the ankle of a wader and as a corpse loves the beak of the vulture. I will love you as the doctor loves his sickest patient and a lake loves its thirstiest swimmer. I will love you as the beard loves the chin, and the crumbs love the beard, and the damp napkin loves the crumbs, and the precious document loves the dampness of the napkin, and the squinting eye of the reader loves the smudged document, and the tears of sadness love the squinting eye as it misreads what is written. I will love you as the iceberg loves the ship, and the passengers love the lifeboat, and the lifeboat loves the teeth of the sperm whale, and the sperm whale loves the flavor of naval uniforms. I will love you as a drawer loves a secret compartment, and as a secret compartment loves a secret, and as a secret loves to make a person gasp... I will love you until all such compartments are discovered and opened, and all the secrets have gone gasping into the world. I will love you until all the codes and hearts have been broken and until every anagram and egg has been unscrambled. I will love you until every fire is extinguished and rebuilt from the handsomest and most susceptible of woods. I will love you until the bird hates a nest and the worm hates an apple. I will love you as we find ourselves farther and farther from one another, where once we were so close... I will love you until your face is fogged by distant memory. I will love you no matter where you go and who you see, I will love you if you don't marry me. I will love you if you marry someone else--and i will love you if you never marry at all, and spend your years wishing you had married me after all. That is how I will love you even as the world goes on its wicked way.

Good code is its own best documentation. As you're about to add a comment, ask yourself, 'How can I improve the code so that this comment isn't needed?' Improve the code and then document it to make it even clearer.

I have never been one of those people—I know you aren’t, either—who feels that the love one has for a child is somehow a superior love, one more meaningful, more significant, and grander than any other. I didn’t feel that before Jacob, and I didn’t feel that after. But it is a singular love, because it is a love whose foundation is not physical attraction, or pleasure, or intellect, but fear. You have never known fear until you have a child, and maybe that is what tricks us into thinking that it is more magnificent, because the fear itself is more magnificent. Every day, your first thought is not “I love him” but “How is he?” The world, overnight, rearranges itself into an obstacle course of terrors. I would hold him in my arms and wait to cross the street and would think how absurd it was that my child, that any child, could expect to survive this life. It seemed as improbable as the survival of one of those late-spring butterflies—you know, those little white ones—I sometimes saw wobbling through the air, always just millimeters away from smacking itself against a windshield. And let me tell you two other things I learned. The first is that it doesn’t matter how old that child is, or when or how he became yours. Once you decide to think of someone as your child, something changes, and everything you have previously enjoyed about them, everything you have previously felt for them, is preceded first by that fear. It’s not biological; it’s something extra-biological, less a determination to ensure the survival of one’s genetic code, and more a desire to prove oneself inviolable to the universe’s feints and challenges, to triumph over the things that want to destroy what’s yours. The second thing is this: when your child dies, you feel everything you’d expect to feel, feelings so well-documented by so many others that I won’t even bother to list them here, except to say that everything that’s written about mourning is all the same, and it’s all the same for a reason—because there is no real deviation from the text. Sometimes you feel more of one thing and less of another, and sometimes you feel them out of order, and sometimes you feel them for a longer time or a shorter time. But the sensations are always the same. But here’s what no one says—when it’s your child, a part of you, a very tiny but nonetheless unignorable part of you, also feels relief. Because finally, the moment you have been expecting, been dreading, been preparing yourself for since the day you became a parent, has come. Ah, you tell yourself, it’s arrived. Here it is. And after that, you have nothing to fear again.

The unit tests are documents. They describe the lowest-level design of the system.

In a modern twist to the classic overeating experiments, Feltham decided that he would eat 5794 calories per day and document his weight gain. But the diet he chose was not a random 5794 calories. He followed a low-carbohydrate, high-fat diet of natural foods for twenty-one days. Feltham believed, based on clinical experience, that refined carbohydrates, not total calories, caused weight gain. The macronutrient breakdown of his diet was 10 percent carbohydrate, 53 percent fat and 37 percent protein. Standard calorie calculations predicted a weight gain of about 16 pounds (7.3 kilograms). Actual weight gain, however, was only about 2.8 pounds (1.3 kilograms). Even more interesting, he dropped more than 1 inch (2.5 centimeters) from his waist measurement. He gained weight, but it was lean mass.

Overlooked, too, is that the Visigothic Code of Law was, for its time, an impressive document that combined Visigoth practices with Roman law and Christian principles, and that evidences a guiding desire to limit the power of government many centuries before Magna Carta.

The Bible became the book of books, but it is not one document. It is a mystical library of interwoven texts by unknown authors who wrote and edited at different times with widely divergent aims. This sacred work of so many epochs and so many hands contains some facts of provable history, some stories of unprovable myth, some poetry of soaring beauty, and many passages of unintelligible, perhaps coded, perhaps simply mistranslated, mystery. Most of it is written not to recount events but to promote a higher truth—the relationship of one people and their God.

In 1953, Allen Dulles, then director of the USA Central Intelligence Agency (CIA), named Dr Sidney Gottlieb to direct the CIA's MKULTRA programme, which included experiments conducted by psychiatrists to create amnesia, new dissociated identities, new memories, and responses to hypnotic access codes. In 1972, then-CIA director Richard Helms and Gottlieb ordered the destruction of all MKULTRA records. A clerical error spared seven boxes, containing 1738 documents, over 17,000 pages. This archive was declassified through a Freedom of Information Act Request in 1977, though the names of most people, universities, and hospitals are redacted. The CIA assigned each document a number preceded by "MORI", for "Managament of Officially Released Information", the CIA's automated electronic system at the time of document release. These documents, to be referenced throughout this chapter, are accessible on the Internet (see: abuse-of-power (dot) org/modules/content/index.php?id=31). The United States Senate held a hearing exposing the abuses of MKULTRA, entitled "Project MKULTRA, the CIA's program of research into behavioral modification" (1977).

Even the National Cholesterol Education Program admits, “The percentage of total fat in the diet, independent of caloric intake, has not been documented to be related to body weight.

For a thousand years,” Langdon continued, “legends of this secret have been passed on. The entire collection of documents, its power, and the secret it reveals have become known by a single name—Sangreal.

But it is a singular love, because it is a love whose foundation is not physical attraction, or pleasure, or intellect, but fear. You have never known fear until you have a child, and maybe that is what tricks us into thinking that it is more magnificent, because the fear itself is more magnificent. Every day, your first thought is not “I love him” but “How is he?” The world, overnight, rearranges itself into an obstacle course of terrors. I would hold him in my arms and wait to cross the street and would think how absurd it was that my child, that any child, could expect to survive this life. It seemed as improbable as the survival of one of those late-spring butterflies—you know, those little white ones—I sometimes saw wobbling through the air, always just millimeters away from smacking itself against a windshield. And let me tell you two other things I learned. The first is that it doesn’t matter how old that child is, or when or how he became yours. Once you decide to think of someone as your child, something changes, and everything you have previously enjoyed about them, everything you have previously felt for them, is preceded first by that fear. It’s not biological; it’s something extra-biological, less a determination to ensure the survival of one’s genetic code, and more a desire to prove oneself inviolable to the universe’s feints and challenges, to triumph over the things that want to destroy what’s yours. The second thing is this: when your child dies, you feel everything you’d expect to feel, feelings so well-documented by so many others that I won’t even bother to list them here, except to say that everything that’s written about mourning is all the same, and it’s all the same for a reason—because there is no real deviation from the text. Sometimes you feel more of one thing and less of another, and sometimes you feel them out of order, and sometimes you feel them for a longer time or a shorter time. But the sensations are always the same. But here’s what no one says—when it’s your child, a part of you, a very tiny but nonetheless unignorable part of you, also feels relief. Because finally, the moment you have been expecting, been dreading, been preparing yourself for since the day you became a parent, has come. Ah, you tell yourself, it’s arrived. Here it is. And after that, you have nothing to fear again.

The tail is the time period from “code slush” (true code freezes are rare) or “feature freeze” to actual deployment. This is the time period when companies do some or all of the following: beta testing, regression testing, product integration, integration testing, documentation, defect fixing. The worst “tail” I’ve encountered was 18 months—18 months from feature freeze to product release, and most of that time was spent in QA. I’ve

Irena Sendler (code name "Jolanta") described it. A Christian doctor's daughter with many Jewish friends, she reconfigured her job at the Social Welfare Department, recruited ten like-minded others, and began issuing false documents with forged signatures.

And let me tell you two other things I learned. The first is that it doesn’t matter how old that child is, or when or how he became yours. Once you decide to think of someone as your child, something changes, and everything you have previously enjoyed about them, everything you have previously felt for them, is preceded first by that fear. It’s not biological; it’s something extra-biological, less a determination to ensure the survival of one’s genetic code, and more a desire to prove oneself inviolable to the universe’s feints and challenges, to triumph over the things that want to destroy what’s yours. The second thing is this: when your child dies, you feel everything you’d expect to feel, feelings so well-documented by so many others that I won’t even bother to list them here, except to say that everything that’s written about mourning is all the same, and it’s all the same for a reason—because there is no real deviation from the text. Sometimes you feel more of one thing and less of another, and sometimes you feel them out of order, and sometimes you feel them for a longer time or a shorter time. But the sensations are always the same. But here’s what no one says—when it’s your child, a part of you, a very tiny but nonetheless unignorable part of you, also feels relief. Because finally, the moment you have been expecting, been dreading, been preparing yourself for since the day you became a parent, has come. Ah, you tell yourself, it’s arrived. Here it is. And after that, you have nothing to fear again.

Any attempt to fix it with minimum effort will repair the local and obvious, but unless the structure is pure or the documentation very fine, the far-reaching effects of the repair will be overlooked. Second, the repairer is usually not the man who wrote the code, and often he is a junior programmer or trainee.

If Urton is right, khipu were unique. They were the world’s sole intrinsically three-dimensional written documents (Braille is a translation of writing on paper) and the only ones to use a “system of coding information” that “like the coding systems used in present-day computer language, was structured primarily as a binary code.

Inheritance adds complexity to a program, and, as such, it's a dangerous technique. As Java guru Joshua Bloch says, "Design and document for inheritance, or prohibit it." If a class isn't designed to be inherited from, make its members non-virtual in C++, final in Java, or non-overridable in Microsoft Visual Basic so that you can't inherit from it.

Armstrong: I like documentation. I don't think a program is finished until you've written some reasonable documentation. And I quite like a specification. I think it's unprofessional these people who say, "What does it do? Read the code." The code shows me what it does. It doesn't show me what it's supposed to do. I think the code is the answer to a problem.

In the case of Peugeot SA the crucial story was the French legal code, as written by the French parliament. According to the French legislators, if a certified lawyer followed all the proper liturgy and rituals, wrote all the required spells and oaths on a wonderfully decorated piece of paper, and affixed his ornate signature to the bottom of the document, then hocus pocus – a new company was incorporated.

Before getting into CRISPR, Zayner tried a variety of synthetic biology experiments, including on himself. To treat his gastrointestinal problems, he performed a fecal transplant (don’t ask) to transform his gut’s microbiome. He did the procedure in a hotel room with two filmmakers documenting the scene, and (in case you really do want to know how it works) it became a short documentary called Gut Hack that can be found online.2

In the morning I walked to the bank. I went to the automated teller machine to check my balance. I inserted my card, entered my secret code, tapped out my request. The figure on the screen roughly corresponded to my independent estimate, feebly arrived at after long searches through documents, tormented arithmetic. Waves of relief and gratitude flowed over me. The system had blessed my life. I felt its support and approval. The system hardware, the mainframe sitting in a locked room in some distant city. What a pleasing interaction. I sensed that something of deep personal value, but not money, not that at all, had been authenticated and confirmed. A deranged person was escorted from the bank by two armed guards. The system was invisible, which made it all the more impressive, all the more disquieting to deal with. But we were in accord, at least for now.

Irrelevant’ Chris Fogle turns a page. Howard Cardwell turns a page. Ken Wax turns a page. Matt Redgate turns a page. ‘Groovy’ Bruce Channing attaches a form to a file. Ann Williams turns a page. Anand Singh turns two pages at once by mistake and turns one back which makes a slightly different sound. David Cusk turns a page. Sandra Pounder turns a page. Robert Atkins turns two separate pages of two separate files at the same time. Ken Wax turns a page. Lane Dean Jr. turns a page. Olive Borden turns a page. Chris Acquistipace turns a page. David Cusk turns a page. Rosellen Brown turns a page. Matt Redgate turns a page. R. Jarvis Brown turns a page. Ann Williams sniffs slightly and turns a page. Meredith Rand does something to a cuticle. ‘Irrelevant’ Chris Fogle turns a page. Ken Wax turns a page. Howard Cardwell turns a page. Kenneth ‘Type of Thing’ Hindle detaches a Memo 402-C(1) from a file. ‘Second-Knuckle’ Bob McKenzie looks up briefly while turning a page. David Cusk turns a page. A yawn proceeds across one Chalk’s row by unconscious influence. Ryne Hobratschk turns a page. Latrice Theakston turns a page. Rotes Group Room 2 hushed and brightly lit, half a football field in length. Howard Cardwell shifts slightly in his chair and turns a page. Lane Dean Jr. traces his jaw’s outline with his ring finger. Ed Shackleford turns a page. Elpidia Carter turns a page. Ken Wax attaches a Memo 20 to a file. Anand Singh turns a page. Jay Landauer and Ann Williams turn a page almost precisely in sync although they are in different rows and cannot see each other. Boris Kratz bobs with a slight Hassidic motion as he crosschecks a page with a column of figures. Ken Wax turns a page. Harriet Candelaria turns a page. Matt Redgate turns a page. Ambient room temperature 80° F. Sandra Pounder makes a minute adjustment to a file so that the page she is looking at is at a slightly different angle to her. ‘Irrelevant’ Chris Fogle turns a page. David Cusk turns a page. Each Tingle’s two-tiered hemisphere of boxes. ‘Groovy’ Bruce Channing turns a page. Ken Wax turns a page. Six wigglers per Chalk, four Chalks per Team, six Teams per group. Latrice Theakston turns a page. Olive Borden turns a page. Plus administration and support. Bob McKenzie turns a page. Anand Singh turns a page and then almost instantly turns another page. Ken Wax turns a page. Chris ‘The Maestro’ Acquistipace turns a page. David Cusk turns a page. Harriet Candelaria turns a page. Boris Kratz turns a page. Robert Atkins turns two separate pages. Anand Singh turns a page. R. Jarvis Brown uncrosses his legs and turns a page. Latrice Theakston turns a page. The slow squeak of the cart boy’s cart at the back of the room. Ken Wax places a file on top of the stack in the Cart-Out box to his upper right. Jay Landauer turns a page. Ryne Hobratschk turns a page and then folds over the page of a computer printout that’s lined up next to the original file he just turned a page of. Ken Wax turns a page. Bob Mc-Kenzie turns a page. Ellis Ross turns a page. Joe ‘The Bastard’ Biron-Maint turns a page. Ed Shackleford opens a drawer and takes a moment to select just the right paperclip. Olive Borden turns a page. Sandra Pounder turns a page. Matt Redgate turns a page and then almost instantly turns another page. Latrice Theakston turns a page. Paul Howe turns a page and then sniffs circumspectly at the green rubber sock on his pinkie’s tip. Olive Borden turns a page. Rosellen Brown turns a page. Ken Wax turns a page. Devils are actually angels. Elpidia Carter and Harriet Candelaria reach up to their Cart-In boxes at exactly the same time. R. Jarvis Brown turns a page. Ryne Hobratschk turns a page. ‘Type of Thing’ Ken Hindle looks up a routing code. Some with their chin in their hand. Robert Atkins turns a page even as he’s crosschecking something on that page. Ann Williams turns a page. Ed Shackleford searches a file for a supporting document. Joe Biron-Maint turns a page. Ken Wax turns a page.

[ Dr. Lois Jolyon West was cleared at Top Secret for his work on MKULTRA. ] Dr. Michael Persinger [235], another FSMF Board Member, is the author of a paper entitled “Elicitation of 'Childhood Memories' in Hypnosis-Like Settings Is Associated With Complex Partial Epileptic-Like Signs For Women But Not for Men: the False Memory Syndrome.” In the paper Perceptual and Motor Skills,In the paper, Dr. Persinger writes: On the day of the experiment each subject (not more than two were tested per day) was asked to sit quietly in an acoustic chamber and was told that the procedure was an experiment in relaxation. The subject wore goggles and a modified motorcycle helmet through which 10-milligauss (1 microTesla) magnetic fields were applied through the temporal plane. Except for a weak red (photographic developing) light, the room was dark. Dr. Persinger's research on the ability of magnetic fields to facilitate the creation of false memories and altered states of consciousness is apparently funded by the Defense Intelligence Agency through the project cryptonym SLEEPING BEAUTY. Freedom of Information Act requests concerning SLEEPING BEAUTY with a number of different intelligence agencies including the CIA and DEA has yielded denial that such a program exists. Certainly, such work would be of direct interest to BLUEBIRD, ARTICHOKE, MKULTRA and other non-lethal weapons programs. Schnabel [280] lists Dr. Persinger as an Interview Source in his book on remote viewing operations conducted under Stargate, Grill Flame and other cryptonyms at Fort Meade and on contract to the Stanford Research Institute. Schnabel states (p. 220) that, “As one of the Pentagon's top scientists, Vorona was privy to some of the strangest, most secret research projects ever conceived. Grill Flame was just one. Another was code-named Sleeping Beauty; it was a Defense Department study of remote microwave mind-influencing techniques ... [...] It appears from Schnabel's well-documented investigations that Sleeping Beauty is a real, but still classified mind control program. Schnabel [280] lists Dr. West as an Interview Source and says that West was a, “Member of medical oversight board for Science Applications International Corp. remote-viewing research in early 1990s.

As you grow in influence, you’ll find that more and more people want you to care about things. Someone’s putting together a best practices document for how your organization does code review, and they want your opinion. Your group is doing a hiring push and needs help deciding what to interview for. There’s a deprecation that would be making more progress if it had a staff engineer drumming up senior sponsorship. And that’s just Monday morning. What do you do?

understand that there are rules to follow if you are to win: 1. The model will provide consistent value to your customers, employees, suppliers, and lenders, beyond what they expect. 2. The model will be operated by people with the lowest possible level of skill. 3. The model will stand out as a place of impeccable order. 4. All work in the model will be documented in Operations Manuals. 5. The model will provide a uniformly predictable service to the customer. 6. The model will utilize a uniform color, dress, and facilities code.

Consider this oddly neglected fact: the West was acquired, conquested, and largely consolidated into the nation coincident with the greatest breakthrough in the history of human communication. The breakthrough was the telegraph. The great advances that followed it, the telephone, radio, television, and the Internet, were all elaborations on its essential contribution. The telegraph separated the person from the message. Before it, with a few exceptions such as a sephamore and carrier pigeons, information moved only as fast as people did. By the nineteenth century, people were certainly moving a lot faster, and indeed a second revolution, that of transportation, was equally critical in creating the West, but before the telegraph a message still had to move with a person, either as a document or in somebody’s head. The telegraph liberated information. Now it could travel virtually at the speed of light. The railroad carried people and things, including letters, ten to fifteen times faster than the next most rapid form of movement. The telegraph accelerated communication more than forty million times. A single dot of Morse code traveled from Kansas City to Denver faster than the click it produced moved from the receiver to the telegrapher’s eardrum.

Security is a big and serious deal, but it’s also largely a solved problem. That’s why the average person is quite willing to do their banking online and why nobody is afraid of entering their credit card number on Amazon. At 37signals, we’ve devised a simple security checklist all employees must follow: 1. All computers must use hard drive encryption, like the built-in FileVault feature in Apple’s OS X operating system. This ensures that a lost laptop is merely an inconvenience and an insurance claim, not a company-wide emergency and a scramble to change passwords and worry about what documents might be leaked. 2. Disable automatic login, require a password when waking from sleep, and set the computer to automatically lock after ten inactive minutes. 3. Turn on encryption for all sites you visit, especially critical services like Gmail. These days all sites use something called HTTPS or SSL. Look for the little lock icon in front of the Internet address. (We forced all 37signals products onto SSL a few years back to help with this.) 4. Make sure all smartphones and tablets use lock codes and can be wiped remotely. On the iPhone, you can do this through the “Find iPhone” application. This rule is easily forgotten as we tend to think of these tools as something for the home, but inevitably you’ll check your work email or log into Basecamp using your tablet. A smartphone or tablet needs to be treated with as much respect as your laptop. 5. Use a unique, generated, long-form password for each site you visit, kept by password-managing software, such as 1Password.§ We’re sorry to say, “secretmonkey” is not going to fool anyone. And even if you manage to remember UM6vDjwidQE9C28Z, it’s no good if it’s used on every site and one of them is hacked. (It happens all the time!) 6. Turn on two-factor authentication when using Gmail, so you can’t log in without having access to your cell phone for a login code (this means that someone who gets hold of your login and password also needs to get hold of your phone to login). And keep in mind: if your email security fails, all other online services will fail too, since an intruder can use the “password reset” from any other site to have a new password sent to the email account they now have access to. Creating security protocols and algorithms is the computer equivalent of rocket science, but taking advantage of them isn’t. Take the time to learn the basics and they’ll cease being scary voodoo that you can’t trust. These days, security for your devices is just simple good sense, like putting on your seat belt.

I’d never coded before, and I’d always thought games were huge undertakings by thousands of people in a big studio. Little did I know that a major part of coding involves Googling to find documentation, code snippets, and communities that help people fix common problems. Free information and guidance aren’t limited to programming, either. The Open Source movement makes tremendous amounts of knowledge and resources available online for free, and some major universities are making classes available for free on the internet. It’s a shame that a lot of us use the internet only to talk shit in comments sections and check our email when we have the sum of human knowledge at our fingertips.

In a classic study of how names impact people’s experience on the job market, researchers show that, all other things being equal, job seekers with White-sounding first names received 50 percent more callbacks from employers than job seekers with Black-sounding names.5 They calculated that the racial gap was equivalent to eight years of relevant work experience, which White applicants did not actually have; and the gap persisted across occupations, industry, employer size – even when employers included the “equal opportunity” clause in their ads.6 With emerging technologies we might assume that racial bias will be more scientifically rooted out. Yet, rather than challenging or overcoming the cycles of inequity, technical fixes too often reinforce and even deepen the status quo. For example, a study by a team of computer scientists at Princeton examined whether a popular algorithm, trained on human writing online, would exhibit the same biased tendencies that psychologists have documented among humans. They found that the algorithm associated White-sounding names with “pleasant” words and Black-sounding names with “unpleasant” ones.7 Such findings demonstrate what I call “the New Jim Code”: the employment of new technologies that reflect and reproduce existing inequities but that are promoted and perceived as more objective or progressive than the discriminatory systems of a previous era.

In the case of Peugeot SA the crucial story was the French legal code, as written by the French parliament. According to the French legislators, if a certified lawyer followed all the proper liturgy and rituals, wrote all the required spells and oaths on a wonderfully decorated piece of paper, and affixed his ornate signature to the bottom of the document, then hocus pocus – a new company was incorporated. When in 1896 Armand Peugeot wanted to create his company, he paid a lawyer to go through all these sacred procedures. Once the lawyer had performed all the right rituals and pronounced all the necessary spells and oaths, millions of upright French citizens behaved as if the Peugeot company really existed.

The American Declaration of Independence asserts that: We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable rights, that among these are life, liberty, and the pursuit of happiness. Like Hammurabi’s Code, the American founding document promises that if humans act according to its sacred principles, millions of them would be able to cooperate effectively, living safely and peacefully in a just and prosperous society. Like the Code of Hammurabi, the American Declaration of Independence was not just a document of its time and place – it was accepted by future generations as well. For more than 200 years, American schoolchildren have been copying and learning it by heart. The two texts present us with an obvious dilemma. Both the Code of Hammurabi and the American Declaration of Independence claim to outline universal and eternal principles of justice, but according to the Americans all people are equal, whereas according to the Babylonians people are decidedly unequal. The Americans would, of course, say that they are right, and that Hammurabi is wrong. Hammurabi, naturally, would retort that he is right, and that the Americans are wrong. In fact, they are both wrong. Hammurabi and the American Founding Fathers alike imagined a reality governed by universal and immutable principles of justice, such as equality or hierarchy. Yet the only place where such universal principles exist is in the fertile imagination of Sapiens, and in the myths they invent and tell one another. These principles have no objective validity. It

At one level, the whole notion seemed ludicrous, even suicidal. Yet in a way that he could not explain even to himself, his uncle’s intense sense of conviction about the matter struck a mystifying yet riveting chord deep in Jacob’s soul. Finally he shrugged and nodded, and as he did, Avi and Morry beamed with what appeared to be joy, a rather odd emotion to be feeling under the circumstances, Jacob thought. “Very good,” the Frenchman began. “I will personally oversee your training. You two must both get in much better shape. Physical conditioning is critical. Then we’ll cover setting up safe houses, forging documents, Morse code, building and fixing and operating all kinds of radios, surveillance, weapons training, hand-to-hand combat. But we don’t have much time. We’re expecting the Germans to invade by the end of the year. You sure you’re up for this?” Jacob looked at his uncle, then to Maurice Tulek, and nodded. “I’m ready.

The potential for manipulation here is enormous. Here’s one example. During the 2012 election, Facebook users had the opportunity to post an “I Voted” icon, much like the real stickers many of us get at polling places after voting. There is a documented bandwagon effect with respect to voting; you are more likely to vote if you believe your friends are voting, too. This manipulation had the effect of increasing voter turnout 0.4% nationwide. So far, so good. But now imagine if Facebook manipulated the visibility of the “I Voted” icon on the basis of either party affiliation or some decent proxy of it: ZIP code of residence, blogs linked to, URLs liked, and so on. It didn’t, but if it had, it would have had the effect of increasing voter turnout in one direction. It would be hard to detect, and it wouldn’t even be illegal. Facebook could easily tilt a close election by selectively manipulating what posts its users see. Google might do something similar with its search results.

Cash was running low, so I'd applied for a job as an administrative assistant for a nonprofit arts group. Without question, my organizational skills were as sharp as my vision, and I had no office experience to speak of. Luckily for me, none of this surfaced during the interview. 'Ryan, pretend it's a rough morning for a sec. Handle this situation for me. When you arrive at work to open the arts resource centre, several people are already at the door. Two clients want immediate help with grant applications - you know those artists, they just can't wait! - and a third wants to use our library, which isn't open till noon. Entering the office, you hear the phone is ringing and see the message light is blinking. The fax machine looks jammed again, and we're expecting an important document. Among the people waiting is a courier with a package you need to sign for. Think about it, though. The lights haven't been turned on yet, and the sign put out front. The alarm needs the code within a minute, too. So, wow, rough morning. I'd like to know what you'd do first.' 'First I'd tell everybody how weird this is. I'm in the same test situation from my job interview. What are the chances?' I started the next day.

When a domain reaches a point where the knowledge for skillful professional practice cannot be acquired in a decade, more or less, then several adaptive developments are likely to occur. Specialization will usually increase (as it has, for example, in medicine), and practitioners will make increasing use of books and other external reference aids in their work. Architecture is a good example of a domain where much of the information a professional requires is stored in reference works, such as catalogues of available building materials, equipment, and components, and official building codes. No architect expects to keep all of this in his head or to design without frequent resort to these information sources. In fact architecture can almost be taken as a prototype for the process of design in a semantically rich task domain. The emerging design is itself incorporated in a set of external memory structures: sketches, floor plans, drawings of utility systems, and so on. At each stage in the design process, partial design reflected in these documents serves as a major stimulus suggesting to the designer what he should attend to next. This direction to new sub-goals permits in turn new information to be extracted from memory and reference sources and another step to be taken toward the development of the design.

2006 interview by Jim Gray, Amazon CTO Werner Vogels recalled another watershed moment: We went through a period of serious introspection and concluded that a service-oriented architecture would give us the level of isolation that would allow us to build many software components rapidly and independently. By the way, this was way before service-oriented was a buzzword. For us service orientation means encapsulating the data with the business logic that operates on the data, with the only access through a published service interface. No direct database access is allowed from outside the service, and there’s no data sharing among the services.3 That’s a lot to unpack for non–software engineers, but the basic idea is this: If multiple teams have direct access to a shared block of software code or some part of a database, they slow each other down. Whether they’re allowed to change the way the code works, change how the data are organized, or merely build something that uses the shared code or data, everybody is at risk if anybody makes a change. Managing that risk requires a lot of time spent in coordination. The solution is to encapsulate, that is, assign ownership of a given block of code or part of a database to one team. Anyone else who wants something from that walled-off area must make a well-documented service request via an API.

How exactly did Armand Peugeot, the man, create Peugeot, the company? In much the same way that priests and sorcerers have created gods and demons throughout history, and in which thousands of French curés were still creating Christ’s body every Sunday in the parish churches. It all revolved around telling stories, and convincing people to believe them. In the case of the French curés, the crucial story was that of Christ’s life and death as told by the Catholic Church. According to this story, if a Catholic priest dressed in his sacred garments solemnly said the right words at the right moment, mundane bread and wine turned into God’s flesh and blood. The priest exclaimed, ‘Hoc est corpus meum! ’ (Latin for ‘This is my body!’) and hocus pocus – the bread turned into Christ’s flesh. Seeing that the priest had properly and assiduously observed all the procedures, millions of devout French Catholics behaved as if God really existed in the consecrated bread and wine. In the case of Peugeot SA the crucial story was the French legal code, as written by the French parliament. According to the French legislators, if a certified lawyer followed all the proper liturgy and rituals, wrote all the required spells and oaths on a wonderfully decorated piece of paper, and affixed his ornate signature to the bottom of the document, then hocus pocus – a new company was incorporated. When in 1896 Armand Peugeot wanted to create his company, he paid a lawyer to go through all these sacred procedures. Once the lawyer had performed all the right rituals and pronounced all the necessary spells and oaths, millions of upright French citizens behaved as if the Peugeot company really existed.

Sociologist Barry Glassner (1999) has documented many of the biases introduced by “If it bleeds, it leads” news reporting, and by the strategic efforts of special interest groups to control the agenda of public fear of crime, disease, and other hazards. Is an increase of approximately 700 incidents in 50 states over 7 years an “epidemic” of road rage? Is it conceivable that there is (or ever was) a crisis in children’s day care stemming from predatory satanic cults? In 1994, a research team funded by the U.S. government spent 4 years and $750,000 to reach the conclusion that the myth of satanic conspiracies in day care centers was totally unfounded; not a single verified instance was found (Goodman, Qin, Bottoms, & Shaver, 1994; Nathan & Snedeker, 1995). Are automatic-weapon-toting high school students really the first priority in youth safety? (In 1999, approximately 2,000 school-aged children were identified as murder victims; only 26 of those died in school settings, 14 of them in one tragic incident at Columbine High School in Littleton, Colorado.) The anthropologist Mary Douglas (Douglas & Wildavsky, 1982) pointed out that every culture has a store of exaggerated horrors, many of them promoted by special interest factions or to defend cultural ideologies. For example, impure water had been a hazard in 14th-century Europe, but only after Jews were accused of poisoning wells did the citizenry become preoccupied with it as a major problem. But the original news reports are not always ill-motivated. We all tend to code and mention characteristics that are unusual (that occur infrequently). [...] The result is that the frequencies of these distinctive characteristics, among the class of people considered, tend to be overestimated.

Sometimes what-if fantasies are useful. Imagine that the entirety of Western civilisation’s coding for computer systems or prints of all films ever made or all copies of Shakespeare and the Bible and the Qur’an were encrypted and held on one tablet device. And if that tablet was lost, stolen, burnt or corrupted, then our knowledge, use and understanding of that content, those words and ideas, would be gone for ever – only, perhaps, lingering in the minds of a very few men of memory whose job it had been to keep ideas alive. This little thought-experiment can help us to comprehend the totemic power of manuscripts. This is the great weight of responsibility for the past, the present and the future that the manuscripts of Constantinople carried. Much of our global cultural heritage – philosophies, dramas, epic poems – survive only because they were preserved in the city’s libraries and scriptoria. Just as Alexandria and Pergamon too had amassed vast libraries, Constantinople understood that a physical accumulation of knowledge worked as a lode-stone – drawing in respect, talent and sheer awe. These texts contained both the possibilities and the fact of empire and had a quasi-magical status. This was a time when the written word was considered so potent – and so precious – that documents were thought to be objects with spiritual significance. (...) It was in Constantinople that the book review was invented. Scholars seem to have had access to books within a proto-lending-library system, and there were substantial libraries within the city walls. Thanks to Constantinople, we have the oldest complete manuscript of the Iliad, Aeschylus’ dramas Agamemnon and Eumenides, and the works of Sophocles and Pindar. Fascinating scholia in the margins correct and improve: plucking work from the page ‘useful for the reader . . . not just the learned’, as one Byzantine scholar put it. These were texts that were turned into manuals for contemporary living.

Make interfaces programmatic rather than semantic when possible. Each interface consists of a programmatic part and a semantic part. The programmatic part consists of the data types and other attributes of the interface that can be enforced by the compiler. The semantic part of the interface consists of the assumptions about how the interface will be used, which cannot be enforced by the compiler. The semantic interface includes considerations such as "RoutineA must be called before RoutineB" or "RoutineA will crash if dataMember1 isn't initialized before it's passed to RoutineA." The semantic interface should be documented in comments, but try to keep interfaces minimally dependent on documentation. Any aspect of an interface that can't be enforced by the compiler is an aspect that's likely to be misused. Look for ways to convert semantic interface elements to programmatic interface elements by using Asserts or other techniques.

If you can't figure out how to use a class based solely on its interface documentation, the right response is not to pull up the source code and look at the implementation. That's good initiative but bad judgment. The right response is to contact the author of the class and say "I can't figure out how to use this class.

The right response for the class author is to check out the class-interface file, modify the class-interface documentation, check the file back in, and then say "See if you can understand how it works now.

The Pseudocode Programming Process Have you checked that the prerequisites have been satisfied? Have you defined the problem that the class will solve? Is the high-level design clear enough to give the class and each of its routines a good name? Have you thought about how to test the class and each of its routines? Have you thought about efficiency mainly in terms of stable interfaces and readable implementations or mainly in terms of meeting resource and speed budgets? Have you checked the standard libraries and other code libraries for applicable routines or components? Have you checked reference books for helpful algorithms? Have you designed each routine by using detailed pseudocode? Have you mentally checked the pseudocode? Is it easy to understand? Have you paid attention to warnings that would send you back to design (use of global data, operations that seem better suited to another class or another routine, and so on)? Did you translate the pseudocode to code accurately? Did you apply the PPP recursively, breaking routines into smaller routines when needed? Did you document assumptions as you made them? Did you remove comments that turned out to be redundant? Have you chosen the best of several iterations, rather than merely stopping after your first iteration? Do you thoroughly understand your code? Is it easy to understand?

Class Quality Abstract Data Types Have you thought of the classes in your program as abstract data types and evaluated their interfaces from that point of view? Abstraction Does the class have a central purpose? Is the class well named, and does its name describe its central purpose? Does the class's interface present a consistent abstraction? Does the class's interface make obvious how you should use the class? Is the class's interface abstract enough that you don't have to think about how its services are implemented? Can you treat the class as a black box? Are the class's services complete enough that other classes don't have to meddle with its internal data? Has unrelated information been moved out of the class? Have you thought about subdividing the class into component classes, and have you subdivided it as much as you can? Are you preserving the integrity of the class's interface as you modify the class? Encapsulation Does the class minimize accessibility to its members? Does the class avoid exposing member data? Does the class hide its implementation details from other classes as much as the programming language permits? Does the class avoid making assumptions about its users, including its derived classes? Is the class independent of other classes? Is it loosely coupled? Inheritance Is inheritance used only to model "is a" relationships—that is, do derived classes adhere to the Liskov Substitution Principle? Does the class documentation describe the inheritance strategy? Do derived classes avoid "overriding" non-overridable routines? Are common interfaces, data, and behavior as high as possible in the inheritance tree? Are inheritance trees fairly shallow? Are all data members in the base class private rather than protected? Other Implementation Issues Does the class contain about seven data members or fewer? Does the class minimize direct and indirect routine calls to other classes? Does the class collaborate with other classes only to the extent absolutely necessary? Is all member data initialized in the constructor? Is the class designed to be used as deep copies rather than shallow copies unless there's a measured reason to create shallow copies?

You'll learn how to design and code better, reduce time-to-market, produce always up-to-date documentation, obtain high code coverage through quality tests, and write clean code that works. Every journey has a start and this one is no exception. Our destination is a Java developer with the test-driven development (TDD) black-belt.

But you’d need the key from which the code was assembled. The master document. Without it, there’s little to no chance of breaking a cipher. That’s why they’re so effective.

Codex Magica is the first book ever to crack the Illuminati code. It is a fully documented, authoritative reference source, as you’ll see from its lengthy index and footnotes sections. Now they won’t be able to dodge and duck, because, in addition to my exclusive investigative materials, Codex Magica also heavily quotes and relies on the Illuminati’s own, most touted textbooks and manuals.

Kids that are outside the societal norms look for a place to fit in, a way to be indoctrinated and accepted. Not because they have bad parents, or dysfunctional families, but because humans on a gut level need the traditions, rituals, and myths that used to be a part of primitive culture. We have replaced them with laws, lawyers, and court systems. The modern day thought is that right and wrong are black and white, written in a court document or a book of codes of law set down by the legislature. It is not passed on by accepted norms and ethos.

We write code, which communicates our intentions to a machine and documents our thinking for future generations of developers.

As programmers, we collect, organize, maintain, and harness knowledge. We document knowledge in specifications, we make it come alive in running code, and we use it to provide the checks needed during testing.

Use manual sanity checks in data pipelines. When optimizing data processing systems, it’s easy to stay in the “binary mindset” mode, using tight pipelines, efficient binary data formats, and compressed I/O. As the data passes through the system unseen, unchecked (except for perhaps its type), it remains invisible until something outright blows up. Then debugging commences. I advocate sprinkling a few simple log messages throughout the code, showing what the data looks like at various internal points of processing, as good practice — nothing fancy, just an analogy to the Unix head command, picking and visualizing a few data points. Not only does this help during the aforementioned debugging, but seeing the data in a human-readable format leads to “aha!” moments surprisingly often, even when all seems to be going well. Strange tokenization! They promised input would always be encoded in latin1! How did a document in this language get in there? Image files leaked into a pipeline that expects and parses text files! These are often insights that go way beyond those offered by automatic type checking or a fixed unit test, hinting at issues beyond component boundaries. Real-world data is messy. Catch early even things that wouldn’t necessarily lead to exceptions or glaring errors. Err on the side of too much verbosity.

documenting exclusively through code has some of the same basic problems as using comprehensive UML diagrams.

A document shouldn’t try to do what the code already does well.

Written documents should complement the code and the talking.

Finally, unlike Plan-and-Document, in Agile you revise code continuously to improve the design and to add functionality starting with the second iteration.

Therese Neumann, who, in addition to having stigmata, did not eat or drink anything for thirty-five years. All this has been rigorously documented by an investigating committee sent by the bishop of Regensburg:

Question of Official Secrets Act confronts Delhi Police probe By Shreeja Sen | 553 words New Delhi: Investigations into an alleged corporate espionage case are on at full steam, the Delhi Police said on Sunday even as it held around a dozen people in detention after confidential documents were stolen from the petroleum ministry. With the detainees yet to be charged, the police are proceeding only under the provisions of the Indian Penal Code, 1860—Sections 411 (dishonestly receiving stolen property) and 120B (criminal conspiracy).

The code sought to uphold accessible law, not favoring privileges by birth, religion, or superstition, nor based on local customs, exemptions, or feudal Lords. Under the penal code only true crimes, not phony offenses were outlawed. A code of civil procedure, a commercial code, a code of Criminal instructions was published, declaring the rights of citizens presumed innocent until declared guilty. It is one of the few positive documents to have influence on the rule of law to this day.

Terrorism suspects aren’t the NSA’s only targets, however. Operations against nation-state adversaries have exploded in recent years as well. In 2011, the NSA mounted 231 offensive cyber operations against other countries, according to the documents, three-fourths of which focused on “top-priority” targets like Iran, Russia, China, and North Korea. Under a $652-million clandestine program code named GENIE, the NSA, CIA, and special military operatives have planted covert digital bugs in tens of thousands of computers, routers, and firewalls around the world to conduct computer network exploitation, or CNE. Some are planted remotely, but others require physical access to install through so-called interdiction—the CIA or FBI intercepts shipments of hardware from manufacturers and retailers in order to plant malware in them or install doctored chips before they reach the customer.

I kept the poems in the tower with my hoarded documents of murders. I was constructing my own house of conscience with the transgressions of conscience on exhibit. I found myself poring over the verses for days and nights trying to break their code.

Use coding for cross-referencing the source documents and the central documents. The simplest method is to assign an alphabetic code by author or text. You can use abbreviations or keywords to record the core ideas in the selection review and abstract sections. The important notion here is that the key ideas be decipherable on the tally matrix and that tallying

In a 2006 interview by Jim Gray, Amazon CTO Werner Vogels recalled another watershed moment: We went through a period of serious introspection and concluded that a service-oriented architecture would give us the level of isolation that would allow us to build many software components rapidly and independently. By the way, this was way before service-oriented was a buzzword. For us service orientation means encapsulating the data with the business logic that operates on the data, with the only access through a published service interface. No direct database access is allowed from outside the service, and there’s no data sharing among the services.3 That’s a lot to unpack for non–software engineers, but the basic idea is this: If multiple teams have direct access to a shared block of software code or some part of a database, they slow each other down. Whether they’re allowed to change the way the code works, change how the data are organized, or merely build something that uses the shared code or data, everybody is at risk if anybody makes a change. Managing that risk requires a lot of time spent in coordination. The solution is to encapsulate, that is, assign ownership of a given block of code or part of a database to one team. Anyone else who wants something from that walled-off area must make a well-documented service request via an API.

unfolding events, and since censorship and suppression of information is underway, it’s best to approach this book as a living document. When new information emerges that can add to or improve the thousands of references and citations in this book, updates, additional notes, and new references will be provided via the QR code below, and the QR codes that appear throughout the book.

Project house is a warehouse of more than 100+ projects in all platforms focused on effectively helping understudies with quality, well-informed, dependable and project ideas and task materials that helps the final year projects for computer science students to make a good academic project and improving their project ideas.This website not only helps you to choose a project but also provides step by step instructions on how to make it happen by providing abstract, demo videos and screenshots and also an option to upload your individual project. The top project categories are python, unity, machine learning, android, .net, java and php. All software projects are exploring IEEE Papers. We provide all the documents regarding the projects. And the code deployment will also be given to you. All the software needed to the project will be given by us. You just do one thing; Pick a project that matches your interest and then you can request to the administrator for that project then administrator group will reach you for further procedures. We help you to identify the best project for you. Project house also helps to identify free internship for final year Computer science and Information science and job training facility. Register now site link is in my profile

Turing’s years at Bletchley constitute the best-documented period in his life, yet in the end his work as a code breaker amounted to a very long diversion from his dream of building a universal machine. For the bombes were about as far from universal as you could get. Their very design guaranteed their obsolescence, since it depended on the quirks and particularities of another, much smaller machine, the Enigma, of which the bombe was the huge, distorted shadow.

I also fear an attack directly upon us which shall be considerably aided by the French colonists! I therefore support your plan to act first and stage a preemptive strike against the French by launching “Operation Bright Moon”, which is now the code name for the Japanese coup d ětat which will disarm the Vichy French Forces by or during the 9th of March 1945!”  

Building on the Pentagon’s anthrax simulation (1999) and the intelligence agency’s “Dark Winter” (2001), Atlantic Storm (2003, 2005), Global Mercury (2003), Schwartz’s “Lockstep” Scenario Document (2010), and MARS (2017), the Gates-funded SPARS scenario war-gamed a bioterrorist attack that precipitated a global coronavirus epidemic lasting from 2025 to 2028, culminating in coercive mass vaccination of the global population. And, as Gates had promised, the preparations were analogous to “preparing for war.”191 Under the code name “SPARS Pandemic,” Gates presided over a sinister summer school for globalists, spooks, and technocrats in Baltimore. The panelists role-played strategies for co-opting the world’s most influential political institutions, subverting democratic governance, and positioning themselves as unelected rulers of the emerging authoritarian regime. They practiced techniques for ruthlessly controlling dissent, expression, and movement, and degrading civil rights, autonomy, and sovereignty. The Gates simulation focused on deploying the usual psyops retinue of propaganda, surveillance, censorship, isolation, and political and social control to manage the pandemic. The official eighty-nine-page summary is a miracle of fortune-telling—an uncannily precise month-by-month prediction of the 2020 COVID-19 pandemic as it actually unfolded.192 Looked at another way, when it erupted five years later, the 2020 COVID-19 contagion faithfully followed the SPARS blueprint. Practically the only thing Gates and his planners got wrong was the year. Gates’s simulation instructs public health officials and other collaborators in the global vaccine cartel exactly what to expect and how to behave during the upcoming plague. Reading through the eighty-nine pages, it’s difficult not to interpret this stunningly prescient document as a planning, signaling, and training exercise for replacing democracy with a new regimen of militarized global medical tyranny. The scenario directs participants to deploy fear-driven propaganda narratives to induce mass psychosis and to direct the public toward unquestioning obedience to the emerging social and economic order. According to the scenario narrative, a so-called “SPARS” coronavirus ignites in the United States in January 2025 (the COVID-19 pandemic began in January 2020). As the WHO declares a global emergency, the federal government contracts a fictional firm that resembles Moderna. Consistent with Gates’s seeming preference for diabolical cognomens, the firm is dubbed “CynBio” (Sin-Bio) to develop an innovative vaccine using new “plug-and-play” technology. In the scenario, and now in real life, Federal health officials invoke the PREP Act to provide vaccine makers liability protection.

The Very Difference Between Game Design & 3D Game Development You Always Want to Know Getting into the gaming industry is a dream for many people. In addition to the fact that this area is always relevant, dynamic, alive and impenetrable for problems inherent in other areas, it will become a real paradise for those who love games. Turning your hobby into work is probably the best thing that can happen in your career. What is Game Designing? A 3D Game Designer is a creative person who dreams up the overall design of a video game. Game design is a large field, drawing from the fields of computer science/programming, creative writing, and graphic design. Game designers take the creative lead in imagining and bringing to life video game worlds. Game designers discuss the following issues: • the target audience; • genre; • main plot; • alternative scenarios; • maps; • levels; • characters; • game process; • user interface; • rules and restrictions; • the primary and secondary goals, etc Without this information, further work on the game is impossible. Once the concept has been chosen, the game designers work closely with the artists and developers to ensure that the overall picture of the game is harmonized and that the implementation is in line with the original ideas. As such, the skills of a game designer are drawn from the fields of computer science and programming, creative writing and graphic design. Game designers take the creative lead in imagining and bringing to life video game stories, characters, gameplay, rules, interfaces, dialogue and environments. A game designer's role on a game development outsourcing team differs from the specialized roles of graphic designers and programmers. Graphic designers and game programmers have specific tasks to accomplish in the division of labor that goes into creating a video game, international students can major in those specific disciplines if desired. The game designer generates ideas and concepts for games. They define the layout and overall functionality of the Game Animation Studio. In short, they are responsible for creating the vision for the game. These geniuses produce innovative ideas for games. Game designers should have a knack for extraordinary and creative vision so that their game may survive in the competitive market. The field of game design is always in need of artists of all types who may be drawn to multiple art forms, original game design and computer animation. The game designer is the artist who uses his/her talents to bring the characters and plot to life. Who is a Game Development? Games developers use their creative talent and skills to create the games that keep us glued to the screen for hours and even days or make us play them by erasing every other thought from our minds. They are responsible for turning the vision into a reality, i.e., they convert the ideas or design into the actual game. Thus, they convert all the layouts and sketches into the actual product. It may involve concept generation, design, build, test and release. While you create a game, it is important to think about the game mechanics, rewards, player engagement and level design. 3D Game development involves bringing these ideas to life. Developers take games from the conceptual phase, through *development*, and into reality. The Game Development Services side of games typically involves the programming, coding, rendering, engineering, and testing of the game (and all of its elements: sound, levels, characters, and other assets, etc.). Here are the following stages of 3D Game Development Service, and the best ways of learning game development (step by step). • High Concept • Pitch • Concept • Game Design Document • Prototype • Production • Design • Level Creation • Programming

Fuchs’s transfer of scientific secrets to the Soviet Union between 1941 and 1943 was one of the most concentrated spy hauls in history, some 570 pages of copied reports, calculations, drawings, formulae and diagrams, the designs for uranium enrichment, a step-by-step guide to the fast-moving development of the atomic weapon. Much of this material was too complex and technical to be coded and sent by radio, and so Ursula passed the documents to Sergei through a “brush contact,” a surreptitious handover imperceptible to a casual observer. If Ursula needed to pass on urgent information, or bulky files, she alerted Aptekar by means of an agreed “signal site”: “I had to travel to London and, at a certain time and in a certain place, drop a small piece of chalk and tread on it.” Two days later she would cycle to the rendezvous site, a side road six miles beyond the junction of the A40 and A34 on the road from Oxford to Cheltenham; Aptekar would drive from London in the military attaché’s car and arrive at the pickup site at an appointed time for a swift handover. At one of these meetings, the Soviet officer presented her with a new Minox camera for making microdots and copying documents, and a small but powerful transmitter measuring just six by eight inches, a sixth of the size of her homemade radio and easier to conceal. She dismantled her own equipment, but kept it in reserve “for emergency use.” Fuchs was privy to the innermost workings of the atomic project and he held nothing back. In the first year, he and Peierls wrote no fewer than eleven reports together, including seminal papers on isotope separation and calculating the destructive power of

We are never told or encouraged to think of ‘unchanging moral law’ when we read the words ‘Ten Commandments’ or any of its synonymous terms. We are to think ‘covenant document.’ We are to think of a specific code of law (the Ten Commandments) that was made the covenant terms of a specific covenant document. We are always to remember that the Ten Commandments were the specific terms, written on stone tablets, of the covenant that established Israel’s special relationship with God. The Ten Commandments, Israel, Sinai, and covenant all go together.

The Ten Commandments are a covenant document given to Israel alone; they are not an unchanging moral code for all people in all ages.

Beneath the farcical veneer of The Wit to Woo it is easy to espy some of the more enduring and darker themes which habitually occupied Peake’s imagination. First among these is the question of how one is to forge an authentic personal identity in the face of constricting social codes and conventions: it could easily have been Lord Titus, instead of Percy Trellis, who protests towards the end of the play, “Oh damn the whole affair. / Pale documents have trapped me. And now I am unable to exist.

Beneath the farcical veneer of The Wit to Woo it is easy to espy some of the more enduring and darker themes which habitually occupied Peake’s imagination. First among these is the question of how one is to forge an authentic personal identity in the face of constricting social codes and conventions: it could easily have been Lord Titus, instead of Percy Trellis, who protests towards the end of the play, “Oh damn the whole affair. / Pale documents have trapped me/ And now I am unable to exist.

Beneath the farcical veneer of The Wit to Woo it is easy to espy some of the more enduring and darker themes which habitually occupied Peake’s imagination. First among these is the question of how one is to forge an authentic personal identity in the face of constricting social codes and conventions: it could easily have been Lord Titus, instead of Percy Trellis, who protests towards the end of the play, “Oh damn the whole affair. / Pale documents have trapped me/ And now I am unable to exist.

I’m a historian. I’m opposed to the destruction of documents, and I would love to see religious scholars have more information to ponder the exceptional life of Jesus Christ.” “You’re arguing both sides of my question.” “Am I? The Bible represents a fundamental guidepost for millions of people on the planet, in much the same way the Koran, Torah, and Pali Canon offer guidance to people of other religions. If you and I could dig up documentation that contradicted the holy stories of Islamic belief, Judaic belief, Buddhist belief, pagan belief, should we do that? Should we wave a flag and tell the Buddhists that we have proof the Buddha did not come from a lotus blossom? Or that Jesus was not born of a literal virgin birth? Those who truly understand their faiths understand the stories are metaphorical.” Sophie looked skeptical. “My friends who are devout Christians definitely believe that Christ literally walked on water, literally turned water into wine, and was born of a literal virgin birth.” “My point exactly,” Langdon said. “Religious allegory has become a part of the fabric of reality. And living in that reality helps millions of people cope and be better people.” “But it appears their reality is false.” Langdon chuckled. “No more false than that of a mathematical cryptographer who believes in the imaginary number ‘i’ because it helps her break codes.

Here are some reasons for the software developer community to adopt "docs-as-ecosystem": Proposes a more holistic and community-centered approach: The term "docs-as-ecosystem" recognizes that documentation is not just a set of markdown files or code snippets but an ecosystem that needs to be managed and nurtured. The term "docs-as-code" has been widely adopted recently, but it may not fully capture the complexity and diversity of documentation development. The term "docs-as-ecosystem" aligns with the industry trend towards a more holistic and community-centered approach to documentation development. Encourages collaboration: The term "docs-as-ecosystem" acknowledges that documentation development involves different roles and stakeholders, such as technical writers, designers, developers, community members, and beyond. By adopting this term, the software developer community can encourage collaboration across diverse stakeholders and facilitate the creation of high-quality documentation. Emphasizes the importance of retrieving and incorporating community feedback: The term "docs-as-ecosystem" highlights the importance of retrieving and integrating community feedback in documentation development. It recognizes that documentation is about providing information and meeting community needs and preferences.

Research on workplace engagement funded by the Bavarian State Ministry for Education and Culture found that with EEG, it is now possible to classify the type of activity an individual is engaged in—central tasks (e.g., programming, database, web development), peripheral tasks (e.g., setting up a development environment, writing documentation), and meta tasks (e.g., social media browsing, reading news sites).47 As pattern classification of brain wave data becomes ever more sophisticated, employers will be able to tell not just whether you are alert or your mind is wandering but also whether you are surfing social media or developing code.

There are. Storytelling may be the mind’s way of rehearsing for the real world, a cerebral version of the playful activities documented across numerous species which provide a safe means for practicing and refining critical skills. Leading psychologist and all-around man of the mind Steven Pinker describes a particularly lean version of the idea: “Life is like chess, and plots are like those books of famous chess games that serious players study so they will be prepared if they ever find themselves in similar straits.” Pinker imagines that through story we each build a “mental catalogue” of strategic responses to life’s potential curveballs, which we can then consult in moments of need. From fending off devious tribesmen to wooing potential mates, to organizing collective hunts, to avoiding poisonous plants, to instructing the young, to apportioning meager food supplies, and so on, our forebears faced one obstacle after another as their genes sought a presence in subsequent generations. Immersion in fictional tales grappling with a wide assortment of similar challenges would have had the capacity to refine our forebears’ strategies and responses. Coding the brain to engage with fiction would thus be a clever way to cheaply, safely, and efficiently give the mind a broader base of experience from which to operate.

These microservices were delivered not as a pile of code, nor as a website, but as a web-based API. APIs are well-defined interfaces that enable code to talk to other bits of code. Once a team builds and exposes an API to others, it’s important that they teach other teams how to use it via documentation that’s accurate and up to date.

She located a code on the document and used her computer terminal to look it up. “Postal money order.” Daphne said, “Difficult if not impossible to trace.

Extreme Programming concentrates exclusively on the active elements of a program and executable tests. Even comments added to the code do not affect program behavior, so they always fall out of sync with the active code and its driving model. External documents and diagrams do not affect the behavior of the program, so they fall out of sync. On the other hand, spoken communication and ephemeral diagrams on whiteboards do not linger to create confusion. This dependence on the code as communication medium motivates developers to keep the code clean and transparent.

The most famous ruler of this period was Hammurabi, who lived circa 1810–1750 BCE. He is best known for the Code of Hammurabi—a set of laws inscribed on a black basalt pillar that now stands in the Louvre Museum. Hammurabi’s code specifies the rate of interest on silver at 20% and on barley at 33⅓%. What is most important about the code is not what is says but what it represents. The code is a uniform legal framework for the entire Babylonian empire. It covered everything from criminal law to family law, commercial practice to property rights. It details a range of punishments for transgressions, methods of dispute resolution, and attributions of fault for various offenses. It specifies the roles of judge, jury, witnesses, plaintiffs, and defendants. It recognizes and elaborates the rights of ownership of property, including rights to lease and rights of eminent domain. It specifies the role of the written document in a contractual obligation, the necessity of receipts, and what should be done if they do not exist. It specifies legal tender. It describes the obligations of merchants, brokers, and agents and their fiduciary duties and limits to their liabilities in case of attack or theft. It places limits on the term of debt indenture (three years). In short, it creates a comprehensive, uniform framework for commerce.

Death causes us discomfort by reminding us of the humanity we share. Our healthcare system’s handling of death, on the other hand, causes us discomfort by reminding us of the shared humanity we choose to ignore. As I documented

While pulling clean drafts together took thousands of hours of work, the stories had all but revealed themselves. Facebook had allowed human trafficking to take place in the Persian Gulf on its platform as long as it occurred through brick-and-mortar businesses. In trying to improve the platform and boost user numbers, it had actually made the site, and the people who used it, angrier. Mental health researchers had concluded “we make body issues worse” and that Instagram was a toxic place for many teen girls, in particular. We divided up the stories among ourselves. Georgia Wells began interviewing young women who had developed eating disorders or body image issues of the sort that Instagram’s researchers worried their product might aggravate. The story she led would cite company documents that found “comparisons on Instagram can change how young women view and describe themselves,” citing research that found 32 percent of teen girls said that “when they felt bad about their bodies, Instagram made them feel worse.

For a story on Facebook’s failings in developing countries, Newley Purnell and Justin Scheck found a woman who had been trafficked from Kenya to Saudi Arabia, and they were looking into the role Facebook had played in recruiting hit men for Mexican drug lords. That story would reveal that Facebook had failed to effectively shut down the presence of the Jalisco New Generation Cartel on Facebook and Instagram, allowing it to repeatedly post photos of extreme gore, including severed hands and beheadings. Looking into how the platform encouraged anger, Keach Hagey relied on documents showing that political parties in Poland had complained to Facebook that the changes it had made around engagement made them embrace more negative positions. The documents didn’t name the parties; she was trying to figure out which ones. Deepa Seetharaman was working to understand how Facebook’s vaunted AI managed to take down such a tiny percentage—a low single-digit percent, according to the documents Haugen had given me—of hate speech on the platform, including constant failures to identify first-person shooting videos and racist rants.

If you want code that presents good abstractions, you must document those abstractions with comments.

I discovered other parallels with South African apartheid. I learned that to control the movement of Black people, the apartheid regime had imposed a “pass” system forcing every Black person to carry an identity document indicating whether they had permission to be in a given area—and permission to be in any city was granted only to those employed by white farms, mines, or businesses. Black people who lacked a pass to be in a city could be summarily deported to a rural economic wasteland known as a Bantustan. Similarly, to control our movement as Palestinians in the occupied territories, Israel imposes color-coded identification cards and license plates, has installed an elaborate permit and checkpoint system, and has designated specific roads we’re allowed to drive on—not to mention that Israel erected an apartheid wall.

Here are a few of of the most important red flags discussed in this book. The presence of any of these symptoms in a system suggests that there is a problem with the system’s design: Shallow Module: the interface for a class or method isn’t much simpler than its implementation (see pp. 25, 110). Information Leakage: a design decision is reflected in multiple modules (see p. 31). Temporal Decomposition: the code structure is based on the order in which operations are executed, not on information hiding (see p. 32). Overexposure: An API forces callers to be aware of rarely used features in order to use commonly used features (see p. 36). Pass-Through Method: a method does almost nothing except pass its arguments to another method with a similar signature (see p. 52). Repetition: a nontrivial piece of code is repeated over and over (see p. 68). Special-General Mixture: special-purpose code is not cleanly separated from general purpose code (see p. 71). Conjoined Methods: two methods have so many dependencies that its hard to understand the implementation of one without understanding the implementation of the other (see p. 75). Comment Repeats Code: all of the information in a comment is immediately obvious from the code next to the comment (see p. 104). Implementation Documentation Contaminates Interface: an interface comment describes implementation details not needed by users of the thing being documented (see p. 114). Vague Name: the name of a variable or method is so imprecise that it doesn’t convey much useful information (see p. 123). Hard to Pick Name: it is difficult to come up with a precise and intuitive name for an entity (see p. 125). Hard to Describe: in order to be complete, the documentation for a variable or method must be long. (see p. 133). Nonobvious Code: the behavior or meaning of a piece of code cannot be understood easily. (see p. 150).

which a drawing imported into a text document can no longer be altered, but must be changed in the original graphics program and reintroduced into the text document.) Out of the box the Star was multilingual, offering typefaces and keyboard configurations that could be implemented in the blink of an eye for writing in Russian, French, Spanish, and Swedish through the use of “virtual keyboards”—graphic representations of keyboards that appeared on screen to show the user where to find the unique characters in whatever language he or she was using. In 1982 an internal library of 6,000 Japanese kanji characters was added; eventually Star users were able to draft documents in almost every modern language, from Arabic and Bengali to Amharic and Cambodian. As the term implied, the user’s view of the screen resembled the surface of a desk. Thumbnail-sized icons representing documents were lined up on one side of the screen and those representing peripheral devices—printers, file servers, e-mail boxes—on the other. The display image could be infinitely personalized to be tidy or cluttered, obsessively organized or hopelessly confused, alphabetized or random, as dictated by the user’s personality and taste. The icons themselves had been painstakingly drafted and redrafted so they would be instantaneously recognized by the user as document pages (with a distinctive dog-eared upper right corner), file folders, in and out baskets, a clock, and a wastebasket. Thanks to the system’s object-oriented software, the Star’s user could launch any application simply by clicking on the pertinent icon; the machine automatically “knew” that a text document required it to launch a text editor or a drawing to launch a graphics program. No system has ever equaled the consistency of the Star’s set of generic commands, in which “move,” “copy,” and “delete” performed similar operations across the entire spectrum of software applications. The Star was the epitome of PARC’s user-friendly machine. No secretary had to learn about programming or code to use the machine, any more than she had to understand the servomechanism driving the dancing golf ball to type on an IBM Selectric typewriter. Changing a font, or a margin, or the space between typed lines in most cases required a keystroke or two or a couple of intuitive mouse clicks. The user understood what was happening entirely from watching the icons or documents move or change on the screen. This was no accident: “When everything in a computer system is visible on the screen,” wrote David Smith, a designer of the Star interface, “the display becomes reality. Objects and actions can be understood purely in terms of their effects on the display.

North America felt that the king of England was treating them unjustly. Their representatives gathered in the city of Philadelphia, and on 4 July 1776 the colonies declared that their inhabitants were no longer subjects of the British Crown. Their Declaration of Independence proclaimed universal and eternal principles of justice, which, like those of Hammurabi, were inspired by a divine power. However, the most important principle dictated by the American god was somewhat different from the principle dictated by the gods of Babylon. The American Declaration of Independence asserts that: We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable rights, that among these are life, liberty, and the pursuit of happiness. Like Hammurabi’s Code, the American founding document promises that if humans act according to its sacred principles, millions of them would be able to cooperate effectively, living safely and peacefully in a

In-code documentation plays a crucial role in software design. Comments are essential to help developers understand a system and work efficiently, but the role of comments goes beyond this. Documentation also plays an important role in abstraction; without comments, you can’t hide complexity.

I have never been one of those people—I know you aren't, either—who feels that the love one has for a child is somehow a superior love, one more meaningful, more significant, and grander than any other. I didn't feel that before Jacob, and I didn't feel that after. But it is a singular love, because it is a love whose foundation is not physical attraction, or pleasure, or intellect, but fear. You have never known fear until you have a child, and maybe that is what tricks us into thinking that it is more magnificent, because the fear itself is more magnificent. Every day, your first thought is not “I love him” but “How is he?” The world, overnight, rearranges itself into an obstacle course of terrors. I would hold him in my arms and wait to cross the street and would think how absurd it was that my child, that any child, could expect to survive this life. It seemed as improbable as the survival of one of those late-spring butterflies—you know, those little white ones—I sometimes saw wobbling through the air, always just millimeters away from smacking itself against a windshield. And let me tell you two other things I learned. The first is that it doesn't matter how old that child is, or when or how he became yours. Once you decide to think of someone as your child, something changes, and everything you have previously enjoyed about them, everything you have previously felt for them, is preceded first by that fear. It's not biological; it's something extra-biological, less a determination to ensure the survival of one's genetic code, and more a desire to prove oneself inviolable to the universe's feints and challenges, to triumph over the things that want to destroy what's yours. The second thing is this: when your child dies, you feel everything you'd expect to feel, feelings so well-documented by so many others that I won't even bother to list them here, except to say that everything that's written about mourning is all the same, and it's all the same for a reason—because there is no real deviation from the text. Sometimes you feel more of one thing and less of another, and sometimes you feel them out of order, and sometimes you feel them for a longer time or a shorter time. But the sensations are always the same. But here's what no one says—when it's your child, a part of you, a very tiny but nonetheless unignorable part of you, also feels relief. Because finally, the moment you have been expecting, been dreading, been preparing yourself for since the day you became a parent, has come. Ah, you tell yourself, it's arrived. Here it is. And after that, you have nothing to fear again.

During the trip to the NATO base, Agnew noticed something that made him wary. “I observed four F84F aircraft . . . sitting on the end of a runway, each was carrying two MK 7 [nuclear] gravity bombs,” he wrote in a document declassified in 2023. What this meant was that “custody of the MK 7s was under the watchful eye of one very young U.S. Army private armed with a M1 rifle with 8 rounds of ammunition.” Agnew told his colleagues: “The only safeguard against unauthorized use of an atomic bomb was this single G.I. surrounded by a large number of foreign troops on foreign territory with thousands of Soviet troops just miles away.” Back in the United States, Agnew contacted a project engineer at Sandia Laboratories named Don Cotter and asked “if we could insert an electronic ‘lock’ in the [bomb’s] firing circuit that could prevent just any passerby from arming the MK 7.” Cotter got to work. He put together a demonstration of a device, a lock and coded switch, that functioned as follows: “[a] 3-digit code would be entered, a switch was thrown, the green light extinguished, and the red light illuminated indicating the arming circuit was live.

Selecting names for variables, methods, and other entities is one of the most underrated aspects of software design. Good names are a form of documentation: they make code easier to understand. They reduce the need for other documentation and make it easier to detect errors. Conversely, poor name choices increase the complexity of code and create ambiguities and misunderstandings that can result in bugs.

The researchers [Picca and Feagin] document that in front-stage settings (those in which people of color were present), the white students displayed a range of racially conscious behaviors, including the following: - Acting overly nice - Avoiding contact (e.g., crossing a street or not going to a particular bar or club) - Mimicking "black mannerisms and speech" - Being careful not to use racial terms or labels - Using code words to talk negatively about people of color - Occasional violence directed at people of color In backstage settings, where people of color were not present, white students often used humor to reinforce racial stereotypes about people of color, particularly blacks. Picca and Feagin argue that the purpose of these backstage performances is to create white solidarity and to reinforce the ideology of white and male supremacy. This behavior keeps racism circulating, albeit in less formal but perhaps more powerful ways than in the past. Today we have a cultural norm that insists we hide our racism from people of color and deny it among ourselves, but not that we actually challenge it. In fact, we are socially penalized for challenging racism. (p. 49-50)

If multiple teams have direct access to a shared block of software code or some part of a database, they slow each other down. Whether they’re allowed to change the way the code works, change how the data are organized, or merely build something that uses the shared code or data, everybody is at risk if anybody makes a change. Managing that risk requires a lot of time spent in coordination. The solution is to encapsulate, that is, assign ownership of a given block of code or part of a database to one team. Anyone else who wants something from that walled-off area must make a well-documented service request via an API.

If any of the news coverage had drawn blood, Meta wasn’t going to show it. Zuckerberg told the company’s People Planning team to bring him an aggressive hiring target for 2022. When they brought him an unprecedentedly ambitious plan to bring on 40,000 new staffers that year, Zuckerberg took the one-page document—known as “the napkin”—and then passed it back with a handwritten instruction to hire 8,000 more. “If we don’t hit these targets it’s game over,” Recruiting VP Miranda Kalinowski told the managers on her staff. To handle the deluge of hiring, Meta brought on an additional 1,000 recruiters between the last quarter of 2021 and the first quarter of the following year. Few of the new staffers would be slated to go into integrity work. Zuckerberg had declared that the company’s existing products were no longer its future, and Haugen’s document breach had solidified a sense that researchers and data scientists working on societal problems contained a potential corporate fifth column.

But despite the fact that this boy was clearly suicidal and required hospitalization, he was not included among the patients listed as having developed serious adverse effects in the published 2001 Paxil study. Other patients were similarly miscoded. One was a fifteen-year-old girl who had been withdrawn from the Brown study site in 1995 after becoming combative with her mother. According to internal university documents that Howard gave me, Brown researchers knew that this girl had become suicidal after taking Paxil. In a memo to the Institutional Review Board dated October 30, 1995, Martin Keller wrote that this teenager, who had been enrolled in the study in June 1995, “was hospitalized on 9/15/95 due to becoming very combative with her mother and threatening suicide.” Yet instead of coding her behavior as an adverse effect related to Paxil, Keller in his memo says she was “terminated from the study for non-compliance.” The Brown investigators may have coded her as noncompliant because she had stopped taking Paxil before having her meltdown. But they shouldn’t have, according to several clinicians familiar with the study. The Brown researchers should have included all adverse effects experienced by their patients, regardless of what may have caused the problems. As a Harvard Medical School biostatistician later told me, “You shouldn’t try to make these subjective attributions and exclude patients who don’t fit into your thesis.” As research has shown, the SSRI antidepressants can cause serious side effects, including suicidal behaviors and hostility, weeks after people stop taking them.

Tyresia (Τειρεσίας) Tyresias is blind, it is said, but we are not really sure. We read that Tyresias was blinded by the gods because they did not want him to prophesy about 'private' matters. However, other ancient historical documents say that Tyresias was the son of a nymph who was made so by Athena as a punishment for seeing her bathing naked, but was then made a soothsayer by the goddess herself at his mother's request. Perhaps the best-known fact about Tyiresias is the one I am about to tell. One day, while walking on Mount Cillene, Tyresias came upon two snakes mating, and, annoyed by the scene, killed the female (according to one version, he merely separated them by striking first the female and then the male). At the same time, Tyresias was transformed from a man into a woman. He lived in this state for seven years, experiencing all the pleasures a woman can experience. After this period he was confronted with the same scene as the serpents. This time he killed the male serpent and instantly became a man again. One day, Zeus and Hera were divided by an argument: whether in love the man or the woman felt more pleasure. Unable to reach an agreement, with Zeus claiming it was the woman and Hera claiming it was the man, they decided to summon Tyresias, who was considered the only one who could settle the dispute as he was both man and woman. When questioned by the gods, he replied that pleasure is made up of ten parts: a man feels only one and a woman nine, so a woman feels nine times as much pleasure as a man. The goddess Hera, furious that Tyresias had revealed such a secret, made him blind, but Zeus, to compensate for the damage done, gave him the power to foresee the future and the gift of life for seven generations: the Greek gods cannot undo what other gods have done or decided. So Tyresias' blindness is actually the condition for him to fulfil his role as soothsayer. Sight comes into play directly, as a violation of a code of conduct enunciated by Callimachus (the laws of Cronus state that whoever sees an immortal against his will will pay a high price for that sight).

No writer in the world agonizes over words the way a scientist does. Terminology is everything: we identify something by its established name, describe it using the universally agreed-upon terms, study it in a completely individual way, and then write about it using a code that takes years to master. When documenting our work, we “hypothesize” but never “guess”; we “conclude,” not just “decide.” We view the word “significant” to be so vague that it is useless but know that the addition of “highly” can signify half a million dollars of funding.