Copeat-program force shouxi 1 (0 basic Edition)

I. Preparations

"To do well, you must first sharpen your tools ."

1. The computer does not have to be configured high, but the dual screen is required. The larger the screen, the better, the better. It is better to have a horizontal screen and a vertical screen. One is used to query data and the other is used to write code. In short, it seems that the amount of information is very large and the efficiency is very high.

2. The Chair does not have to be comfortable, but it must be half-lying.

3. A large number of notes and various colors are used to record the transactions to be completed every day. Try to stick the border along the computer screen as full as possible, showing a lot of things.

4. tool books, orelly's, machinery industry, electronics industry, and everything can be either in English or not. The thicker the better, the better, and never put it on the shelf, be sure to heap on the table, half open.

2. Start from entry

1. dress! Dress! Whether you want to go to a lab, a company building, a small company building, or a black workshop that you have created, whether it's spring, summer, autumn, or winter, when it's windy, rainy, or tornado, A programmer of B should be very concerned about his own dress! Here, we only propose the secondary exam. 0 basic: shirt + jeans + casual shoes. Medium: T-shirt + loose shorts + slippers. Advanced outfit: Vest + loose underpants + Flipper.

2. decent manners. In the corridor and whatever form of passage, you must put your hands in your pockets and walk like a hacker. At least it should look a little anti-social. If not, you can take the weak-minded geek route ..

3. let's say that a female points a finger behind your back and whispers that this must be a technical male. You should bow your head first, then keep your head down and look back slowly, make a bad smile, but do not speak out, and then move forward quickly.

4. after entering the door, do not say hello to anyone, straight to your location, a cup of coffee at most, do not have extra actions, show your focus and no worries.

3. Sit down and stop moving.

1. After you sit down, you need to raise your head a little later, and it is best to hold your legs up. Then you can bow your head to see the screen, and then never move again.

2. Roughly open a heap of books in front of the computer, and then take off a notebook on the computer and take a look. It's only three seconds to start coding.

3. Don't use it without using ide. It can't be installed. No matter what IDE is, it must be converted into a black background like DOS.

4. If you write the front-end interface, you will not stop debugging the background code. If you write Java, you will mix C in it. If you write C, you will mix and compile it in it. Not only need coding, but also need to flip out an English book from time to time. If you don't understand it, you can just look at the illustration and then throw it to the front to pretend to understand it and continue coding.

5. What seems to be high-end is used. Don't worry about whether it is useful or not. For example, C ++: Switch duplicates to form polymorphism. If there are pointers, all are changed to smart ones. c ++ must write its own template; the number is the length of the name to be replaced with a macro. struct should not appear. If it appears, it must be modified with _ attriburte _. operations are bit operations; all operators are overloaded; the network is a pool of concurrent buffer threads; Int Is declared only with int32_t; inheritance does not need to be normal, and more inheritance is virtual inheritance; helloworld also needs to write to catch exceptions; the latter looks at the code, and there are a bunch of keyword extern, ASM, auto, xxxxx_cast, volatile, explicit, register, and template in the middle, so that the total number of keyword extern, if, else, for the small program ape suddenly began to worship.

6. staring? Forget it. There are only two routes to choose from: 1. The variable name is very long, and reading the code is as smooth as reading an English article, so you do not need to stare at it. Second, the code is very obscure, and the addition of without gaze has no impact at all.

7. Do not use IM tools to communicate with others. Do not ask questions from colleagues. If you are not a good user, you can access the Internet or check books on your own.

8. Don't look up, whether it's a joke between colleagues or when a group of people occurs, let alone look around. Even if an earthquake or fire occurs, you must submit the code before leaving.

4. easily leave

1. When people go, the host cannot be shut down. At least a daily build should be run, but it cannot be submitted in SVN.

2. Books should have been piled up in front of the screen again. Do not sort them out. Open them again tomorrow.

3. Do not force the last one to go, but all the non-programmers should be required. What market, front-end, and PM should all be gone, so we can do it.

4. Be sure to handle things and never pick up whatever you want. Stand up and go out. Okay, that's it.

5. If you have to say something today, find the most difficult programmer and tell him that your progress is too slow.