A Guide for High-Quality Programmers

1. Start preparations

1. First of all, your computer does not have to be highly configured, but it must It has to be dual screens, and the bigger the better. It would be even better if it could have one horizontal screen and one vertical screen. In this way, one is used to check information and the other is used to write code. In short, it should appear to be very informative and very efficient.

2. If people ask you where did you learn PHP that is so awesome? Don't say you learned it from php Chinese website. Be sure to say that you learned it all by yourself! Let me brag again: I know all the languages, I am self-taught, and I can master any programming language in three days. Remember, don’t blink when you brag.

3. Again, your chair does not have to be comfortable, but it must be able to lie down halfway.

4. Then, there should be a large number of sticky notes, preferably in various colors, to record the tasks to be completed every day. Try to stick it all along the border of the computer screen, so that it can show that there are many things going on.

5. Reference books, mechanical industry, orelly, electronic industry, etc. are acceptable. If you can speak English, use English. If you can’t photocopy, you can also use it. Anyway, the thicker the better. Remember, don’t put it on the bookshelf. On the table, they must be piled half open on the table.

2. Starting from the entrance

1. Dress up! Dress up! Dress up! (Say important things three times) No matter you go to a laboratory, a company building, a private house in a small company, or a black workshop where you start your own business; no matter spring, summer, autumn, winter, day or night, wind or rain, lightning Thunder, typhoons and tornadoes, a high-quality programmer should pay great attention to what he wears! Here are some professional advanced suggestions for you, such as:

● Basic outfit: shirt, jeans, casual shoes.

● Intermediate attire: T-shirt, loose shorts, slippers.

● High-end clothing: vest, loose floral pants and flip-flops.

2. Behave appropriately. When you are in the corridor or aisle, you must put your hands in your pockets and walk like a ruffian. Even if you don't look like it, you must at least look a little anti-social. If that doesn't work, you can try to act like a weak genius. The geek route...

3. If a girl is pointing at you behind your back or whispering something, you should lower your head first, then keep your head down, then slowly look back and smile mischievously. But don't make a sound and walk away quickly.

4. After entering the door, remember not to say hello to anyone, and walk straight to your seat. At most, when you pass by the coffee machine, make a cup of coffee, but do not make any unnecessary movements next, so that you can show yourself Focused and focused.

3. Stop moving after sitting down

1. After sitting down, your posture needs to be slightly tilted back. The best way to test this program is to cross your legs, then lower your head while leaning back so that you can see the screen, and keep this posture until you get off work.

2. Brutally push the pile of books in front of the computer open to look more manly. Then take off a sticky note on the computer, take a look at it, and remember, no more than 3 seconds. Now you can start coding

3. If you can’t use the IDE, don’t use it. If you really can't install it, no matter what the IDE is, it must be adjusted to a black background like DOS. This is very important.

4. Never use IM tools to communicate, never ask colleagues questions, it will appear that you are not good at it, just go online or read books by yourself.

4. Must use high-end, regardless of whether it is practical or not

1. If you write a front-end interface, keep debugging the background Code; if you write Java, mix C in it; if you write C, mix assembly in it. Not only do you have to code, but you also have to take out an English book from time to time and look through it. If you don’t understand, just look at the illustrations, then throw it in front of you, pretend to understand and continue coding.

2. For example, C: all switches are restructured into polymorphism; if there are pointers, all are changed to smart ones; C must write its own template; all numbers must be replaced with macro names, and the names can be as long as possible long; the struct should not appear. If it does, it must be modified with __attriburte__; operations are all bit operations; operators are all overloaded; networks are all concurrent buffer thread pools; int is only declared with int32_t There is no need for ordinary inheritance, what is multiple inheritance and virtual inheritance? HelloWorld also needs to be written to catch exceptions. When future generations look at the code, there are a bunch of keywords extern, asm, auto, XXXXX_cast, volatile, explicit, register, template, etc. in the middle. Little programmers who are always typing int, if, else, and for suddenly feel admiration.

3. Want to write a comment? forget it. There are only two routes to choose from: First, the variable names are extremely long, and reading the code is as smooth as reading an English article, and there is no need to add comments at all. Second, the code is extremely obscure, and adding comments or not has no impact at all.

5. Finally leave in style

1. Whether it’s joking among colleagues or any group time, don’t raise your head. Don't look around. Even if there is an earthquake or fire, you must submit the code before leaving.

#2. When people leave, the host cannot be turned off. At least you have to run a daily build. If it doesn't work, you can barely pass it by submitting it to svn, and you have to ensure that it can run normally on weekends.

3. "From Getting Started to Giving Up" or "Cervical Spine Rehabilitation Guide" have been piled up in front of the screen again. Do not organize them. Be sure to appear knowledgeable and knowledgeable.

4. Overtime is a must. You don’t have to be the last one to leave in the technical department, but you must let the front desk, marketing, and especially the PM leave before you can leave.

5. When walking, you must be straightforward and simple. Never pack anything. Stand up, walk out, OK, that's it.

6. If you must say something when you leave, then find the person who is struggling the most and tell him: Your progress is too slow. Don’t keep me waiting for you.