Inspiring quotes about software engineering which I practice and follow

Quotes for Team & Leadership

1. When somebody begins a sentence with “IT WOULD BE NICE IF..” the right thing to do is to wait politely for the speaker to finish. No project ever gets around to the it-would-be-nice features: or if they do, they regret it. Wait for sentences that begin “WE HAVE TO..” and pay close attention, and see if you agree. - Tom Van Vleck
2. Simple things should be simple, complex things should be POSSIBLE.
3. A team of highly competent programmers who are also highly territorial, egotistical politicians will fail while a team of equally competent programmers, who are also egoless, cooperative, team players will succeed. - Daniel M. Berry
4. In high-performance teams, the leaders managed the principles, and the principles managed the team. - Jim Highsmith
5. As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications. - Dave Parnas
6. The best meetings get real work done. When your people learn that your meetings actually accomplish something, they will stop making excuses to be elsewhere.
7. The manager’s function is not to make people work, but to make it possible for people to work.
8. Punishment demotivates when it comes from people rather than a system of well-defined rules.
9. The conclusion is simple: if a 200-man project has 25 managers who are the most competent and experienced programmers, fire the 175 troops and put the managers back to programming. - Frederick Brooks

Quotes for Tester

1. It is far better to improve the effectiveness of testing first than to improve the efficiency of poor testing. Automating chaos just gives faster chaos.
2. Tests are sometimes mistaken with quality assurance. These two notions are not identical: 1) quality assurance ensures that the organization's processes are implemented and applied correctly; 2) testing identifies defects and failures and provides information on the software and the risks associated with their release to the market. - Bernard Homes
3. The job of a tester is to prove that the software is bug-free, while it has to be the other way around: The job of a tester is to prove that the software is broken. The better testers are doing their jobs, the more bugs they manage to find and report. - Yegor Bugayenko
4. In many ways, being a good tester is harder than being a good developer because testing requires not only a very good understanding of the development process and its products, but it also demands the ability to anticipate likely faults and errors. - John D. McGregor
5. Quality is a product of a conflict between programmers and testers. - Yegor Bugayenko

Quotes for Programmer

1. Slow code is optional
2. Truth can only be found in one place: the code - Rober C. Martin
3. If you ever talk to a great programmer, you’ll find they know their tools like an artist knows their paintbrushes. - Bill Gates
4. You might not think that programmers are artists, but programming is an extremely creative profession. It's logic-based creativity - Jhon Romero
5. 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. Andy Hunt
6. Debugging is like being the detective in a crime movie where you are also the murderer. 
7. Do it.  Do it right. Do it right now
8. There is no pill to convert yourself as a good programmer, it takes lots of reading, learning, and practice. So start now. 
9. I still think that one of the finest tests of programming ability is to hand the programmer about 30 pages of code and see how quickly he can read through and understand it. - Bill Gates
10. Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. - John F. Woods
11. I’m not a great programmer; I’m just a good programmer with great habits.
12. The code you write makes you a programmer. The code you delete makes you a good one. The code you don’t have to write makes you a great one.
13. You can optimize for low latency. You can optimize for high throughput. You can optimize for memory occupation. However 90% of the time the most precious thing you should optimize for its maintainability.
14. Remember, code is your house, and you have to live in it.
15. We must not blame programmers for their bugs. They belong to them only until the code is merged into the repository. After that, all bugs are ours! - Yegor Bugayenko

Quotes for Architect

1. The brutal truth is that architecture is too important to be left exclusively to a few people. It’s fine to have an architect, but the key way to keep an architecture intact is to make sure that everyone on the team knows what it is and has a stake in it.
2. Software development is about finding trade-offs, for example
1. CAP theorem
2. Normalization vs Denormalization
3. Development speed vs high-quality code
3. There is a big difference between making a simple product and making a product simple - Des Traynor
4. Tips for developers
1. Re-read code before opening a PR
2. An open pull request (PR) is a liability in at least 2 ways. 1 it’s a feature/fix not shipped to customers. 2 it will invite code conflicts soon.
3. Having automated tests but no Continuous Integration(CI) is like having a sword but letting it rot.
4. Programmers/developers need to become software engineers. Think of a solution than the technology to implement it. Think of abstractions then code.
5. Ask for help when truly stuck
6. Help others who are stuck
7. Take tasks that scare you
8. Don't be afraid to admit you don't know something
5. A clever person solves a problem. A wise person AVOIDS it. Albert Einstein
6. Before software can be reusable it first has to be usable. Ralph E. Johnson
7. Why do we never have time to do it right, but always have time to DO IT OVER?
8. Given eight hours to chop down a tree, I’d spend six sharpening his axe. - Abraham Lincoln
9. Design first then code.
10. Don't patch bugs out, rewrite them out.
11. Don't test bugs out, design them out.
12. I myself have had many failures and I’ve learned that if you are not failing a lot, you are probably not being as creative as you could be, you aren’t stretching your imagination enough. - John Backus
13. Theory and practice sometimes clash. And when that happens, theory loses. Every single time.
14. Quality must be enforced, otherwise, it won’t happen. We programmers must be required to write tests, otherwise, we won’t do it.
15. Being a senior developer doesn’t mean getting a large salary or being appreciated in the office. It means belonging to an elite group of developers who know how to do certain things and can do them. Most of the time architects are nothing but senior developers.
16. Any software project must have a technical leader, who is responsible for all technical decisions made by the team and have enough authority to make them. Responsibility and authority are two mandatory components that must be present in order to make it possible to call such a person an architect. - Yegor Bugayenko
17. Engineering is a profession that can do the job of almost all other professions. - Amit Kalantri
18. Domain-Driven Design (DDD) is a process that aligns your code with the reality of your problem domain. - Scott Millett