The growth of small-tech teams

Many small technical team, in the face of fast growing business, feel powerless. They feel that the urgent need for cattle, but the cattle are always, not high price, is just want to stay big companies, also do not want to take risks in small enterprises, to have a high salary and options ... In fact, the cattle do not need more, the cattle are not always able to stay, the cattle do not solve all problems. I want to sum up something, but I don't have much experience, um. Think of something. does not calculate the instruction, is to leave this record, in the future has the opportunity to pull the team to do the revolution, hoped can solve this problem.

Teams need to accumulate experience from the outset. I have seen a fault reporting system, the first step in the event of failure is to record the problem. Then proceed to http://www.aliyun.com/zixun/aggregation/7432.html "> Solve the problem. Solve the problem, and then record the process. Later there are new people, you can read some of the common problems of the solution, quick start. Within Yahoo, there are several wikis that typically require all of the project's documentation on it, with a wiki with perfect search capabilities. Some people leave something, even if there is no handover, also not let Up-and. Specifications are important. Set up at the outset. The specification is not much. Maybe no one has, but if you want to follow a specification, you have to have a model. It's better to be pushed. The code has to be commented, and that's what everyone says, but it's really too much coder to keep it. At least, the comment on who wrote the code, when the write, can always? Is it low enough for a file to add two lines? When I deal with a business problem in Yahoo, I really have a headache: a bunch of php files, often the first few functions have comments, to the back of the estimate is lazy, or forget, on a line of comments are gone. Eldest brother, you write your gtalk or MSN on the file head, I specially go to ask you to consult you OK? Archive。 Backup。 Technical documentation, program code, to be backed up. Otherwise, once the hard drive hang something, may be completely finished. A big team has a system now, and there's no big mistake. And it is a person who make a mistake, a project wrong, no serious consequences. Small team can be a setback, that is, the project frustrated economic damage team to leave .... If you can, try what the team is doing and what the pairing tests are. Everyone has the advantage, I have a period of time with Horon behind Look, (well, peeping ...), found that he used vim, and then pestered him to teach me. After learning, you can never leave. There is also a while watching Xu Peng writing things, but also benefited a lot. For example, to start by filling the database with something (100w+), the performance problem development phase can be exposed to almost, later will be less to backtrack. Cattle people don't always solve problems. Well, I said it at the beginning. At first, not all things need to be solved by a lot of cattle. The significance of the cow is to introduce the direction of learning to the team, guide the team growth, the key moment to provoke a burden. Small team, get a cow person is enough. More, the chaos. It is not easy for a small business owner to serve a cow. Once the cow asked for a fake or something, he thought, alas, he won't quit. Cattle people always like a lot of new things at once, can not meet him. Well, it's a little bit higher than the team now, and it can be done quickly by other members of the team. Too trendy things, easy to play their own death. Respect him, restrain him. As the team grows, so does the treatment. Otherwise, not very easy to cultivate a few people, ability strength, all fly. Cultivate peopleCome and keep. New people generally in the initial ability to grow quickly, it is easy to be tempted, easy personal expansion. It's good to go through a bit. It's OK for the boss to earn less, let's take it slow. It's not a rush. Get rid of the black sheep at any time. Don't wait for him to motivate others to change jobs, or to introduce recruiters to colleagues. Small team, stability first, unity first. Small team, very fragile. 35 people, 10 fishes gun, suddenly a job-hopping, but also take two to go together, enough for a while boss.

Well, team growth is Pain di, bother Di, let people headaches. Small team, to steady progress.

Source Address: http://www.162cm.com/arch......ives/991.html