Students must read the 40 moments that most make programmers collapse

The 40 crash moments of programmers are too real

01. Company interns find bugs

02. When debugging, set breakpoints on errors

03. When I have a great debugging idea

04. By chance I see the code I wrote many years ago

05. When I Starting my unit test for the first time

06. I forgot to use the qualifier where in the delete statement of the database

07. It is obviously a small bug, but it cannot be fixed.

08. When I try to adjust something in the production database

09. It seems that no one really found the bug in my product

10. Before leaving get off work, I still There is a task that has not been completed

11. When the product is put into production without testing

12. Anyone who debugs too many threads will understand

13. When I think When all possible exceptions have been caught...

14. When I try to clean up a few lines of so-called old code

15. When someone asks me to help him debug the code

16. The programmer demonstrates the project to the boss for the first time

17. When you see code you haven’t touched in months

18. Receive I didn’t feel sleepy at all when the product manager called me

19. Everything was ok during the test, but when it was actually launched...

20. As a programmer, it is a torture of the soul. The time has come

21. The process of learning C language back then

22. When the front-end programmer wanted to change the back-end code, the back-end programmer acted stupidly

23. Debugging bug

24. While debugging, suddenly the memory overflowed

25. The requirements document has been changed again

26. The hard-working back-end engineer

27. Back-end engineers do UI work

28. Do hotfixes in the production environment

29. Just adjusted the stable system, the company was airlifted Both architects have to reconstruct the existing system...

30. When the programmer hears that the customer is still using IE

31. The functionality is improved Let’s talk about it first

32. The process of a novice programmer doing a project for the first time

33. Compilation with zero errors and zero warnings is passed

34. Around the Spring Festival The status of writing code at work is like this

35. I was assigned by my boss to take over the project of my colleague who just resigned...

36. When I was about to get off work, the test reported a bug again... .

37. Test the code you just wrote

38. When I thought I fixed a bug

39. When a novice programmer tries a new framework

40. The interface I designed and the interface that others call me (it hurts)