Summary of the two work experience

When a programmer for several years, although more time writing code point, but hands also has managed, with over part of the programmer. Has been thinking about a problem, what is the programmer, the programmer should do those things, what kind of quality of programmer is a programmer? What kind of programmer programmer be responsible for it? Work which I have not found less staff is doing a job, how it happened? they just put me to complete assigned work exactly right, but do not ask why? some programmers prefer just needs to change, you have to change yourself feel good, changed do not report, when finally found and turned over to the project requirements are not the same? so stupid.
　　According to my own experience of the programmer divided into the following
　　1, a simple no-brainer: This staff is one of the most irritating, because most of them are just getting started, or students just out of school, do not like to ask, do not know how to analyze, it just blindly obedient, why they simply do? that is because they never ask, do not speak nor their own ideas, so that you do what you do, how to do it yourself on how dry it sounds good employees feel special, very obedient, if only so give you like, the frightening thing is they do not have brains, like you said let him complete an added feature of it, they are very obedient to you to do it, but just an added feature, he did not increase after the function something about the problem refresh the data, or do the necessary verification, but it can not scalable code, that are faceless side of things, impossible. You say let you do a search function, he is entirely possible for you to do it all in one query function, not control you or not based on time, not to paging, or other means of inquiry, but also rational people will tell you, you did not say ah on demand, saying only that there must be a function queries? then you speechless.
　　2, the first cut after Minato's mind: These programmers generally work for a year or two years of work experience, thinks he is some experience, and do several projects, NB, feel incredible. There are always a function assigned their own ideas, in fact, he did not know these ideas not mature, just a personal subjective intentions, you say let people make a navigation bar, you clearly told him in the head with, should be straight row pull-down type. Well, get demand up, he did no matter how you do this, in the process of doing, he found himself before doing some projects in the navigation bar, and look great, they think, is how the manager wants, the design also as I designed good-looking, I gave him change it might even get his reward, then put himself straight into a row of drop-down navigation, direct discharge panel that, as good-looking, but do not tell the manager, wanted to give everyone a surprise to see a manager who knows that how to change the demand, customers do not like this, then he will tell you the reason, say good-looking, and what better scalability, advanced technology, fashion, then you will be free resistance to tell him that you really do look good, but how do customers do not pay, so he had no way to change under your "forced", then you are not satisfied with his work, first of all is the man bad management, old themselves, and do not take you seriously, how do managers a good point will slowly guide it, big temper manager will direct throw the word "get out."
　　Let's analyze his psychology:
　　The first possibility is to feel a lot of projects to do, there is a little arrogant attitude, arrogant, look down on what others design, always think their technology and code great, because he fought in a year or two community programs , and also be some exposure. But they really do not understand, now own just as current as Cao Cao Cao Ren learn, but learn to do their shape and obtaining God. Most of the software, websites, not only the value of the site itself, successful or not, not what they say, nor is the manager have the final say, will have to see customers, customers like the word is a good thing, customers do not understand technology ah, no matter how you write, customers do not understand oh, so be sure do not make change demand, and market software to combine in order to truly reflect its value, so that we do like the software, rather than purely technical accumulation.
　　The second possibility is that he lazy, because within two years, also wrote a lot of code, have got a lot of source code directly on the line to find a good point on energy, why should write their own ah, but also good-looking and fast.
　　A third possibility is that they can not achieve, but do not want to learn, feeling a waste of time, so it got a direct change. I feel if you write the words, written Fortunately, that is not good writing, delay time, a few days to finish navigation, would be ashamed of. So to speed up.
　　Such programmers have brains, but do not listen, problem management, must be good guide, I hope at this stage of the friends attention. Enhance learning, seriously do the project, so that their regularization. Do Rumo Dao. See more experienced programmer's code, think about why managers do this, listen to his reasons, the report must be written at the same time changing demand, or through directly to discuss the matter, not to themselves.
　　3, have brains, very obedient, very serious, but the foundation is not good, the code has its limitations: Most of this type of programmer is working one to two years programmer, but different and above, they are very good brain thinking , and it is to listen to the words of the manager, to do things very seriously, they will not finish the overtime write, learn new things quickly, but one thing bad is that they have many reasons to say that they have no time to learn the basics, these people generally is not learn in school, regret it later came out, learn it very seriously, as learned some new knowledge, high starting point, look down on the basis of things, and never think of nothing to look at programming basics, take a look at algorithms, data structures look always thought I could make such a project, but also to see those little things will be very shameful, so the company never looked back home but do not want to see, a long time, technology will have significant limitations on a piece of technology is very good, but not very good for other technologies, so when you receive a project, always prefer to use their existing, will be the technology to achieve, turn around and around finally put things Written, but also to work overtime to complete, but the performance of the code, is far worse on the stability and efficiency, scalability is also out of the question, over time, a project increased, there will be many times the anti-worker, because the demand is constantly changing, so your code should be changed, it is only natural feeling, a project right, took over much trouble, just get new projects, old projects on the problem, not here, little fault when the function is to be upgraded, so put down the new project, the project set out to reform the old hands can have three or four projects will be on the go, the more change, the change would have no way to re-design or direct say that this feature can not be achieved.
　　In fact, a friend at this stage promising, as long as little thought tutorial about their technical defects, see more master code, think about before you write, design it, naturally more with less, do not have unrealistic expectations of mentality.
　　Let's talk about how the real master programmer ------------ NB figure works
　　1. Do not just changing needs: they are not subjective to change something, whether it is right or wrong, if you want to change, then they will be in a meeting, or to privately raise with you, then by change, otherwise it will act according to the needs of .
　　2. Do not write code without thinking: when writing feature will add some user-friendly features, plus a small icon than the fruit, add some validation, to deal with some operating practices, Gaga shortcuts, deal Tab order, and so these , do you say, they will take care of themselves.
　　3. Do not write code without vision: they would want to write code that will not be a simple function to achieve, he wants to, if people have to use this method of how to do, how to change the future, when to do, write the code is not reasonable, it is not it will affect the performance, and then will be "stingy" shot.
　　4. irresponsible not to write code: First, we write code for customers to use, and second, allow other people to see, not just their own maintenance, to be responsible for their own code, the code out from his hand is their own behalf face, the code is not good, people will "play face". They do not want to be beaten so they are responsible.
　　Expert in programming efficiency may not be much faster than ordinary programmers, because they would mean each line of code yourself Qiaoxia. This "stingy" has two meanings, structure and integrity considerations One project, Coding second is from the perspective of performance and optimization. In fact, here it is the mapping of a vision technology developer.
　　There are many technical experts stressed that while the overall concept of the project implementation. The face of a project, even an ordinary member of the team, but also seeks to examine the development needs from the perspective of the overall structure of the project, expected to do optimization and configuration of the various modules, interfaces and communication. This review technical layout of the entire project from the global, predict problems that may arise.
　　After determining the whole, the implementation of specific modules to achieve, every line of code will not only have to consider the context of planning, but also with the overall layout between modules. This is the technical field of view within the module, such as the definition of the interface, the readability of annotation, the code efficiency and the like. When before you write a line of code, to consider whether it would affect the whole system, whether other convenient interface calls, which are developing a master of "technology subconscious."
　　According to some frequently led the entry-level developer's technical manager, most people only consider the module responsible for their own development, the lack of a technology perspective overall and code performance demanding attitude, although this can be completed by the delivery date of the project, but there are huge obstacles to self-improve the quality of projects and developers.
　　Development ace is the code reader. Code reader amount of technical experts is most common programmer hundred times, reading the code much longer than the time to write code. Most programmers only to developers as a job, they care about the platform's prospects, the merits of the language, the level of remuneration; they do not want to delve into a technical point repeatedly, unwilling to elaborate a bug test, do not want to own technology improve the level of spend more time. And the development of technical experts often have simple dreams, technology willing to pay all their time.
　　To have a purely technical dream, and to pay all their time.
　　Yes, all the time.
　　In this wish each a mere technical dreams can become a programming expert.