Software Quotes

Quotes tagged as "software" Showing 1-30 of 78
Robert M. Pirsig
“The test of the machine is the satisfaction it gives you. There isn't any other test. If the machine produces tranquility it's right. If it disturbs you it's wrong until either the machine or your mind is changed.”
Robert M. Pirsig, Zen and the Art of Motorcycle Maintenance: An Inquiry Into Values

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

Joseph Weizenbaum
“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.”
Joseph Weizenbaum

Robert C. Martin
“It is not enough for code to work.”
Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

Charles Yu
“Sometimes at night I worry about TAMMY. I worry that she might get tired of it all. Tired of running at sixty-six terahertz, tired of all those processing cycles, every second of every hour of every day. I worry that one of these cycles she might just halt her own subroutine and commit software suicide. And then I would have to do an error report, and I don't know how I would even begin to explain that to Microsoft.”
Charles Yu, How to Live Safely in a Science Fictional Universe

Eliyahu M. Goldratt
“More importantly, our software worked. I don't just mean that it didn't bump, or that it performed according to the written specifications, or that it was efficient in producing reports. It really worked”
Eliyahu M. Goldratt, The Goal: A Process of Ongoing Improvement

Sercan Leylek
“If it's not written, it never happened. If it is written, it doesn't matter what happened.”
Sercan Leylek

Jason Farman
“Similarly, the computers used to run the software on the ground for the mission were borrowed from a previous mission. These machines were so out of date that Bowman had to shop on eBay to find replacement parts to get the machines working. As systems have gone obsolete, JPL no longer uses the software, but Bowman told me that the people on her team continue to use software built by JPL in the 1990s, because they are familiar with it. She said, “Instead of upgrading to the next thing we decided that it was working just fine for us and we would stay on the platform.” They have developed so much over such a long period of time with the old software that they don’t want to switch to a newer system. They must adapt to using these outdated systems for the latest scientific work.
Working within these constraints may seem limiting. However, building tools with specific constraints—from outdated technologies and low bitrate radio antennas—can enlighten us. For example, as scientists started to explore what they could learn from the wait times while communicating with deep space probes, they discovered that the time lag was extraordinarily useful information. Wait times, they realized, constitute an essential component for locating a probe in space, calculating its trajectory, and accurately locating a target like Pluto in space. There is no GPS for spacecraft (they aren’t on the globe, after all), so scientists had to find a way to locate the spacecraft in the vast expanse. Before 1960, the location of planets and objects in deep space was established through astronomical observation, placing an object like Pluto against a background of stars to determine its position.15 In 1961, an experiment at the Goldstone Deep Space Communications Complex in California used radar to more accurately define an “astronomical unit” and help measure distances in space much more accurately.16 NASA used this new data as part of creating the trajectories for missions in the following years. Using the data from radio signals across a wide range of missions over the decades, the Deep Space Network maintained an ongoing database that helped further refine the definition of an astronomical unit—a kind of longitudinal study of space distances that now allows missions like New Horizons to create accurate flight trajectories.
The Deep Space Network continued to find inventive ways of using the time lag of radio waves to locate objects in space, ultimately finding that certain ways of waiting for a downlink signal from the spacecraft were less accurate than others. It turned to using the antennas from multiple locations, such as Goldstone in California and the antennas in Canberra, Australia, or Madrid, Spain, to time how long the signal took to hit these different locations on Earth. The time it takes to receive these signals from the spacecraft works as a way to locate the probes as they are journeying to their destination. Latency—or the different time lag of receiving radio signals on different locations of Earth—is the key way that deep space objects are located as they journey through space. This discovery was made possible during the wait times for communicating with these craft alongside the decades of data gathered from each space mission. Without the constraint of waiting, the notion of using time as a locating feature wouldn’t have been possible.”
Jason Farman, Delayed Response: The Art of Waiting from the Ancient to the Instant World

“Software is eating the world, so we need software developers. But it is less clear what we will need when software finishes its meal and settles down to digest. What happens when robots learn to program themselves?”
Joseph E. Aoun, Robot-Proof: Higher Education in the Age of Artificial Intelligence

Nipun Varma
“India is the only country wherein the total number of engineers exceeds the number of vehicles on the road.”
Nipun Varma, Adventures of an Indian Techie

Nipun Varma
“Developer is the one who creates bugs/defects mostly and working code rarely”
Nipun Varma, Adventures of an Indian Techie

“Hope the English literature will invent a few more alphabets to avoid plagiarism. The permutation and combination of 26 alphabets even a human calculator can do, no need for plagiarism software”
Dr.P.S. Jagadeesh Kumar

Steven Magee
“When one of the workers suggested they could automate some of the manager’s job with software they could easily develop, they were instructed not to do so.”
Steven Magee

Steven Magee
“In the era of surveillance of the masses, I like to use phrases like terrorists, assassinate, bomb, explosions, attack, weapons of mass destruction, and so on in my on-line activities to screw up the automated government surveillance software.”
Steven Magee

Satya Nadella
“I do have a bias for which I am unapologetic... for driving investment toward technological advancements... that help people create, connect, and become more productive rather than software that is simply entertaining—memes for conspicuous consumption. Spillover effects on the economy are pretty limited for technologies that don't foster a more equitable ratio of consumption to creation.”
Satya Nadella, Hit Refresh

Ellen Ullman
“You mean you don't stage the software?" I asked him. "You don't test it?"
"Why should we? Everything we do is live all the time, always new, minute by minute.This is the Web! Code it, post it, run it, change it, run it again.”
Ellen Ullman, The Bug

“Two examples illustrate the redundancy principle. First, when a virtual machine fails in a cloud-based system, an identical instance is started automatically. Second, a critically important system should have at least one secondary backup system that runs in parallel with the primary system to ensure a safe fallback. Leading up to the next principle, we note that the secondary system should differ from the primary system to avoid both failing for the same reasons.”
Kjell Jorgen Hole, Anti-Fragile ICT Systems

Amit Kalantri
“Software testing is not only ensuring absence of bugs but also ensuring presence of value.”
Amit Kalantri

Jean Baudrillard
“We are threatened not just by memory loss, but by the routing of the synapses by the filterable viruses of memory. The strange disappearance of names, faces and places seems like a programmed erasure, like the imperceptible advance of a virus which, after infecting the artificial memories of computers, is now attacking natural memories. Might there not be a conspiracy of software?”
Jean Baudrillard, Fragments

“Tech ICS is a highly professional UK based software company started in the UK in 2006 running another branch in Sylhet, Bangladesh since 2018 providing services including software & web application development and e-commerce development. It has gained a huge amount of popularity in the UK as well as in Bangladesh." TechICS is a multi-award-winning website design and digital marketing company recognized as the ‘go to’ company for high-end website design, development and tactical digital marketing campaigns. We know how hard it is to choose from the thousands of companies offering design services, but we guarantee you’ll notice a difference working with TechICS.”
Abdul Kadir

“I may not be big, but my heart is”
Sunny Menon

Misha Glenny
“Many of the criminal skills on the Web have emerged from an essential division in the philosophical debate generated by the Internet.

In simple terms the debate is between those, on the one hand, who believe its commercial role is paramount and those, on the other, who argue that it is in the first instance a social and intellectual tool, whose very nature changes the fundamental moral code of mass communication. For the former, any copying of computer ‘code’ (shorthand for the computer language in which software or a program is written) that is not explicitly sanctioned is regarded as a criminal violation. The latter, however, are convinced that by releasing software you are also relinquishing copyright.”
Misha Glenny, DarkMarket: Cyberthieves, Cybercops and You

“Clean code always looks like it was written by someone who cares”
Michael Feathers

“Regular expressions are widely used for string matching. Although regular-expression systems are derived from a perfectly good mathematical formalism, the particular choices made by implementers to expand the formalism into useful software systems are often disastrous: the quotation conventions adopted are highly irregular; the egregious misuse of parentheses, both for grouping and for backward reference, is a miracle to behold. In addition, attempts to increase the expressive power and address shortcomings of earlier designs have led to a proliferation of incompatible derivative languages.”
Chris Hanson, Software Design for Flexibility: How to Avoid Programming Yourself Into a Corner

“So the syntax of the regular-expression language is awful; there are various incompatible forms of the language; and the quotation conventions are baroquen [sic]. While regular expression languages are domain-specific languages, they are bad ones. Part of the value of examining regular expressions is to experience how bad things can be.”
Chris Hanson, Software Design for Flexibility: How to Avoid Programming Yourself Into a Corner

Joel Spolsky
“The Joel Test

1. Do you use source control?
2. Can you make a build in one step?
3. Do you make daily builds?
4. Do you have a bug database?
5. Do you fix bugs before writing new code?
6. Do you have an up-to-date schedule?
7. Do you have a spec?
8. Do programmers have quiet working conditions?
9. Do you use the best tools money can buy?
10. Do you have testers?
11. Do new candidates write code during their interview?
12. Do you do hallway usability testing?”
Joel Spolsky, Joel on Software

Joel Spolsky
“In general, the longer you wait before fixing a bug, the costlier (in time and money) it is to fix.”
Joel Spolsky, Joel on Software

Joel Spolsky
“Programmers and software engineers who dive into code without writing a spec tend to think they're cool gunslingers, shooting from the hip. They're not. They are terribly unproductive. They write bad code and produce shoddy software, and they threaten their projects by taking giant risks which are completely uncalled for.”
Joel Spolsky, Joel on Software

Joel Spolsky
“Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think this kind of motivation is brain-dead. When I'm behind schedule, I feel doomed and depressed and unmotivated. When I'm working ahead of schedule, I'm cheerful and productive. The schedule is not the place to play psychological games.”
Joel Spolsky, Joel on Software

Joel Spolsky
“The confidence you get from knowing about every crash, anywhere in the world, is crucial to delivering a high-quality product that needs to be used in the wild. In the consumer software business, you can't rely on your customers to tell you about crashes—many of them may not be technical enough, and most of them won't bother to take time off of their own important work to give you a useful crash report unless you make it completely automatic.”
Joel Spolsky, Joel on Software

« previous 1 3