Crazy programmers are by no means arrogant and desperate programmers, but programmers who can be down-to-earth and work hard continuously. When a programmer truly achieves these two things, after he becomes technically advanced, the only thing that can limit him is The only thing you have is imagination. Only then can you be considered a "crazy programmer". This kind of programmer can make your opponents extremely frightened. The following are inspirational quotes from programmers, welcome to read them!

1. Either be the first or the best.

2. Beliefs and goals must always permeate the hearts of programmers.

3. When you are most tired, your family is your best destination.

4. C programmers will never perish. They just cast to void.

5. Real programmers think that they understand what users need better than users.

6. Take a step back and the sky is brighter. This is a proper state of mind.

7. The past code was untested code.

8. Excellent judgment comes from experience, but experience comes from wrong judgment.

9. Testing is to show the existence of bugs rather than their absence.

10. One of the problems in our world is that fools swear and wise people are full of doubts.

11. There are three gangs of heroes, and the same is true for programmers.

12. No matter how many books you read, you won’t be able to learn all the scripts. You need to practice more.

13. Selfless dedication is not a fantasy, sometimes we can do it.

14. There are only two truths in the world: 1. People will definitely die. 2. The program must have bugs.

15. Unix is ??very simple. But it takes a certain genius to understand this simplicity.

16. There are many truths contained in the program, and only those with great enlightenment can understand the mysteries.

17. How many setbacks will we encounter in programming? It means giving up. There must be an oasis at the end of the desert.

18. You must have perseverance when doing technology, so as not to give up halfway.

19. Don’t be confused by words such as objects, properties, methods, etc.; the most fundamental thing is to understand the most basic knowledge first.

20. Please practice the examples in the book on your computer, even if there are source files on the supporting CD.

21. Don’t expect to remember and grasp anything after reading the book for the first time – please read it a second or third time.

22. If debugging is a process of eliminating bugs, then programming must be a process of putting bugs in.

23. Knowing something does not mean that you can write scripts. Scripts require the accumulation of experience.

24. A real programmer does not accept the concept of team development unless he is the leader.

25. if (bool learning == false) bool falling behind = true; only by continuous learning can we continue to move forward.

26. Real programmers rarely write comments on their code. If a comment is difficult to write, it will certainly be difficult to read.

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

28. Having no sentimentality and no understanding of romance may be one side of programmers, but having unpretentious love is their other side.

29. This sentence is not very elegant. I completely despise those programmers who are afraid that others will surpass themselves and refuse to answer other people's questions.

30. If construction workers build houses the same way programmers write programs, then the first woodpecker that flies over will destroy human civilization.

31. Programmers can make concessions, but they cannot retreat. They can be shy, but they cannot be weak. In short, programmers must be brave.

32. It’s hard when you want to find an error in your code; it’s even harder when you think your code will have no errors.

33. Programmers, what do they think? What they think about is always technology, and what they admire is always technology.

34. A 100-line code debugging may cause programmers to encounter many setbacks. Therefore, we can never bow our heads in the face of setbacks.

35. One of the main reasons for the collapse of the Roman Empire was that without 0, they had no effective way to indicate the successful termination of their C program.

36. Never give up. There are two principles in never giving up. The first principle is to never give up. The second principle is: when you want to give up, look back at the first principle.

37. What does it feel like to sit quietly in front of a computer and write code? It was the feeling of a martial arts master practicing in seclusion.

38. Even if we stand on the top of the mountains, don’t forget that the eagle can still fly over our heads. Pride is something more ridiculous than using java for low-level development.

39. Those who are tough are afraid of those who are violent, those who are violent are afraid of risking their lives, and madmen are all desperate for their lives, so madmen are powerful. There is only one kind of programmer, a crazy programmer.

40. Whenever you learn a difficult point in a script, try to explain this knowledge point to others and let them understand it - only if you can explain it clearly will you truly understand it.

41. As a real programmer, you should first respect programming and love the program you write. He is your partner, not a tool.

42. Every problem is a lock. You have to believe that there must be a key in the world that can open the lock, and you can also find the key.

43. Read the help. Don’t stop reading it because it is difficult and you are a beginner; the help is always the best reference manual, although the text in the help is sometimes difficult to understand and it always feels not intuitive enough.

44. Non-excellent programmers often use up space and time, but excellent programmers always have enough space and time to complete programming tasks, and the cooperation is almost perfect.

45. Programmers make a bet with God to develop bigger and better software that even fools can use. But God always creates bigger and dumber fools. So, God always wins.

46. For programmers, most of the happiness comes from solving problems, especially solving problems independently, rather than from how big the case is and how big the bonus is.

47. A real programmer will not work between 9:00 am and 5:00 pm. If you see him working at 9:00 am, it means that he has been working since last night. Now.

48. ‘Theory’ is something you know is true, but it doesn’t work. ‘Practice’ is that it works great, but you don’t know why. Programmers combine theory and practice: it doesn't work, and they don't know why.

49. If you are better than him, he will not admit you, but will be jealous of you. Only if you are much better than him, will he admit you and admire you very much, so do it. You must do much better than others.

50. When senior programmers talk about whether a person has a future in learning to write programs, they always say: "Learning programs not only requires hard work and hard work, but also whether you have sense. For people with sense, no matter how hard you learn, no matter how much you explain to them, the effect will not be good.

51. When you are halfway through using the script and find that the method you used is clumsy, please don’t stop immediately; please. Complete the rest of the code as quickly as possible to ensure the integrity of the code, then analyze your errors and rewrite and work.

52. If debugging a program makes you very distressed, never give up. Success is always behind the corner. Unless you go to the corner, you will never know how far you are from him, so please remember, persevere until you succeed.