I am a single-player, I can solve many problems with a single gun, in fact, many times I am indeed in a single gun.
After more than ten years of "standard" education, I learned to solve independently. In the school, many times the collaborative behavior will be criticized as an improper behavior, such as the collaboration in the exam is called cheating. At the same time as the ability of independent thinking, the collaborative ability is lost. The loss of collaborative ability is often accompanied by selfishness. Why do I have to tell you about a problem that I have a hard work? This is what I demonstrate! The individual opposite the individual is often ignored, and the feeling of "Hedi Chicken Group" is far better than "common prosperity".
The history of software development is almost a series of individual hero, from Bill Gates to Linus Torvalds, which is not allowed to make the world to change people. Ask, we have used the programmers of the later persons, there are no masters in the hearts used to worship, and maybe the difference is the less level, the less worship. Like those who have become a chasing star, it is often imitated, intentionally or unintentional to idols. The worship of individual heroes is often hoped to have an independent ability to create a world.
Campus's atmosphere encourages this "independence", and the real-world software development requires "collaboration", after all, the problem we face is no longer able to solve it before the deadline. Although I am in a environment that needs collaboration, I am very developing with people because of work allocation, so I still in the state of independent work. It is also because of independent work, exercise my ability to solve the problem, with the rest assured to me to solve problems, the person in charge will be more responsible for the development of a single module, so I will get more and more "unique".
Recently, in cooperation with several friends, we have to develop a thing, consider the actual level of these friends and the degree of understanding of the target, in the early stage, I need me to lead them together. As in peace, I will enter the stage of solving various incurable diseases at first, and I will tell them my experience.
One day, I asked a friend, what I feel about what I said. I am unexpected, the answer to me is not about what I explain: "I think you are too tired." This is my interest. He believes that since everyone is developing, you should take a responsibility together. Now, the situation is that I have anti-all the burners, and others are in a relatively idle state, for a team, this is absolutely It is an unreasonable. In the current state, I actually act as a person in charge, you should know how to assign your work to others, not to bear, this will cause a group of tragic results.
His words opened a door to me, let me enter a completely different world. I have never thought about this problem before. I have never truly undertake the person in charge, never considered the assignment of work to others, in my original field of view, I have encountered problems I need to solve myself. After all, I suddenly turned out. Of course, I believe I can solve the vast majority of problems you have, but not all these must do it yourself.
In actual work, I really feel that my time is somewhat not enough, it is necessary to design, but also to encode, and consider the next direction.
On the other hand, this practice is also an untrust of your peers, although it may be unconscious. In a team, the trust of each other can let everyone take responsibility together. For current development, the current ability is not enough to complete, but if you don't give them enough opportunities, they will never reach the requirements, and the gap will only get more and more. Personal capabilities are also increasing during the development process.
In the end, I decided to accept this friend's suggestion and put it completely to them, and I will continue to go forward and do some technical exploration for the next step. Software development is not a person's work, and independent solving problems does not mean everything is made by one, and a small cleverness cannot be comparable to collective wisdom.
The new beginning is today is the day starting to start, I hope that the new beginning is now. Our project version 2.0 has been doing this year since the end of last year, because it is my first project, I have a non-consequent feelings. It is precisely because it is the first, so it is inevitable that there are some unsatisfactory places. In the previous version 1.0, I just override several modules you are responsible. Although there is a certain understanding of the whole system, after all, that is not my own experience, what you can see is very limited. In the design of 2.0, I do my best to avoid the problems in the 1.0 I can see. From the later actual situation, it is indeed a progress relative to 1.0, 2.0, whether it is an overall structure or a development method. Although 2.0 moves into a good direction, because I lack a good understanding of the whole, it seems that 2.0 systems still have many problems that make my heartache. For our system, my biggest ideals in my heart is to develop 3.0. The software industry seems to have a third version to go to mature laws, and Windows is hot from 3.0, and two seniors have fallen in front of Unix. From this, the third version of our system is still looking forward to. In order to give yourself a new beginning, the project leader wants to give the project a new name. On the afternoon, a topic is to give the project. When I turned over the Dictionary in the morning, I topped a word "lama" (lama), which is also the most funny in all my names today. However, this name is not finally selected. The selected name is "CLAP" (applause), based on this name, I made a selection of shine boat, then the next item is called "Cheers". Give the project a more interesting code name, it is a very nice start. No matter what the name is, in my heart, it is still my 3.0, I will release the accumulation in 2.0 in 3.0. In addition to writing the code for 3.0, the biggest goal of this project is to form a frame structure that can be reused from the project. In our department, the C group has a relatively stable development library, while the Java group has not formed a good reuse, so-called multiplexing more stays at the code level. The previous colleague has made a certain try, but later left the department, all the work stopped. In my opinion, the usual framework includes two parts of the base library and frame. The base library can simplify the writing of the code, and the framework is quite defined in a set of development modes. The biggest difference between the base library and the framework is who is called: the base library is usually us to call, and the framework is called our code. It is because of this, Martin Fowler will say that it is an IOC that will be renamed for "IOC" as Dependency Injection. One of this goal is to form a framework - including both the base library, including a framework. The framework cannot be generated in air, so I will rely on 3.0 to generate this framework and gradually improved during the development process. I have mentioned a process of multiple asset generated in the project group, including an incubation process, in view of Apache's INCUBATOR. Any content that enters the prepared multiplex must have been incubated for a period of time, after the code stability document is complete, it can become formal multiplexing. During this development process, I still undertake the main design work, but this range is more than the entire system, not just the original business system. For me, this is another meaningful exercise. I may experience this development, I have a more complete understanding of software development.
The body is most important that the body is not very good. In fact, the body is not good or two days, just never care. The reason is very simple, youth, before the body is not bad, the small illness is not placed in the eyes. Until, I have to discover two years of programmer life for a while, I have lost a lot. I remember that I just arrived in the previous few days, I sat in a day, I was still uncomfortable. I haven't long been used to it, I am too lazy. Because I stayed in the software garden, I have to spend a lot of time, so I am used to going to face the computer in the hall, because there is a deep feeling between the computer, so it faces it for a few hours a few hours. I don't feel tired. Just sat down this day, lack exercise, the body's function is also declining. When the medical examination was experienced last year, the body is no longer 100% health, and the doctor's order is exercised. I belong to the type of causing coffin, because I don't think I'm not good, I didn't put the doctor in my eyes at all. In this way, I still continue my own work habits. The crazy coding at the end of last year has finally arrived in the project before the deadline, but the high-intensity work for ten consecutive days makes my body have begun to have a reaction, and the back often feels hurt. After I have been busy, I have a break in a while, and the body's reaction is not so strong. Plus the joy of the New Year, I will throw this in the cloud. Speaking of this, I have to mention the problem of the stool. When reading Kent Beck's "agile software development", let me feel that the deepest is not the philosophy of testing drive development, but about the problem of stool (Chapter 26, Cheap Desk, Nice Chair). Although our company's stool is not the hardboard stool, it is very uncomfortable, how do you feel awkward? Sit height, on the waist, sit down, and screwless. The encoding time is long, it is inevitable to rely on the stool, so that the body is in a uncomfortable state, no problem. A long period of time is a busy, the body has begun to react again. If it is not a kick, I may not go to see the doctor. The injury to the knee is the end of July, and it is also three months from now. At first, I didn't care, just a little, a colleague sent a bidder, I can't wait to play, and I haven't played for five minutes. When I was stubborn, I was a little bit of kicking half a bed. I thought it was nothing to rest for two days, I didn't expect to be a three months. A colleague who is similar to me, the injury is still longer than me, and it is not good for a year. Not long ago, massage it for a month, finally cured, and he recommended, I finally made a decision to face the doctor. When the bite adheres to the doctor, I will finish the knee and I think of my back. After the doctor, I had a problem. No way, there is a spoonful of sick. Massage thirty oceans, plus a total of sixty waist. This day should be at least one month, count the drug, and throw it in two thousand oceans at once, this is still a good direction. What is the concept of two thousand? Considering the discount factor into, the two hundred oceans can buy a set of "computer programming art", two thousand but ten Bible prices. It is necessary to buy this dozens of books to buy this dozens of books. This suddenly throws two thousand oceans. Oh, spending money is easy to make money! I often listen to people say: "Don't be sick, don't have money," I used to feel the feelings of no money, and now I know the pain. If you have money to buy something, it is good, and it is true that it is really good to give the doctor.
The body is the capital of the revolution. Who is willing to do the business? This is easy, our programmers solve problems, I am happy to remember that there is still a body. Who didn't fight a bug for a few hours? Who didn't have a few hours coded crazy? Who didn't fight after the night or even the history of the morning? If you are a programmer like me, I have been sitting here for a while, then, please stand up. The body is most important, isn't it? Dream returns to the previous blog has been more than two months. If the two "reprint" the article, this time is approximately two and a half months. This is the longest period of BLOG after it is self-being BLogger. In the me, many friends who care about "Dream Storm" asked me, why didn't you see you have a new blog, my answer is more popular, "Busy"! This is an optimal interface that can be blocked, I can't help but do it. There have been many things in more than two months. Far in the horizon, from no one to ask the Asian cup of the empty alley, let the Chinese people carry the Olympics of the vastness, making the Chinese computer people excited MD5 crack ... Nearly, I learned the basic technology of web development, Once, I truly gave others as a teacher. Our products have experienced a few months of evolution. During this period, the brain has an idea of various strange ideas. Idea, if there is a meteor, if it is not possible to record in time, it will also be lost. At this time, I miss my most is my "dream storm". Blog has become part of my life, every thoughts are stunned, my first idea is, this is a good topic, I can write a blog. Without blog, there are many fun in life, and I have not summarized myself in time, so that I always have a regret of the virtuality. During this day, I didn't forget to do advertisements for blog. When chatting with people, BLO is often recommended as a best practice to the behavior, although the effect is small, I am still not tired. What is the most difficult thing in software development? In my opinion, it is not a technology, not a process, but insists. The beginning of the passion is not equal to the successful completion, the program is written to half, solve the original technical problem, the remaining only is boundless purely encoded, when the passion power is lost, the most needed is to persist. Halfway is difficult to become a good programmer. In memory, in addition to learning and programming, blog is me, not much, I am not willing to stick to things, I don't want to give up. "Dream Storm" is back! In the future, I hope to continue to share my happiness with my friends in the "River" that I have a trip, I will have my friends!
At the beginning of the project housing project, the brothers and sisters from the five seas of the five seas came together for a common goal. Under normal circumstances, a project group is difficult to finish from the same person, and everyone is accustomed to the entry of the project team member. If this is a vital project, as the project is carried out every day, a group of so-called "project main" gradually exposes the water, although other people in the project team have the same way, come again, but these project main force is basically It is not asked, the leader will not choose to let them enter the ranks of the horse. The project main force is stable in a project, and the communication between each other has given them a rare tacit understanding, a look, a movement, a few words, no complete expression, everyone has already thought God. It is this tacit understanding, making the exchange province between project groups have gone a lot of trouble, and it is this tacit, invisiblely formed a hard shell. For any newly joined project, if he cannot break this hard shell, he can only be in the project, can't really integrate into the project. Our project has begun from the beginning of last year. To now, in the early stage of the project, I have been insisting on the project, there are three people: the project leader responsible for the development of the management system and me, responsible for the management system development. Brothers. The third person participating in the business system is now incorporated into the project team last year, initially responsible for testing, until the end of the year, the development of the 2.0 system, which officially joined the development business system. The private chat, he said to me that he has encountered various difficulties when he first entered the business system: the project document is incomplete, and it is very simple to understand the project. The development work is not clear ... At that time, I didn't realize the existence of these problems. Because everything is very clear, I am very easy to discuss in the project and the person in charge, because each other knows. But all this, for this brother who has just joined us, is not so simple, our words may be like a book, because no one tells him everything you should know. However, he finally was hard to work, integrated into the project group, and another one was not so lucky. It is also the end of last year. In view of the hard work of the management system, the new needs are pressed, and a colleague enters the project team and joins the development team of the management system. Before before and after, he did half a year in our project group. Unfortunately, he can eventually be integrated into the project group. Since the management system is not very familiar, the person in charge often gives the content of the management system to the colleague responsible for the management system, and the task of this new colleague can only arrange a probably one. He expects that colleagues who are responsible for managing systems can make better arrangements. However, this idea did not have adequate communication, and the colleague is only the developer of the management system, but there is no real "official title" on the head, so he is not obliged to complete the "responsibility" work. The result of this is that this new colleague is often a long period of time, I don't know what I should do. When the period is approaching, I suddenly discovered that I have so many things to do. Finally, he broke out in a project group meeting. Now, he left our project group and changed to other project groups. It is nothing wrong with the discussion of people here, and after discovering problems, we need to solve problems. As the saying goes: "A slap in the face is not ringing", there is a problem, and it is usually not very ideal.
