Direct delivery
1. Company interns find bugs
2. When debugging, set the breakpoint in the wrong position
3. When I have a great debugging idea
4. I accidentally saw the code I wrote many years ago
5. When I start my unit test for the first time
6. The Delete statement of the database forgot to use the qualifier where...
7. Obviously it's a small bug, but it's not easy to fix it all the time...
8. When I try to adjust something in the production database
9. It seems that no one really found a bug in my product...
10. I still have one task that I haven't completed before get off work
11. When the product has not been tested and put into production directly
12. Those who debug too many threads will understand!
13. When I thought I had caught all possible exceptions...
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. When the programmer first demonstrated the project to the boss
17. Do you need to know more about pair programming?
18. When you see code that you haven't touched in months
19. I got no sleep when I received the call from the product manager!
20. Everything was ok during the test, when it went live...
21. As a programmer, the time to torture the soul has arrived!
22. The process of learning C language back then
23. When the front-end programmer wants to change the back-end code, what the back-end programmer looks like
24. Debug bug
25. Debugging, suddenly the memory overflowed
26. The requirements document is changed again
27. Hard-working back-end engineer
28. Back-end engineers do UI work
29. Separate development of front and back ends
30. Single Internet Dog Day
31. Make hotfix in the production environment
32. Just after adjusting the stable system, the company dropped an architect, and both wanted to rebuild the existing system...
33. When programmers hear customers say they are still using IE
34. When hackers get root privileges
35. After the code enters the loop branch
36. The process of a novice programmer doing a project for the first time
37. Compile with zero errors and zero warnings once
38. The state of writing code at work around the Spring Festival is like this
39. Confidently refactor a seemingly simple module
40. Be entrusted by the boss to take over the project of a colleague who just left...
41. When they asked me to test all application functions
42. When preparing to get off work, the test brought up a bug again...
43. Use the new framework but forget to read the document
44. Test the code of the intern
45. The harm of network delay...
46. Test the code just written
47. When deleting, I forgot to add the where condition
48. Lightweight architecture meets heavyweight needs
49. When I thought I fixed a bug
50. When I look at intern coding
51. Test my website in IE for the first time
52. When I first tested my code
53. Novice debugging CSS
54. Deliver customer requirements in advance
55. The interface I designed and the interface that others call me (it hurts)
56. try-catch in the wrong place
57. Fix a small bug, but the server is down
58. When I push the wrong branch
59. Often interrupted at work
60. When senior developers are programming as a team
61. Never use two hands series that can be done with one finger
62. Senior developers refactor the code
No more, no fun, hold back, can't laugh