These secret techniques that only the coding gods understand will be taught to you today...
1. Serious nonsense
During the confrontation with the product manager, the function that is not good/does not want to be realized is spoken out in a serious way through metaphysics, etc., so that the product manager is confused on the spot and retreats in spite of the difficulties.
2. Three stages of debugging
The first paragraph: exhaustive debugging
When you can't find the problem, try commenting out the relevant code line by line until you find the problem.
The second paragraph: "Exhaustive Method Debugging" Advanced Edition: Dichotomy Debugging
The expression is similar to the "two-point debugging spell". When the problem cannot be found, try to delete half of the relevant code and compile and run. If the problem still exists, then delete half of the code to compile and run. This method theoretically takes O(logn) time (n is the number of lines of code), and is said to be slightly faster than the exhaustive method.
The third paragraph: online debugging
If the first two methods are good or not, and I don’t know if this is the right change, send it to the online and try it first. . . If it doesn't work, roll back immediately!
3、"1111111111" 术
4. Too lazy to explain
When a programmer is too lazy to explain what he's doing, he usually summarizes his code in terms of "algorithms".
5. Forget everything
Looking at the code I wrote three months ago, I completely forgot why I wrote it that way.
6. Everyone is a fool
Product managers are stupid X, QA is stupid X
The user is stupid X, the one who wrote this code is stupid X
Wait. . .
It seems that I wrote it. . .
7. Product consecration
Please ask the master to perform a casting consecration ceremony for the products that are about to be launched to ensure stable operation and rolling financial resources. For example like this:
or like this
And this
8. Code Consecration
Put a Buddha image at the beginning of each file to pray for the blessing of the Buddha and never have bugs. E.g:
9, hit the big luck debug technique
Just change it, it seems to be running correctly, although I don't know why. The specific form is:
10. Do not believe in evil debug techniques
The specific form is:
11. Pair programming
Two sympathetic programmers fold their hands on the keyboard and program in a tandem position. The technical term is: spooning (spoon)
12, hold back the big trick
It refers to being indifferent after receiving a demand, and then starting to chat on WeChat, swiping Weibo, and watching A/B stations. Start fulfilling requirements as Deadline approaches, and finish the week's workload in a day or a few hours.
13. Mind manipulation
Using a mechanical keyboard to crack and crack code, the programmer next door was upset, inefficient, worked overtime, lacked sleep, and eventually caused his nervous breakdown.
14. Stack Overflow
Refers to using Stackoverflow.com to find answers when you have any questions . Making good use of this technique will make programming more effective.
15. Metaphysics
The code that worked well before I got off work yesterday, I haven't changed anything, it won't get off work if it runs!
Refill every day
co-worker's bastard
Original: http://www.techug.com/post/programmer-funny-pictures-4.html