Computer Programmers Quotes

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.

That's the thing about people who think they hate computers. What they really hate is lousy programmers.

The best programs are written so that computing machines can perform them quickly and so that human beings can understand them clearly. A programmer is ideally an essayist who works with traditional aesthetic and literary forms as well as mathematical concepts, to communicate the way that an algorithm works and to convince a reader that the results will be correct.

The computer programmer is a creator of universes for which he alone is the lawgiver. No playwright, no stage director, no emperor, however powerful, has ever exercised such absolute authority to arrange a stage or field of battle and to command such unswervingly dutiful actors or troops.

A computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things.

Well, writing novels is incredibly simple: an author sits down…and writes. Granted, most writers I know are a bit strange. Some, downright weird. But then again, you’d have to be. To spend hundreds and hundreds of hours sitting in front of a computer screen staring at lines of information is pretty tedious. More like a computer programmer. And no matter how cool the Matrix made looking at code seem, computer programmers are even weirder than authors.

All great programmers learn the same way. They poke the box. They code something and see what the computer does. They change it and see what the computer does. They repeat the process again and again until they figure out how the box works.

The best computer programmers never write a new program when they can use an old one for a new job.

Most of us know that the media tell us our bodies are imperfect - too fat, to smelly, too wrinkled, or too soft. And, even though we may know it’s horseshit, these messages still seep into our brains and mess with our self-esteem. In a media-saturated country where most images of women and men have been photoshopped to perfection, it’s hard to find a living supermodel (much less a computer programmer), who doesn’t wish she had sexier earlobes or a tighter ass. So, buck up, even the prettiest bombshell has body insecurities. You can spend your life thinking your butt’s too big (or your cock’s too small) or feeling sexy as hell. Make the choice to appreciate your body as it is.

Monty Python is, for reasons best known to nobody, rather popular with computer programmers. There’s even a programming language called Python, based on their sketches.

With software there are only two possibilites: either the users control the programme or the programme controls the users. If the programme controls the users, and the developer controls the programme, then the programme is an instrument of unjust power.

Computer programmers are highly susceptible to the just world fallacy (that their economic good fortune is the product of virtue rather than circumstance) and the fallacy of transferable expertise (that being competent in one field means they’re competent in others).

While we may continue to use the words smart and stupid, and while IQ tests may persist for certain purposes, the monopoly of those who believe in a single general intelligence has come to an end. Brain scientists and geneticists are documenting the incredible differentiation of human capacities, computer programmers are creating systems that are intelligent in different ways, and educators are freshly acknowledging that their students have distinctive strengths and weaknesses.

DON’T GIVE UP! When the battle seems endless and you think you’ll never make it, remember that you are reprogramming a very carnal, fleshly, worldly mind to think as God thinks. Impossible? No! Difficult? Yes! But, just think, you have God on your team. I believe He is the best “computer programmer” around. (Your mind is like a computer that has had a lifetime of garbage programmed into it.) God is working on you; at least, He is if you have invited Him to have control of your thoughts. He is reprogramming your mind. Just keep cooperating with Him—and don’t give up!

You Can't Write Perfect Software. Did that hurt? It shouldn't. Accept it as an axiom of life. Embrace it. Celebrate it. Because perfect software doesn't exist. No one in the brief history of computing has ever written a piece of perfect software. It's unlikely that you'll be the first. And unless you accept this as a fact, you'll end up wasting time and energy chasing an impossible dream.

You are not reading this book because a teacher assigned it to you, you are reading it because you have a desire to learn, and wanting to learn is the biggest advantage you can have.

The best computer programmers are much better than novices at remembering the overall structure of programs because they understand better what they’re intended to do and how.

As a feminist I feel immediately guilty because everyone is trying to encourage girls into STEM subjects now, but to be honest I’m not dedicated enough to the Vagenda to force myself to become a computer programmer.

The corollary of constant change is ignorance. This is not often talked about: we computer experts barely know what we're doing. We're good at fussing and figuring out. We function well in a sea of unknowns. Our experience has only prepared us to deal with confusion. A programmer who denies this is probably lying, or else is densely unaware of himself.

When a computer creates art, who is the artist—the computer or the programmer? At MIT, a recent exhibit of highly accomplished algorithmic art had put an awkward spin on the Harvard humanities course: Is Art What Makes Us Human?

What one programmer can do in one month, two programmers can do in two months.

Babbage had most of this system sketched out by 1837, but the first true computer to use this programmable architecture didn’t appear for more than a hundred years.

How many computer programmers does it take to change a light bulb? Are you kidding? That's a hardware problem!

With software there are only two possibilites: either the users control the programme or the programme controls the users. If the programme controls the users, and the developer controls the programme, then the programme is an instrument of unjust power.

An Essay from Andy Weir: How Science Made Me a Writer I’m a nerd. Okay, a lot of people say that these days. But I really am. I was hired as a computer programmer for a national laboratory at age fifteen.

Computer science education cannot make anybody an expert programmer any more than studying brushes and pigment can make somebody an expert painter.

Each mobile phone today – indeed, each washing machine – has more computing power than NASA could deploy on the Apollo programme.

Like Ada Lovelace, Turing was a programmer, looking inward to the step-by-step logic of his own mind. He imagined himself as a computer. He distilled mental procedures into their smallest constituent parts, the atoms of information processing.

For a long time it puzzled me how something so expensive, so leading edge, could be so useless, and then it occurred to me that a computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things. They are, in short, a perfect match.

if you program a purpose into a computer program, does that constitute its will? Does it have free will, if a programmer programmed its purpose?

After all, computer science was man-made. All the answers had to be there.

Simple explanation for kids: Seen as if a computer game: God is the programmer/creator of all the universe and all things, and Jesus would be his avatar/character in the game.

Our brains are like computers; it's our responsibility to programme them well, daily, and remove the viruses.

perfect software doesn't exist. No one in the brief history of computing has ever written a piece of perfect software.

When a computer creates art, who is the artist—the computer or the programmer?

The computer programmer creates the only path available to the computer user; the effect of his decisions on others is masked by their abstraction.

(To think like a computer programmer, it helps to be lazy.)

In other words, evolution is neither a free-for-all, nor the execution of a rigidly predetermined computer programme. It could be compared to a musical composition whose possibilities are limited by the rules of harmony and the structure of the diatonic scales-which, however, permit an inexhaustible number of original creations. Or it could be compared to the game of chess obeying fixed rules but with equally inexhaustible variations.

The second reason that deep work is valuable is because the impacts of the digital network revolution cut both ways. If you can create something useful, its reachable audience (e.g., employers or customers) is essentially limitless—which greatly magnifies your reward. On the other hand, if what you’re producing is mediocre, then you’re in trouble, as it’s too easy for your audience to find a better alternative online. Whether you’re a computer programmer, writer, marketer, consultant, or entrepreneur, your situation has become similar to Jung trying to outwit Freud, or Jason Benn trying to hold his own in a hot start-up: To succeed you have to produce the absolute best stuff you’re capable of producing—a task that requires depth.

The Vedic viewpoint presents a type of linguistic realism in which reality is the 'text' which is being processed by the observer. Reality can also be modified by adding text to it similar to how a programmer programs a computer by inputting a computer program.

Poke the box How do computer programmers learn their art? Is there a step-by-step process that guarantees you’ll get good? All great programmers learn the same way. They poke the box. They code something and see what the computer does. They change it and see what the computer does. They repeat the process again and again until they figure out how the box works. The box might be a computer or it might be a market or it might be a customer or it might be your boss. It’s a puzzle, one that can be solved in only one way—by poking.

So, when Cole was two and I was four, we moved to Goshen Falls. Lucky us! The whole town is three blocks long. We have a cute little farm with a cute little farmhouse. And even though Mom and Dad are computer programmers — not farmers — we have a backyard full of chickens.

A great programmer, on a roll, could create a million dollars worth of wealth in a couple weeks. A mediocre programmer over the same period will generate zero or even neg- ative wealth (e.g. by introducing bugs). This is why so many of the best programmers are libertarians.

if you program a purpose into a computer program, does that constitute its will? Does it have free will, if a programmer programmed its purpose? Is that programming any different from the way we are programmed by our genes and brains? Is a programmed will a servile will? Is human will a servile will? And is not the servile will the home and source of all feelings of defilement, infection, transgression, and rage?

What does AI have to do with me? Isn't it a distant future that has nothing to do with me, not a scientist, a technician, or a computer programmer? Well, Artificial intelligence is not a story of someone who has nothing to do with it, but the fact is, it is now everyone's story.

Intellectual curiosity was not one of the motives on the FBI’s list. Indeed, the whole concept seemed foreign to them. Those in authority tend to be annoyed by hackers’ general attitude of disobedience. But that disobedience is a byproduct of the qualities that make them good programmers.

This is why so many of the best programmers are libertarians. In our world, you sink or swim, and there are no excuses. When those far removed from the creation of wealth — undergraduates, reporters, politicians — hear that the richest 5% of the people have half the total wealth, they tend to think injustice! An experienced programmer would be more likely to think is that all? The top 5% of programmers probably write 99% of the good software.

Most organised abuser groups call each particular training a “programme”, as if you were a computer. Many specific trained behaviours have “on” and “off” triggers or switches. Some personality systems are set up with an inner world full of wires or strings that connect switches to their effects. These can facilitate a series of actions by a series of insiders. For example, one part watches the person function in the outside world, and presses a button if he or she sees the person disobeying instructions. The button is connected to an internal wire, which rings a bell in the ear of another part. This part then engages in his or her trained behaviour, opening a door to release the pain of a rape, or cutting the person's arm in a certain pattern, or pushing out a child part. So the watcher has no idea of who the other part is or what she or he does. These events can be quite complicated.

Ultimately, man should not ask what the meaning of his life is, but rather must recognize that it is he who is asked. In a word, each man is questioned by life; and he can only answer to life by answering for his own life; to life he can only respond by being responsible.” Personal responsibility, or proactivity, is fundamental to the first creation. Returning to the computer metaphor, Habit 1 says, “You are the programmer.” Habit 2, then, says, “Write the program.

There’s a gravity and sense of importance inherent in deep work—whether you’re Ric Furrer smithing a sword or a computer programmer optimizing an algorithm. Gallagher’s theory, therefore, predicts that if you spend enough time in this state, your mind will understand your world as rich in meaning and importance.

Russians had a reputation for being the best programmers on Wall Street, and Serge thought he knew why: They had been forced to learn to program computers without the luxury of endless computer time. Many years later, when he had plenty of computer time, Serge still wrote out new programs on paper before typing them into the machine. “In Russia, time on the computer was measured in minutes,” he said. “When you write a program, you are given a tiny time slot to make it work.

Pascal (Object Pascal - Free Pascal) for real programmers, Delphi for Nerds... C/C++ for people who always wishes to do things like reinventing the wheel.

Although computer science tends to be thought of as a traditionally male-dominated field, the world’s first programmer was a woman.

Programmers tend to be divided into tribes by the languages they use. More even than by the kinds of programs they write.

When programmers speak of "computer literacy," they are drawing red lines around ethnic groups, too, yet few have pointed this out.

Tests are stories we tell the next generation of programmers on a project.

However, for programmers, combining rich, flexible human thought with the rigid constraints of a digital computer exposes the power and the deepest flaws of both.

It is common knowledge in the programmer's circle that almost every smartphone in the world is infected with some form of trojan.

In our online world there is no way for a regular civilian to keep their phone uninfected. And that includes everybody except skilled and resourceful programmers.

Douglas Adams amusingly satirized computer addiction of exactly the kind that hit me. The target of his satire was the programmer who had a particular problem X, which needed solving. He could have written a program in five minutes to solve X and then got on and used his solution. But instead of just doing that, he spent days and weeks writing a more general program that could be used by anybody at any time to solve all similar problems of the general class of X. The fascination lies in the generality and in the purveying of an aesthetically pleasing, user-friendly product for the benefit of a population of hypothetical and very probably non-existent users – not in actually finding the answer to the particular problem X.

To paraphrase an old joke among programmers, “Writing code accounts for 90 percent of programming. Debugging code accounts for the other 90 percent.” Your computer will do only what you tell it to do; it won’t read your mind and do what you intended it to do. Even professional programmers create bugs all the time, so don’t feel discouraged if your program has a problem.

Hollywood and similar “popular culture” sources of disinformation have assigned largely negative images to programmers. For example, we have all seen the solitary, fat, ugly nerd with no social skills who is obsessed with video games and breaking into other people’s computers. He (almost always a male) is as likely to want to destroy the world as he is to want to save it. Obviously, milder versions of such caricatures exist in real life, but in our experience they are no more frequent among software developers than they are among lawyers, police officers, car salesmen, journalists, artists, or politicians.

STOP STOPPING A growing body of research shows that often what looks like “multitasking” is actually “rapid task-switching,” especially when technology is involved. One study of computer programmers showed that as they attempted to work, they interrupted themselves or were interrupted about every 3 minutes, usually to check email. Other studies have shown that it’s now common for office workers to interrupt what they’re doing to check email 30 to 40 times an hour and that the more a worker self-interrupts, the more stress he or she experiences. Studies of college students show that while trying to study, they lose focus every 3 minutes on average, for example, to check Facebook or text a friend. The more often they interrupt themselves to “multitask,” the worse they do on tests. Multitasking with technology is no way to make the most of your time—those emails can wait!

Usability, fundamentally, is a matter of bringing a bit of human rights into the world of computer-human interaction. It's a way to let our ideals shine through in our software, no matter how mundane the software is. You may think that you're stuck in a boring, drab IT department making mind-numbing inventory software that only five lonely people will ever use. But you have daily opportunities to show respect for humanity even with the most mundane software.

You’re either remarkable or invisible,” says Seth Godin in his 2002 bestseller, Purple Cow.1 As he elaborated in a Fast Company manifesto he published on the subject: “The world is full of boring stuff—brown cows—which is why so few people pay attention…. A purple cow… now that would stand out. Remarkable marketing is the art of building things worth noticing.”2 When Giles read Godin’s book, he had an epiphany: For his mission to build a sustainable career, it had to produce purple cows, the type of remarkable projects that compel people to spread the word. But this left him with a second question: In the world of computer programming, where does one launch remarkable projects? He found his second answer in a 2005 career guide with a quirky title: My Job Went to India: 52 Ways to Save Your Job.3 The book was written by Chad Fowler, a well-known Ruby programmer who also dabbles in career advice for software developers.

The fact is that life is not a race: success in life isn’t determined by how well you do compared to other people. It’s determined by whether you are able to achieve whatever hopes and dreams you set for yourself: to build a great company, to write a great book, to excel as a computer programmer, to be a great teacher or a great plumber. None of that requires besting others; the favorable circumstances they enjoy can’t hold you back. Exactly the reverse is true.

Programmers are always surrounded by complexity; we cannot avoid it. Our applications are complex because we are ambitious to use our computers in ever more sophisticated ways. Programming is complex because of the large number of conflicting objectives for each of our programming projects. If our basic tool, the language in which we design and code our programs, is also complicated, the language itself becomes part of the problem rather than part of its solution.

Shortly before she died in 2011, Jean Jennings Bartik reflected proudly on the fact that all the programmers who created the first general-purpose computer were women: “Despite our coming of age in an era when women’s career opportunities were generally quite confined, we helped initiate the era of the computer.

Before you start to look at the bug, make sure that you are working on code that built cleanly—without warnings. We routinely set compiler warning levels as high as possible. It doesn’t make sense to waste time trying to find a problem that the computer could find for you! We need to concentrate on the harder problems at hand.

Instead of feeling like you are the computer genius, descending from computer heaven to save your poor customer from purgatory, turn the tables around. If you’re, for example, working in the insurance industry, think of your customer as a subject matter expert in insurance from which you have to learn in order to get your job done.

The government spying on people doesn’t literally make programmers write worse code. It just leads eventually to a world in which bad ideas will win. And because this is so important to hackers, they’re especially sensitive to it. They can sense totalitarianism approaching from a distance, as animals can sense an approaching thunderstorm.

Take a simple pocket pen, so cheap that they are given away as advertising. Back of it lie several sorts of chemists, metallurgists, synthetic polymer experts, mechanical engineers, extrusion presses, computer programmers, computers, computer technicians, toolmakers, electrical engineers, a planet-wide petroleum industry, five or more sorts of mines with mining engineers, geologists, miners, railroads, steamships, production engineers, management specialists, merchandizing psychologists—et cetera to a splitting headache. It is impossible even to list the myriad special skills that underlie even the most trivial trade item of our enormously complex and interdependent industrial web.

My mother has always loved piano music and hungered to play. When she was in her early sixties, she retired from her job as a computer programmer so that she could devote herself more fully to the piano. As she had done with her dog obsession, she took her piano education to an extreme. She bought not one, not two, but three pianos. One was the beautiful Steinway B, a small grand piano she purchased with a modest inheritance left by a friend of her parents’. She photocopied all of her music in a larger size so she could see it better and mounted it on manila folders. She practiced for several hours every day. When she wasn’t practicing the piano she was talking about the piano. I love pianos, too, and wrote an entire book about the life of one piano, a Steinway owned by the renowned pianist Glenn Gould. And I shared my mother’s love for her piano. During phone conversations, I listened raptly as she told me about the instrument’s cross-country adventures. Before bringing the Steinway north, my mother had mentioned that she was considering selling it. I was surprised, but instead of reminding her that, last I knew, she was setting it aside for me, I said nothing, unable to utter the simple words, “But, Mom, don’t you remember your promise?” If I did, it would be a way of asking for something, and asking my mother for something was always dangerous because of the risk of disappointment.

Ava was blessed with amazing beauty but was academically challenged. Angelina tried to give her a quick introduction to computers but was horrified at Ava’s lack of knowledge and complete failure to understand. Ava called the CD drawer the cup holder and honestly thought it was her holding her coffee or drink when typing. She thought the monitor was the telly and the mouse was the roller. She kept exiting programmes instead of closing documents and kept deleting items and forgetting to save things. Things happened Angelina’s computers that never happened before: programs failed to respond and the computer kept crashing. She typed e-mails and then printed them and put them in an envelope to post them, Angelina was speechless. She even killed a machine by constant abuse for the week. It just died the screen went blank and a message came up of fundamental hard drive failure, the monitor went black and the keyboard and mouse went dead and could not be restored. It went to the computer scrap yard, RIP. Angelina ran her out of the IT dept in their firm terrified she’d cause any more mayhem. She was the absolute blonde bombshell when it came to computers

If you have programmers, they probably save their code in Git, which is the closest I can think of to a useful blockchain-like technology: it saves individual code edits as transactions in Merkle trees with tamper-evident hashes, and developers routinely copy entire Git repositories around, identifying them by hash. It’s a distributed ledger, but for computer programs rather than money.

This is echoed by King-scott (1996, 295), who warns that unless technology-related issues are integrated into translator-training programmes, there is a real danger that the university teaching of translation may become so remote from practice that it will be marginalized and consequently be widely perceived as irrelevant to the translation task. Tha gap between technological advances and pedagogical practices must be closed.

... bright young men of disheveled appearance, often with sunken glowing eyes, can be seen sitting at computer consoles, their arms tensed and waiting to fire their fingers, already poised to strike, at the buttons and keys on which their attention seems to be riveted as a gambler’s on the rolling dice. When not so transfixed, they often sit at tables strewn with computer printouts over which they pore like possessed students of a cabbalistic text. They work until they nearly drop, twenty, thirty hours at a time. Their food, if they arrange it, is brought to them: coffee, Cokes, sandwiches. If possible, they sleep on cots near the printouts. Their rumpled clothes, their unwashed and unshaven faces, and their uncombed hair all testify that they are oblivious to their bodies and to the world in which they move. These are computer bums, compulsive programmers ...

To better understand the predicament of someone who is rational but emotionless, consider computers. Give a computer a program to run, and it will use flawless logic to execute it. But unless you give a computer a program to run, it will just sit there. Computers need a motivating force before they will do anything, and it is the job of the programmer to provide this motivating force. Damasio’s patient was like an unprogrammed computer. His

Universal computers are capable of performing all the computations permitted by the laws of physics. Once a universal computer is constructed, all you have to do is to load it with the right programme, and it can simulate any other system that is physically allowed. This includes the biosphere, with all its splendid richness of animals, plants, and microorganisms; and, in principle, it even includes your brain, together with thoughts and emotions.

Pham Nuwen spent years learning to program/explore. Programming went back to the beginning of time. It was a little like the midden out back of his father’s castle. Where the creek had worn that away, ten meters down, there were the crumpled hulks of machines—flying machines, the peasants said—from the great days of Canberra’s original colonial era. But the castle midden was clean and fresh compared to what lay within the Reprise’s local net. There were programs here that had been written five thousand years ago, before Humankind ever left Earth. The wonder of it—the horror of it, Sura said—was that unlike the useless wrecks of Canberra’s past, these programs still worked! And via a million million circuitous threads of inheritance, many of the oldest programs still ran in the bowels of the Qeng Ho system. Take the Traders’ method of timekeeping. The frame corrections were incredibly complex—and down at the very bottom of it was a little program that ran a counter. Second by second, the Qeng Ho counted from the instant that a human had first set foot on Old Earth’s moon. But if you looked at it still more closely. . .the starting instant was actually some hundred million seconds later, the 0-second of one of Humankind’s first computer operating systems. So behind all the top-level interfaces was layer under layer of support. Some of that software had been designed for wildly different situations. Every so often, the inconsistencies caused fatal accidents. Despite the romance of spaceflight, the most common accidents were simply caused by ancient, misused programs finally getting their revenge. “We should rewrite it all,” said Pham. “It’s been done,” said Sura, not looking up. She was preparing to go off-Watch, and had spent the last four days trying to root a problem out of the coldsleep automation. “It’s been tried,” corrected Bret, just back from the freezers. “But even the top levels of fleet system code are enormous. You and a thousand of your friends would have to work for a century or so to reproduce it.” Trinli grinned evilly. “And guess what—even if you did, by the time you finished, you’d have your own set of inconsistencies. And you still wouldn’t be consistent with all the applications that might be needed now and then.” Sura gave up on her debugging for the moment. “The word for all this is ‘mature programming environment.’ Basically, when hardware performance has been pushed to its final limit, and programmers have had several centuries to code, you reach a point where there is far more signicant code than can be rationalized. The best you can do is understand the overall layering, and know how to search for the oddball tool that may come in handy—take the situation I have here.” She waved at the dependency chart she had been working on. “We are low on working fluid for the coffins. Like a million other things, there was none for sale on dear old Canberra. Well, the obvious thing is to move the coffins near the aft hull, and cool by direct radiation. We don’t have the proper equipment to support this—so lately, I’ve been doing my share of archeology. It seems that five hundred years ago, a similar thing happened after an in-system war at Torma. They hacked together a temperature maintenance package that is precisely what we need.” “Almost precisely.

Alan Turing appears to be becoming a symbol of the shift towards computing, not least because of his attitude of open-minded defiance of convention and conventional thinking. Not only did he conceptualise the modern computer – imagining a simple machine that could use different programmes – but he put his thinking into practice in the great code breaking struggle with the Nazis in World War II, and followed it up with pioneering early work in the mathematics of biology and chaos.

Meanwhile, the original programmers will have left, and their replacements -- believing they understand the code -- will make some truly spectacular errors, mistakes that will suddenly make everything completely stop working for a while. So that what had seemed to be a descending curve of bugs, a fall toward the ever-receding zero, will reveal itself as the shape of another equation altogether: a line of relentlessly rising, bug-counts climbing in an endless battle against infinity.

At present, computers are spectacular at number crunching and data processing. We can code programmes that feel as though computers are interacting with us, and that's fun, but in fact they aren't interacting in a way that we expect a human being to interact. But what will happen when a programme that has self-developed, that has its own version of what we call consciousness - realises, in the human sense of the verb 'to realise', exactly what/who is on the other side of the screen?

Tom Demarco, a principal of the Atlantic Systems Guild team of consultants ... and his colleague Timothy Lister devised a study called the Coding War Games. The purpose of the games was to identify the characteristics of the best and worst computer programmers; more than six hundred developers from ninety-two different companies participated. Each designed, coded, and tested a program, working in his normal office space during business hours. Each participant was also assigned a partner from the same company. The partners worked separately, however, without any communication, a feature of the games that turned out to be critical. When the results came in, they revealed an enormous performance gap. The best outperformed the worst by a 10:1 ratio. The top programmers were also about 2.5 times better than the median. When DeMarco and Lister tried to figure out what accounted for this astonishing range, the factors that you'd think would matter — such as years of experience, salary, even the time spent completing the work — had little correlation to outcome. Programmers with 10 years' experience did no better than those with two years. The half who performed above the median earned less than 10 percent more than the half below — even though they were almost twice as good. The programmers who turned in "zero-defect" work took slightly less, not more, time to complete the exercise than those who made mistakes. It was a mystery with one intriguing clue: programmers from the same companies performed at more or less the same level, even though they hadn't worked together. That's because top performers overwhelmingly worked for companies that gave their workers the most privacy, personal space, control over their physical environments, and freedom from interruption. Sixty-two percent of the best performers said that their workspace was acceptably private, compared to only 19 percent of the worst performers; 76 percent of the worst performers but only 38 percent of the top performers said that people often interrupted them needlessly.

If a model did anything too obviously bizarre—flooded the Sahara or tripled interest rates—the programmers would revise the equations to bring the output back in line with expectation. In practice, econometric models proved dismally blind to what the future would bring, but many people who should have known better acted as though they believed in the results. Forecasts of economic growth or unemployment were put forward with an implied precision of two or three decimal places. Governments and financial institutions paid for such predictions and acted on them, perhaps out of necessity or for want of anything better. Presumably they knew that such variables as “consumer optimism” were not as nicely measurable as “humidity” and that the perfect differential equations had not yet been written for the movement of politics and fashion. But few realized how fragile was the very process of modeling flows on computers, even when the data was reasonably trustworthy and the laws were purely physical, as in weather forecasting.

forward to it, and Cooper, coatless and chilly in the desert evening, was thinking that the radio man was an asshole. He’d chased Vasquez for nine days now. Someone had warned the programmer just before Cooper got to the Boston walk-up, a brick rectangle where the only light had been a window onto an airshaft and the glowing red eyes of power indicators on computers and routers and surge protectors. The desk chair had been against the far wall as if someone had leaped out of it, and steam still rose from an abandoned bowl of ramen. Vasquez had run, and

It was thus that in the second half of 1969—amid the static of Woodstock, Chappaquiddick, Vietnam War protests, Charles Manson, the Chicago Eight trial, and Altamont—the culmination was reached for three historic enterprises, each in the making for almost a decade. NASA was able to send a man to the moon. Engineers in Silicon Valley were able to devise a way to put a programmable computer on a chip called a microprocessor. And ARPA created a network that could connect distant computers. Only the first of these (perhaps the least historically significant of them?) made headlines. THE

Think of the many articles one can find every year in the Wall Street Journal describing some entrepreneur or businessman as being a "pioneer" or a "maverick" or a "cowboy." Think of the many times these ambitious modern men are described as "staking their claim" or boldly pushing themselves "beyond the frontier" or even "riding into the sunset." We still use this nineteenth-century lexicon to describe our boldest citizens, but it's really a code now, because these guys aren't actually pioneers; they are talented computer programmers, biogenetic researchers, politicians, or media monguls making a big splash in a fast modern economy. But when Eustace Conway talks about staking a claim, the guy is literally staking a goddamn claim. Other frontier expressions that the rest of us use as metaphors, Eustace uses literally. He does sit tall in the saddle; he does keep his powder dry; he is carving out a homestead. When he talks about reining in horses or calling off the dogs or mending fences, you can be sure that there are real horses, real dogs or real fences in the picture. And when Eustace goes in for the kill, he's not talking about a hostile takeover of a rival company; he's talking about really killing something.

Rust’s central feature is ownership. Although the feature is straightforward to explain, it has deep implications for the rest of the language. All programs have to manage the way they use a computer’s memory while running. Some languages have garbage collection that constantly looks for no longer used memory as the program runs; in other languages, the programmer must explicitly allocate and free the memory. Rust uses a third approach: memory is managed through a system of ownership with a set of rules that the compiler checks at compile time. None of the ownership features slow down your program while it’s running.

After the huge push for CES, it was time for Amiga to sort a few things out. First, the Amiga systems engineers began producing 100 Lorraine developer systems to hand out to companies like Activision, Electronic Arts, Infocom, and Microsoft. At the time, Commodore programmer Andy Finkel was helping Infocom in Cambridge to port its games to the C64. “That was where I first got a hint of the Amiga,” says Finkel. “There was this locked room where I couldn’t go, even though I could go anywhere else in the building. The Infocom tech people would sneak in and work on the computer. They told me there was a secret computer that they couldn’t talk about.

When Amabile analyzed the data, she came to a clear conclusion about one key factor: workers are happiest—and most motivated—when they feel that they accomplish something meaningful at work. These accomplishments do not need to be major breakthroughs: incremental but noticeable progress toward a goal was enough to make her subjects feel good. As one programmer described it, “I smashed that [computer] bug that’s been frustrating me for almost a calendar week. That may not be an event to you, but I live a very drab life, so I’m all hyped.”1 The lesson here is that managers can get the most out of their employees by helping them achieve meaningful progress every day.

By failing to make the obvious connection between an openly misogynistic culture and the mysterious lack of women, Levy contributed to the myth of innately talented hackers being implicitly male. And, today, it’s hard to think of a profession more in thrall to brilliance bias than computer science. ‘Where are the girls that love to program?’ asked a high-school teacher who took part in a summer programme for advanced-placement computer-science teachers at Carnegie Mellon; ‘I have any number of boys who really really love computers,’ he mused. ‘Several parents have told me their sons would be on the computer programming all night if they could. I have yet to run into a girl like that.’ This may be true, but as one of his fellow teachers pointed out, failing to exhibit this behaviour doesn’t mean that his female students don’t love computer science. Recalling her own student experience, she explained how she ‘fell in love’ with programming when she took her first course in college. But she didn’t stay up all night, or even spend a majority of her time programming. ‘Staying up all night doing something is a sign of single-mindedness and possibly immaturity as well as love for the subject. The girls may show their love for computers and computer science very differently. If you are looking for this type of obsessive behavior, then you are looking for a typically young, male behavior. While some girls will exhibit it, most won’t.

Tiredness thus draws whole families into the vicious circle of poor nutrition and lack of exercise. The sluggishness that comes from poor diet feeds further exhaustion, which leads to more quick-fix junk food and telly-slumping … and so on, ad infinitum. And all this overlaps with another vicious circle. This is the one where exhausted parents attempt wanly to convince their children it’s bedtime. And the children - over-tired and brattish - play up more and more, until their parents give up the unequal struggle and let them watch ‘one more programme’ or play ‘one more computer game’. The next morning everyone wakes up tired again … and on it goes, the two vicious circles overlapping into a vicious Venn diagram, with a worn-out family trapped in the middle.

So which theory did Lagos believe in? The relativist or the universalist?" "He did not seem to think there was much of a difference. In the end, they are both somewhat mystical. Lagos believed that both schools of thought had essentially arrived at the same place by different lines of reasoning." "But it seems to me there is a key difference," Hiro says. "The universalists think that we are determined by the prepatterned structure of our brains -- the pathways in the cortex. The relativists don't believe that we have any limits." "Lagos modified the strict Chomskyan theory by supposing that learning a language is like blowing code into PROMs -- an analogy that I cannot interpret." "The analogy is clear. PROMs are Programmable Read-Only Memory chips," Hiro says. "When they come from the factory, they have no content. Once and only once, you can place information into those chips and then freeze it -- the information, the software, becomes frozen into the chip -- it transmutes into hardware. After you have blown the code into the PROMs, you can read it out, but you can't write to them anymore. So Lagos was trying to say that the newborn human brain has no structure -- as the relativists would have it -- and that as the child learns a language, the developing brain structures itself accordingly, the language gets 'blown into the hardware and becomes a permanent part of the brain's deep structure -- as the universalists would have it." "Yes. This was his interpretation." "Okay. So when he talked about Enki being a real person with magical powers, what he meant was that Enki somehow understood the connection between language and the brain, knew how to manipulate it. The same way that a hacker, knowing the secrets of a computer system, can write code to control it -- digital namshubs?" "Lagos said that Enki had the ability to ascend into the universe of language and see it before his eyes. Much as humans go into the Metaverse. That gave him power to create nam-shubs. And nam-shubs had the power to alter the functioning of the brain and of the body." "Why isn't anyone doing this kind of thing nowadays? Why aren't there any namshubs in English?" "Not all languages are the same, as Steiner points out. Some languages are better at metaphor than others. Hebrew, Aramaic, Greek, and Chinese lend themselves to word play and have achieved a lasting grip on reality: Palestine had Qiryat Sefer, the 'City of the Letter,' and Syria had Byblos, the 'Town of the Book.' By contrast other civilizations seem 'speechless' or at least, as may have been the case in Egypt, not entirely cognizant of the creative and transformational powers of language. Lagos believed that Sumerian was an extraordinarily powerful language -- at least it was in Sumer five thousand years ago." "A language that lent itself to Enki's neurolinguistic hacking." "Early linguists, as well as the Kabbalists, believed in a fictional language called the tongue of Eden, the language of Adam. It enabled all men to understand each other, to communicate without misunderstanding. It was the language of the Logos, the moment when God created the world by speaking a word. In the tongue of Eden, naming a thing was the same as creating it. To quote Steiner again, 'Our speech interposes itself between apprehension and truth like a dusty pane or warped mirror. The tongue of Eden was like a flawless glass; a light of total understanding streamed through it. Thus Babel was a second Fall.' And Isaac the Blind, an early Kabbalist, said that, to quote Gershom Scholem's translation, 'The speech of men is connected with divine speech and all language whether heavenly or human derives from one source: the Divine Name.' The practical Kabbalists, the sorcerers, bore the title Ba'al Shem, meaning 'master of the divine name.'" "The machine language of the world," Hiro says.

Why is programming fun? What delights may its practitioner expect as his reward? First is the sheer joy of making things. As the child delights in his first mud pie, so the adult enjoys building things, especially things of his own design. I think this delight must be an image of God’s delight in making things, a delight shown in the distinctness and newness of each leaf and each snowflake. Second is the pleasure of making things that are useful to other people. Deep within, we want others to use our work and to find it helpful. In this respect the programming system is not essentially different from the child’s first clay pencil holder “for Daddy’s office.” Third is the fascination of fashioning complex puzzle-like objects of interlocking moving parts and watching them work in subtle cycles, playing out the consequences of principles built in from the beginning. The programmed computer has all the fascination of the pinball machine or the jukebox mechanism, carried to the ultimate. Fourth is the joy of always learning, which springs from the nonrepeating nature of the task. In one way or another the problem is ever new, and its solver learns something; sometimes practical, sometimes theoretical, and sometimes both. Finally, there is the delight of working in such a tractable medium. The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures. (As we shall see later, this very tractability has its own problems.) Yet the program construct, unlike the poet’s words, is real in the sense that it moves and works, producing visible outputs separate from the construct itself. It prints results, draws pictures, produces sounds, moves arms. The magic of myth and legend has come true in our time. One types the correct incantation on a keyboard and a display screen comes to life, showing things that never were nor could be. Programming then is fun because it gratifies creative longings built deep within us and delights sensibilities we have in common with all men.

I WANT TO end this list by talking a little more about the founding of Pixar University and Elyse Klaidman’s mind-expanding drawing classes in particular. Those first classes were such a success—of the 120 people who worked at Pixar then, 100 enrolled—that we gradually began expanding P.U.’s curriculum. Sculpting, painting, acting, meditation, belly dancing, live-action filmmaking, computer programming, design and color theory, ballet—over the years, we have offered free classes in all of them. This meant spending not only the time to find the best outside teachers but also the real cost of freeing people up during their workday to take the classes. So what exactly was Pixar getting out of all of this? It wasn’t that the class material directly enhanced our employees’ job performance. Instead, there was something about an apprentice lighting technician sitting alongside an experienced animator, who in turn was sitting next to someone who worked in legal or accounting or security—that proved immensely valuable. In the classroom setting, people interacted in a way they didn’t in the workplace. They felt free to be goofy, relaxed, open, vulnerable. Hierarchy did not apply, and as a result, communication thrived. Simply by providing an excuse for us all to toil side by side, humbled by the challenge of sketching a self-portrait or writing computer code or taming a lump of clay, P.U. changed the culture for the better. It taught everyone at Pixar, no matter their title, to respect the work that their colleagues did. And it made us all beginners again. Creativity involves missteps and imperfections. I wanted our people to get comfortable with that idea—that both the organization and its members should be willing, at times, to operate on the edge. I can understand that the leaders of many companies might wonder whether or not such classes would truly be useful, worth the expense. And I’ll admit that these social interactions I describe were an unexpected benefit. But the purpose of P.U. was never to turn programmers into artists or artists into belly dancers. Instead, it was to send a signal about how important it is for every one of us to keep learning new things. That, too, is a key part of remaining flexible: keeping our brains nimble by pushing ourselves to try things we haven’t tried before. That’s what P.U. lets our people do, and I believe it makes us stronger.

a harbinger of a third wave of computing, one that blurred the line between augmented human intelligence and artificial intelligence. “The first generation of computers were machines that counted and tabulated,” Rometty says, harking back to IBM’s roots in Herman Hollerith’s punch-card tabulators used for the 1890 census. “The second generation involved programmable machines that used the von Neumann architecture. You had to tell them what to do.” Beginning with Ada Lovelace, people wrote algorithms that instructed these computers, step by step, how to perform tasks. “Because of the proliferation of data,” Rometty adds, “there is no choice but to have a third generation, which are systems that are not programmed, they learn.”27 But even as this occurs, the process could remain one of partnership and symbiosis with humans rather than one designed to relegate humans to the dustbin of history. Larry Norton, a breast cancer specialist at New York’s Memorial Sloan-Kettering Cancer Center, was part of the team that worked with Watson. “Computer science is going to evolve rapidly, and medicine will evolve with it,” he said. “This is coevolution. We’ll help each other.”28 This belief that machines and humans will get smarter together is a process that Doug Engelbart called “bootstrapping” and “coevolution.”29 It raises an interesting prospect: perhaps no matter how fast computers progress, artificial intelligence may never outstrip the intelligence of the human-machine partnership. Let us assume, for example, that a machine someday exhibits all of the mental capabilities of a human: giving the outward appearance of recognizing patterns, perceiving emotions, appreciating beauty, creating art, having desires, forming moral values, and pursuing goals. Such a machine might be able to pass a Turing Test. It might even pass what we could call the Ada Test, which is that it could appear to “originate” its own thoughts that go beyond what we humans program it to do. There would, however, be still another hurdle before we could say that artificial intelligence has triumphed over augmented intelligence. We can call it the Licklider Test. It would go beyond asking whether a machine could replicate all the components of human intelligence to ask whether the machine accomplishes these tasks better when whirring away completely on its own or when working in conjunction with humans. In other words, is it possible that humans and machines working in partnership will be indefinitely more powerful than an artificial intelligence machine working alone?

Chapter One Vivek Ranadivé “IT WAS REALLY RANDOM. I MEAN, MY FATHER HAD NEVER PLAYED BASKETBALL BEFORE.” 1. When Vivek Ranadivé decided to coach his daughter Anjali’s basketball team, he settled on two principles. The first was that he would never raise his voice. This was National Junior Basketball—the Little League of basketball. The team was made up mostly of twelve-year-olds, and twelve-year-olds, he knew from experience, did not respond well to shouting. He would conduct business on the basketball court, he decided, the same way he conducted business at his software firm. He would speak calmly and softly, and he would persuade the girls of the wisdom of his approach with appeals to reason and common sense. The second principle was more important. Ranadivé was puzzled by the way Americans play basketball. He is from Mumbai. He grew up with cricket and soccer. He would never forget the first time he saw a basketball game. He thought it was mindless. Team A would score and then immediately retreat to its own end of the court. Team B would pass the ball in from the sidelines and dribble it into Team A’s end, where Team A was patiently waiting. Then the process would reverse itself. A regulation basketball court is ninety-four feet long. Most of the time, a team would defend only about twenty-four feet of that, conceding the other seventy feet. Occasionally teams played a full-court press—that is, they contested their opponent’s attempt to advance the ball up the court. But they did it for only a few minutes at a time. It was as if there were a kind of conspiracy in the basketball world about the way the game ought to be played, Ranadivé thought, and that conspiracy had the effect of widening the gap between good teams and weak teams. Good teams, after all, had players who were tall and could dribble and shoot well; they could crisply execute their carefully prepared plays in their opponent’s end. Why, then, did weak teams play in a way that made it easy for good teams to do the very things that they were so good at? Ranadivé looked at his girls. Morgan and Julia were serious basketball players. But Nicky, Angela, Dani, Holly, Annika, and his own daughter, Anjali, had never played the game before. They weren’t all that tall. They couldn’t shoot. They weren’t particularly adept at dribbling. They were not the sort who played pickup games at the playground every evening. Ranadivé lives in Menlo Park, in the heart of California’s Silicon Valley. His team was made up of, as Ranadivé put it, “little blond girls.” These were the daughters of nerds and computer programmers. They worked on science projects and read long and complicated books and dreamed about growing up to be marine biologists. Ranadivé knew that if they played the conventional way—if they let their opponents dribble the ball up the court without opposition—they would almost certainly lose to the girls for whom basketball was a passion. Ranadivé had come to America as a seventeen-year-old with fifty dollars in his pocket. He was not one to accept losing easily. His second principle, then, was that his team would play a real full-court press—every game, all the time. The team ended up at the national championships. “It was really random,” Anjali Ranadivé said. “I mean, my father had never played basketball before.” 2. Suppose you were to total up all the wars over the past two hundred years that occurred between very large and very small countries. Let’s say that one side has to be at least ten times larger in population and armed might

Computers speak machine language," Hiro says. "It's written in ones and zeroes -- binary code. At the lowest level, all computers are programmed with strings of ones and zeroes. When you program in machine language, you are controlling the computer at its brainstem, the root of its existence. It's the tongue of Eden. But it's very difficult to work in machine language because you go crazy after a while, working at such a minute level. So a whole Babel of computer languages has been created for programmers: FORTRAN, BASIC, COBOL, LISP, Pascal, C, PROLOG, FORTH. You talk to the computer in one of these languages, and a piece of software called a compiler converts it into machine language. But you never can tell exactly what the compiler is doing. It doesn't always come out the way you want. Like a dusty pane or warped mirror. A really advanced hacker comes to understand the true inner workings of the machine -- he sees through the language he's working in and glimpses the secret functioning of the binary code -- becomes a Ba'al Shem of sorts." "Lagos believed that the legends about the tongue of Eden were exaggerated versions of true events," the Librarian says. "These legends reflected nostalgia for a time when people spoke Sumerian, a tongue that was superior to anything that came afterward." "Is Sumerian really that good?" "Not as far as modern-day linguists can tell," the Librarian says. "As I mentioned, it is largely impossible for us to grasp. Lagos suspected that words worked differently in those days. If one's native tongue influences the physical structure of the developing brain, then it is fair to say that the Sumerians -- who spoke a language radically different from anything in existence today -- had fundamentally different brains from yours. Lagos believed that for this reason, Sumerian was a language ideally suited to the creation and propagation of viruses. That a virus, once released into Sumer, would spread rapidly and virulently, until it had infected everyone." "Maybe Enki knew that also," Hiro says. "Maybe the nam-shub of Enki wasn't such a bad thing. Maybe Babel was the best thing that ever happened to us.

Man’s destiny was to conquer and rule the world, and this is what he’s done — almost. He hasn’t quite made it, and it looks as though this may be his undoing. The problem is that man’s conquest of the world has itself devastated the world. And in spite of all the mastery we’ve attained, we don’t have enough mastery to stop devastating the world — or to repair the devastation we’ve already wrought. We’ve poured our poisons into the world as though it were a bottomless pit — and we go on pouring our poisons into the world. We’ve gobbled up irreplaceable resources as though they could never run out — and we go on gobbling them up. It’s hard to imagine how the world could survive another century of this abuse, but nobody’s really doing anything about it. It’s a problem our children will have to solve, or their children. Only one thing can save us. We have to increase our mastery of the world. All this damage has come about through our conquest of the world, but we have to go on conquering it until our rule is absolute. Then, when we’re in complete control, everything will be fine. We’ll have fusion power. No pollution. We’ll turn the rain on and off. We’ll grow a bushel of wheat in a square centimeter. We’ll turn the oceans into farms. We’ll control the weather — no more hurricanes, no more tornadoes, no more droughts, no more untimely frosts. We’ll make the clouds release their water over the land instead of dumping it uselessly into the oceans. All the life processes of this planet will be where they belong—where the gods meant them to be—in our hands. And we’ll manipulate them the way a programmer manipulates a computer. And that’s where it stands right now. We have to carry the conquest forward. And carrying it forward is either going to destroy the world or turn it into a paradise — into the paradise it was meant to be under human rule. And if we manage to do this — if we finally manage to make ourselves the absolute rulers of the world — then nothing can stop us. Then we move into the Star Trek era. Man moves out into space to conquer and rule the entire universe. And that may be the ultimate destiny of man: to conquer and rule the entire universe. That’s how wonderful man is.