Created
September 27, 2021 20:32
-
-
Save scottashipp/f6a5a83a444a8ad5a90a9c907ce9cc0d to your computer and use it in GitHub Desktop.
Run strfile on this file to make it usable with fortune. Then just run fortune software-quotes to retrieve a random quote.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fools ignore complexity; pragmatists suffer it; experts avoid it; | |
geniuses remove it. | |
Alan Perlis | |
% | |
People think that computer science is the art of geniuses but the | |
actual reality is the opposite, just many people doing things | |
that build on eachother, like a wall of mini stones. | |
Donald Knuth | |
% | |
Engineers like to solve problems. If there are no problems handily available, | |
then they will create their own problems. | |
Scott Adams | |
% | |
Always code as if the guy who ends up maintaining your code will be a violent | |
psychopath who knows where you live. | |
Martin Golding | |
% | |
First, solve the problem. Then, write the code. | |
John Johnson | |
% | |
The competent programmer is fully aware of the limited size of his own skull. | |
He therefore approaches his task with full humility, and avoids clever tricks | |
like the plague. | |
Edsger Dijkstra | |
% | |
Any fool can write code that a computer can understand. Good programmers write | |
code that humans can understand. | |
Martin Fowler | |
% | |
Organizations which design systems are constrained to produce designs which are | |
copies of the communication structures of these organizations. | |
Melvin Conway | |
% | |
Simplicity does not precede complexity, but follows it. | |
Alan Perlis | |
% | |
Don't make the user provide information that the system already knows. | |
Rick Lemons | |
% | |
Simplicity is prerequisite for reliability. | |
Edsger W. Dijkstra | |
% | |
If you can't deploy your services independently then they aren't microservices. | |
Daniel Bryant | |
% | |
The Twelve Factors | |
Factor 1: Codebase | |
One codebase tracked in revision control, many deploys | |
% | |
The Twelve Factors | |
Factor 2: Dependencies | |
Explicitly declare and isolate dependencies | |
% | |
The Twelve Factors | |
Factor 3: Config | |
Store config in the environment | |
% | |
The Twelve Factors | |
Factor 4: Backing services | |
Treat backing services as attached resources | |
% | |
The Twelve Factors | |
Factor 5: Build, release, run | |
Strictly separate build and run stages | |
% | |
The Twelve Factors | |
Factor 6: Processes | |
Execute the app as one or more stateless processes | |
% | |
The Twelve Factors | |
Factor 7: Port binding | |
Export services via port binding | |
% | |
The Twelve Factors | |
Factor 8: Concurrency | |
Scale out via the process model | |
% | |
The Twelve Factors | |
Factor 9: Disposability | |
Maximize robustness with fast startup and graceful shutdown | |
% | |
The Twelve Factors | |
Factor 10: Dev/prod parity | |
Keep development, staging, and production as similar as possible | |
% | |
The Twelve Factors | |
Factor 11: Logs | |
Treat logs as event streams | |
% | |
The Twelve Factors | |
Factor 12: Admin processes | |
Run admin/management tasks as one-off processes | |
% | |
At Google, one of our favorite mottoes is "Failure is an option." It's widely | |
recognized that if you're not failing now and then, you're not being innovative | |
enough or taking enough risks. | |
Brian W. Fitzpatrick | |
Debugging Teams | |
% | |
Code is like humor. When you have to explain it, it's bad. | |
Cory House | |
% | |
Design is choosing how you will fail. | |
Ron Fein | |
% | |
The first 90 percent of the code accounts for the first 90 percent of the | |
development time...The remaining 10 percent of the code accounts for the other | |
90 percent of the development time. | |
Tom Cargill | |
% | |
Program testing can be used to show the presence of bugs, but never to show | |
their absence! | |
Edsger Dijkstra | |
% | |
The belief that complex systems require armies of designers and programmers is | |
wrong. A system that is not understood in its entirety, or at least to a | |
significant degree of detail by a single individual, should probably not be | |
built. | |
Niklaus Wirth | |
% | |
Perfection (in design) is achieved not when there is nothing more to add, but | |
rather when there is nothing more to take away. | |
Antoine de Saint-Exupery | |
% | |
Let us change our traditional attitude to the construction of programs. Instead | |
of imagining that our main task is to instruct a computer what to to, let us | |
concentrate rather on explaining to human beings what we want a computer to | |
do. | |
Donald Knuth | |
% | |
Design and programming are human activities; forget that and all is lost. | |
Bjarne Stroustrup | |
% | |
Before software can be reusable it first has to be usable. | |
Ralph Johnson | |
% | |
The price of reliability is the pursuit of the utmost simplicity. It is a price | |
which the very rich may find hard to pay. | |
C.A.R. Hoare | |
% | |
Premature optimization is the root of all evil in programming. | |
C.A.R. Hoare | |
% | |
There are two ways of constructing a software design: One way is to make it so | |
simple that there are obviously no deficiencies, and the other way is to make | |
it so complicated that there are no obvious deficiencies. The first method is | |
far more difficult. | |
C.A.R. Hoare | |
% | |
Inside every large program, there is a small program trying to get out. | |
C.A.R. Hoare | |
% | |
The goal of Computer Science is to build something that will last at least | |
until we've finished building it. | |
Anonymous | |
% | |
Simple things should be simple, complex things should be possible. | |
Bo Leuf, Ward Cunningham | |
The Wiki Way: Quick Collaboration on the Web | |
% | |
A good way to stay flexible is to write less code. | |
Andrew Hunt, David Thomas | |
Pragmatic Programmer | |
% | |
Correctness is clearly the prime quality. If a system does not do what it is | |
supposed to do, then everything else about it matters little. | |
Bertrand Meyer | |
% | |
When debugging, novices insert corrective code; experts remove defective code. | |
Richard Pattis | |
% | |
Hiring people to write code to sell is not the same as hiring people to design | |
and build durable, usable, dependable software. | |
Larry Constantine | |
% | |
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. | |
Fred Brooks | |
% | |
The purpose of software engineering is to control complexity, not to create it. | |
Pamela Zave | |
% | |
Complexity kills. It sucks the life out of developers, it makes products | |
difficult to plan, build and test, it introduces security challenges, and it | |
causes end-user and administrator frustration. | |
Ray Ozzie | |
% | |
A designer knows that he has achieved perfection not when there is nothing left | |
to add, but when there is nothing left to take away. | |
Antoine de Saint-Exupery | |
% | |
Simplicity and elegance are unpopular because they require hard work and | |
discipline to achieve and education to be appreciated. | |
Edsger W. Dijkstra | |
% | |
The future is already here – it's just not evenly distributed. | |
William Gibson | |
% | |
I call it my billion-dollar mistake. It was the invention of the null reference | |
in 1965 ... This has led to innumerable errors, vulnerabilities, and system | |
crashes, which have probably caused a billion dollars of pain and damage in the | |
last forty years. | |
C.A.R. Hoare | |
% | |
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. | |
Donald Knuth |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment