A different perspective, environmental protection in the programmer's world

Abstract: There is a lot of technical environmental protection work around us that can be done. For example, when using less root user under Linux, when using SQL, select before delete, so that you will not do something that will make you regret. It won't make you start all over again, so at least you won't waste power. When writing code, be careful to manage memory, various resources, and thread concurrency, organize the business logic in your code, do unit testing, automate regression testing, etc.

There is a lot of technical environmental work around us that can be done. For example, when using less root user under Linux, when using SQL, select before delete, so that you will not do something that will make you regret. It won't make you start all over again, so at least you won't waste power. When writing code, be careful to manage memory, various resources, and thread concurrency, organize the business logic in your code, do unit testing, automate regression testing, etc. This way you will encounter fewer bugs and less time to investigate when you encounter a bug. When operating the computer, use less cracked software and visit less strange websites. In this way, you will have less virus, less loss, and less system redo. The same can save power, the most important thing is to save a lot of your time, so that you can do something more valuable.

Of course, in addition, we should be an atmospheric, high-minded environmentalists, such as the following things:

reject IE6. If you are determined not to use IE6 and influence the people around you, ask them to upgrade to IE6, try Chrome or Firefox, and tell your friends more about how to design passwords, how to protect your privacy and security on the Internet, and how to prevent Trojans. In this way, there will be fewer problems, fewer system installations, some power savings, and more time to do more meaningful things. It is also contributing to the entire world and the entire human race.

663b13384066059ff8e30365ab80d7c12d711a95

Refuse plagiarism and copycats. If you despise those naked plagiarists and don't use their products, some people will say that you just want to flaunt your own nobility, ZB, fake nobility, and everyone will say you don't need it. Actually not, you are doing this for "environmental protection", in order to "protect a healthy IT environment". Although you are not innovating, your behavior is encouraging an environment of innovation. In this way, if the entire environment is It is under the influence of the innovation culture that we will be healthier, technicians will be respected, and we ourselves will ultimately benefit. Although we only suppress plagiarism and copycats, we indirectly contribute to society.

43bfe5fac18bc222462f3b8ab986382d93a73e2b

refused to float. For example: Floating entrepreneurs are squeezed round by round by venture capitalists. In order to satisfy the VCs, sacrifice their original intentions, go to the water army to brush the rankings, send spam emails, burn money to buy shouts, create false prosperity, and so on. In addition, don’t chase those new technologies, and be less exaggerated. Don’t talk about massive data and high performance. Instead, it’s better to calm down and study the technologies of the past ten years, think about the problems around you, step by step Take a steady step and avoid a few somersaults. In this way, you will be able to have more ability and self-confidence, and you will be able to do more things and solve more problems. If your career source is good, it will be very environmentally friendly. .

445685757475155bce7f1930d07deb1859990d38

Environmental protection requirements. When we analyze the requirements, if we can do it not like the article "Whose fault is this?" needs? What kind of problems does this function mainly solve? Why not the other one? Can you simplify it? In fact, we don't need to innovate, we only need to really ask these questions, we can watch less detours, work less hard overtime, have less internal friction, and less complain, and we can save money for this society. some resources and thus environmental protection.

5d7ce8e28564874fb36d683603214c988cc7cac6

Environmentally friendly development. When we design and write code, if we spend more time thinking about it, we can write less code (see "More Time Less Code"). If we think a bit more at the beginning, don't rush to understand the world in an iterative way, think more about how to decouple complex things, simplify complex things, how to make an elegant design, how to make our The program is less tricky, how to make our program more concise, clearer, and straighter.

At the beginning, think about the possible changes in future requirements, how the software needs to be tested in the future, and how the future system needs to be operated and maintained. Then, we can have less rework, less refactoring, less debt, less low-level errors, and less Take some pressure after the system goes online. Then, we can also save some resources for this society. To put it more bluntly, you use less code to generate higher benefits, consume less CPU, save some power, and indirectly protect the environment.