Z teammates on the line
Recently chat together and engage in the development of the students, some time ago we have just gone through telecommuting and teamwork scene, it seems inevitable that we all want a little Tucao things.
Therefore Benpian ready to share with you, since we work encountered some programmers Z teammate interesting experience, of course, also share a teammate themselves into X Z's upbringing from his teammates.
Nana Z teammates have, so that a good team is really important.
Having said that, of course, it is the only hope to ridicule than to reflect on yourself, because everyone is the same, you need some good atmosphere excitation source and technology to help us get better, after all, no one is born to single-handedly write good code.
Pig 1: love to write bad code that
Some people have doubts, as a beginner, is to write good code Zezheng it?
In fact, write good code is difficult?
Good code, in fact, does not require complicated! Do not need virtuoso! But you do not need the abuse of syntactic sugar!
Code is clear , clear , readable , maintainable only the first step, by far the most important step. After all, the code is written on posters, the way to computer-executed , you say?
That Z teammate common bad code is usually how to write it? such as:
1, the key code without comments . As if afraid someone else to read code written by him, then stole his core technologies like. Programmers could have been so difficult, it is necessary to this thing, is not it.
2, the code a big lump . One way to write hundreds of lines in wait for them, to take over and maintain the code of people see a very tough battle, very hard to maintain, this may be the legendary "shi mountain" it.
3, likes virtuoso , abuse syntactic sugar , like to write complex compound expressions , which will also take over the maintenance of those suspected and later in life every day.
4, rubbish name . Either meaningless name, not norms, rules mixed, ambiguous; or digging type name, such as using the existing code or libraries already naming names, could lead to the caller reference error.
Work a few years I found that some people really particularly like him on the continuation of a project code-style, but also especially like to copy code from a project he had to do to go with the old, and particularly stubborn, so those almost too good style It has been accompanied by all his projects.
Although this can also understand, after all, everyone's work background is not the same, but it must be said to have a good team and the project is really important to fried chicken, especially when just to work.
Pig 2: random change other people's code
The company did, after all, the project team , work together. Sometimes everyone to write code, the function will inevitably overlap, the code is also inevitable there will be cross .
For example, a function of a code base you write may be, but there will be Z teammates to call. Z teammates this time if there there is a need to demand change , or to add a new feature , this time Z teammates will likely have no message, very insignificant to come and take you to write code base to change, and to try to meet his needs (and not to think about some of the more scalable wording), and changed not tell you, but not changed annotate, and go is the meal if/elsethat sao operation.
This situation can be very headache, because if really a problem, in fact, the pot is introduced others, there may finally be coming back to you! After all, leadership does not know these details.
Pig 3: digging type the code submitted
It can be said this case is simply a giant pit teammates ...
That's teammate at the time of submission Z code directly to code you write to erase.
Because the company must be teamwork to write code, the code we write together, each to be submitted. For example, many companies use gitto manage code.
Z teammates most of the pit, he found that there is a conflict in the code when submitting the code, this time he could not solve, the results of operations meal sao, his own modified several documents submitted did go up, but before others modify and submission he rolled back.
Another is, gitthere is a terrible nature, it is -fmandatory parameters push, Z teammates love with this thing, it will be forced to cover the distal end of the warehouse with a local warehouse. Consequences is that the file is likely to be content to overwrite the old, historic warehouses submitted records are missing, and so on.
When the code is submitted, the normal procedure is to first update, there is conflict must find ways to resolve the conflict, then submit, must not speculation wow!
Pig 4: arbitrary rejection pot
Like the above second case to say, for example, some basic code you write, the result was changed to Z teammates, as well as the results of reform issues, this time really a problem if you say who is going to pot it back?
Pig 5: teamwork?
I found the work a few years, in fact, most of his teammates still very friendly, but inevitably there are some poor sense of teamwork teammate. For example, I encountered that is very difficult to communicate or learn something very closed person.
Study and work for so many years, you do not say, people really come across a cow around a lot, from the laboratory to the master's graduate school to be recruited into the workplace looking for a job, I met a lot of good technical people. I generally find the real technology and some cattle generally characterized by: modest low-key , open-minded , and the exchange is very easy , so that every arrogant, exchanges are holding a struggling teammates what kind of mentality, in fact, I still do not quite understand is of.
mutual encouragement
Well, spit so much, in fact, I want to say is, each of us as individuals and team members, a lot of good habits need to work together to create and maintain.
We can stop others, we can only proceed from the individual ideas, get better and better!
