Leading technologists, historians, and journalists reveal the stories behind the computer coding that touches all aspects of life—for better or worse Few of us give much thought to computer code or how it comes to be. The very word “code” makes it sound immutable or even inevitable. “You Are Not Expected to Understand This” demonstrates that, far from being preordained, computer code is the result of very human decisions, ones we all live with when we use social media, take photos, drive our cars, and engage in a host of other activities. Everything from law enforcement to space exploration relies on code written by people who, at the time, made choices and assumptions that would have long-lasting, profound implications for society. Torie Bosch brings together many of today’s leading technology experts to provide new perspectives on the code that shapes our lives. Contributors discuss a host of topics, such as how university databases were programmed long ago to accept only two genders, what the person who programmed the very first pop-up ad was thinking at the time, the first computer worm, the Bitcoin white paper, and perhaps the most famous seven words in Unix history: “You are not expected to understand this.” This compelling book tells the human stories behind programming, enabling those of us who don’t think much about code to recognize its importance, and those who work with it every day to better understand the long-term effects of the decisions they make. With an introduction by Ellen Ullman and contributions by Mahsa Alimardani, Elena Botella, Meredith Broussard, David Cassel, Arthur Daemmrich, Charles Duan, Quinn DuPont, Claire L. Evans, Hany Farid, James Grimmelmann, Katie Hafner, Susan C. Herring, Syeda Gulshan Ferdous Jana, Lowen Liu, John MacCormick, Brian McCullough, Charlton McIlwain, Lily Hay Newman, Margaret O’Mara, Will Oremus, Nick Partridge, Benjamin Pope, Joy Lisi Rankin, Afsaneh Rigot, Ellen R. Stofan, Lee Vinsel, Josephine Wolff, and Ethan Zuckerman.

For the past 20 years, UNIX insiders have cherished and zealously guarded pirated photocopies of this manuscript, a "hacker trophy" of sorts. Now legal (and legible) copies are available. An international "who's who" of UNIX wizards, including Dennis Ritchie, have contributed essays extolling the merits and importance of this underground classic.

Get more out of your legacy systems: more performance, functionality, reliability, and manageability Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts. In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control. The topics covered include Understanding the mechanics of software change: adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform—with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structure This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

In this delightfully witty, provocative book, literature professor and psychoanalyst Pierre Bayard argues that not having read a book need not be an impediment to having an interesting conversation about it. (In fact, he says, in certain situations reading the book is the worst thing you could do.) Using examples from such writers as Graham Greene, Oscar Wilde, Montaigne, and Umberto Eco, he describes the varieties of "non-reading"-from books that you've never heard of to books that you've read and forgotten-and offers advice on how to turn a sticky social situation into an occasion for creative brilliance. Practical, funny, and thought-provoking, How to Talk About Books You Haven't Read-which became a favorite of readers everywhere in the hardcover edition-is in the end a love letter to books, offering a whole new perspective on how we read and absorb them.

An argument that we must read code for more than what it does—we must consider what it means. Computer source code has become part of popular discourse. Code is read not only by programmers but by lawyers, artists, pundits, reporters, political activists, and literary scholars; it is used in political debate, works of art, popular entertainment, and historical accounts. In this book, Mark Marino argues that code means more than merely what it does; we must also consider what it means. We need to learn to read code critically. Marino presents a series of case studies—ranging from the Climategate scandal to a hactivist art project on the US-Mexico border—as lessons in critical code reading. Marino shows how, in the process of its circulation, the meaning of code changes beyond its functional role to include connotations and implications, opening it up to interpretation and inference—and misinterpretation and reappropriation. The Climategate controversy, for example, stemmed from a misreading of a bit of placeholder code as a “smoking gun” that supposedly proved fabrication of climate data. A poetry generator created by Nick Montfort was remixed and reimagined by other poets, and subject to literary interpretation. Each case study begins by presenting a small and self-contained passage of code—by coders as disparate as programming pioneer Grace Hopper and philosopher Friedrich Kittler—and an accessible explanation of its context and functioning. Marino then explores its extra-functional significance, demonstrating a variety of interpretive approaches.

New York Times bestselling author Lysa TerKeurst unveils her heart amid shattering circumstances and shows readers how to live assured when life doesn't turn out like they expected. What do you do when God’s timing seems questionable, His lack of intervention hurtful, and His promises doubtful? Life often looks so very different than we hoped or expected. Some events may simply catch us off guard for a moment, but others shatter us completely. We feel disappointed and disillusioned, and we quietly start to wonder about the reality of God’s goodness. Lysa TerKeurst understands this deeply. But she's also discovered that our disappointments can be the divine appointments our souls need to radically encounter God. In It's Not Supposed to Be This Way, Lysa invites us into her own journey of faith and, with grit, vulnerability, and honest humor, helps us to: Stop being pulled into the anxiety of disappointment by discovering how to better process unmet expectations and other painful situations. Train ourselves to recognize the three strategies of the enemy so we can stand strong and persevere through unsettling relationships and uncertain outcomes. Discover the secret of being steadfast and not panicking when God actually does give us more than we can handle. Shift our suspicion that God is cruel or unfair to the biblical assurance that God is protecting and preparing us. Know how to encourage a friend and help her navigate hard realities with real help from God's truth.

The bestselling author of ""A Whack on the Side of the Head"" now interprets the aphorisms of Heraclitus as springboards to creativity.