Programmers will hinder the growth of the details

1, get the development tasks directly on the hand-written code. Lack of necessary communication and design, a great chance of rework. Interactive data format before and after the end of the function associated with potential point is not clear, the interface caller is fully functional, design of storage structures, complex business process design, etc., need to communicate in advance to determine the good, before you start writing code to its capability, or card will take a step by step, progress is slow, or even reverse.
2, the logic chaotic place to add new things, rather than reconstruction. Due to add or change features, you need to add in the old code logic in the new features, this is a good opportunity to reconstruction, but a lot of practice to fill up to fill in the original, based on the results of chaos. Especially in the already chaotic place but also add a new code logic, running really no problem, but on their own code quality assurance zero sense.
3, growing reluctant to share technology with others. To teach is to learn the quickest road, will share what they are learning spread to others, and others can be digested and absorbed, it is one of the best test of their knowledge to master. While in the process of sharing in Reviewing the Old, more deep mastery of knowledge and skills. If you have an idea of the church master apprentice starved to death, it would look very out of date. Under the age of the Internet, what knowledge and skills, is unique to you and others never did? Better to come to share, grow together. A person walking fast, a group of talent to go far.
4, first encountered BUG deny their own problems. This is a universal problem, but also a programmer first reaction when encountered BUG. In the end it is not someone else's problem, the problem often turn full circle back to his hands. Wasted everyone's time, while reducing the efficiency of solving the problem. Pose positive solution should be immediately checked itself, determine if your problem is corrected immediately, if not, to find the problem best, handed over to others to deal with, which is a good habit.
5, the absence of verification conditions, the development of functional tests without directly delivered to testers.One is too much self-confidence, there is a lazy performance. Confident is good, but if we can go through the actual scene to check, double insurance, on their own team is guaranteed. Lazy is irresponsible, indeed some functional tests are complex, but in order to ensure availability features, there is no condition to create the conditions to complete, this is an attitude.
When a repair BUG, entrainment other problems. BUG has not found a test of self-discovery after unauthorized repair, and submit the source code. This is more common in the testing phase, but also later if this problem occurs, the stability of the product / project is a great risk, especially in a production environment. This is a process specification issue, but also a professionalism problem.
6, the lead in organizing what to do, done on idle, not learning new skills, new business. Retired and sit on the brush microblogging circle of friends, take a look at news chat, which is typical of migrant workers thinking, go to work, but also a sense of their own business processes in the company's system, with the corresponding resources to achieve their own the goal, in essence, with own business to complete a goal, the path is the same. In others existing environment, not to mind their own business to treat people, it is simply a waste, this is a great opportunity to exercise, take the initiative to assume greater responsibility for more tasks. Indeed, to do more, the probability of error will be larger, but the low cost of trial and error, have more opportunity to grow, there is nothing better than to grow it!
7, when the cross tasks, focus on their own and can not be integrated upstream and downstream from the global. In fact, this is a problem in the sense of cooperation, need two or more parties are relatively cool job, and not just to make myself great, let other people very uncomfortable. Over time, it will be isolated, it's not a single game, but a repeated game, the best strategy is to win.
They do their own faster, but the brothers next task seems relatively heavy, while they do not lend a helping hand. Differences inevitably lead to different results, but for the team, not just the individual needs of individual achievement skills, but team collaboration to produce high efficiency and high quality. This process is also a repeated game, there is no guarantee that they have in times of difficulties, do not you want someone a hand together to solve the problem? Rentongcixin, Xintongcili, mutual support, which is fighting as a team charm.
8, not timely feedback progress.Things most taboo is anticlimactic, in most cases will die a natural death, nothing. The best practice for the task assigned is timely reporting of risk exposure difficult, timely reporting of progress, even if such work is not up to the goal, the whole process is obvious. Leaders fear the practice is issued after the task, the following also ensure the completion of the task, but really pay to live, put a bunch of this or that reason, the task is not complete. When you are not sure when a surprise to the leadership, timely reporting progress, and finally get free only scared, too late.
8, hand party. To the forum, a community where you can see just a bunch caught out, the purpose is to achieve their goals faster, but lack the ability or lazy, and completely dependent on others, it is best he needs mentioning, you deliver even if done to a thing. In another case, after a problem occurs, without in-depth analysis, directly to someone else to solve. Long-term hand without actually started practice, the operational capacity of natural decline, since only taste bitter. There are words: you can be as lazy as a pig, but not like a pig, like, lazy peace of mind. This is a sore point.
9, spare time without recharging. After work basically in free-range state, the basic work rest on our laurels, or barely able to cope with, work basically no big improvement, not bad but not too good. Before say "you only stop the run, in order to stay in place!", Highlights the block changes of the times, is not a big fish small fish, but fast fish eat slow fish, particularly in some life, slower than the pace of work second and third tier cities. The gap between people is not opened within eight hours, play a decisive role but outside of work, the so-called time outside of poems. Technology updates iteration quicker pace than any era, than we good people are still hard, we saw no reason to lazy it?
10, can not take the initiative to push things forward. The initiative to do something with the passive acceptance to do something, the mood is not the same, work efficiency is vastly different. Active people have more growth opportunities, whereas in continuous passive in response to someone else's mission, which has nothing to do with the level in the hierarchy. If you are in a high-level task can not take the initiative to advance forward, I believe in this job will not stay too long.
11, sharing technology exchange will just listen to it.In particular, multi-tier cities such opportunity, if you will, one day catch several games. Although it is to share with others, if not properly utilized, only attending the left, the result is almost zero. Be familiar with prior history lecturer, sharing content, listening with his own questions, but not at the record books, Q & A session will be thrown doubt point, to know people sharing session, the sharing will continue the discussion after the addition of micro-channel group will wait etc., can play a better share performance will. Do not allow to participate in technology sharing will be a mere formality.
12, multi-scene can not switch roles. Just Getting Started, engrossed in the development is still possible, with the increasing age of personal responsibility will change, and then have time to concentrate on a single piece of monolithic matters little chance more time is fragmented slice, faced with different colleagues, customers, leadership, partnerships, and others, if you can not respond quickly to change, can only be used to describe cope exhausted, rational work going. You need to quickly switch roles, into different environments, can be abstract, but also with technology, to grasp the overall situation, but also the details in depth, this treatment from the problem can be handy, rapid growth.
13, easy to get into the details. Or very tangled details, the opposite side will lead to lack of global view, and occasionally a dead end. Over the pursuit of the perfect details of someone who is a perfectionist, perfect when the facts can not exist in real life. Into details without knowing ranging from project delays, while in missed market window period. Hold a degree is very important, if needed this situation, it is necessary to sacrifice local imperfections.
14, does not intervene in the development of other matters outside the mission. Temporary assignments inevitable, especially entrepreneurial team, but there is no clear division of job boundaries, if necessary, direct the top, the goal is to get things done. Focus only on development tasks that something is clearly not enough to do the job skills to a higher reserve, it does not take up too much time if whatever it is recommended to exercise it. Experience are considered their own, grow too, who can take away.
15, do not pay attention to record critical nodes retained.Mobility, business software changes to ongoing maintenance is a challenge, head record alone, is clearly unrealistic. Many of my friends say that the code has ah, look at the code on the line. If you must take the code to say something, I can only say you are too immature, design documentation, flow charts, data tables aid in the understanding of these things is it simply decoration? In particular, some complex business process design, complex algorithm design, difficult BUG solutions and so on. Although Agile development does not advocate everything necessary documentation to prevail, but it is important to retain the necessary documents, forms can be limited.
16, do not want to go with the leadership of the past. Is there such an experience: everything leadership at the occasion, the atmosphere are more dignified? The people are let go? In fact, this is a employment relationship at play. Staff and leadership is not in a state of mutually beneficial cooperation, which is the "Alliance," a book mentioned partnership. If you have not seen, I suggest you buy and read it. With the leadership to go near any harm you? Not lazy is true. In my opinion, he becomes friends with executives is a career useful things. Can make you a better understanding of leadership, can stand higher than their dimensions to treat people, can be exposed to a lot of higher-level contacts, etc., etc., etc., there are many, to be to be explored. If given the opportunity, do not hide away.
17, the lack of financial awareness. IT salary levels than the average person in terms of the industry is quite substantial, but if you do not pay attention and increase the value, then the moon is full presence, coupled with consumer credit is so popular, Cary figure will only increase not decrease. Coupled with inflation, relying on savings, it is actually a process of depreciation of assets. So clever melon head, to reach some stocks, bonds, funds, P2P, real estate and other investment operations of the subject, or necessary, you want to achieve financial freedom? Then go back to sleep to improve your income [passive income] it.
18, frequent transformation industry.Information technology has tentacles deep into all walks of life, but a large difference between the industry and the business sector, some industries and high barriers, highly professional, such as medicine, finance and so on. Technical services in business, if you are adaptable, the ability to digest the strong no harm, but in most cases is not new to a depth over, if you can not maintain continuity, it is likely that concludes this . The actual process of business operation of the core points need to master certain accumulation, which requires precipitation for many years to achieve in the industry, such as focus on the financial sector, but which also involve insurance, securities, banking and other types of business scenarios, each of which is complicated and varied, if the frequent change in the industry, not to mention basically precipitation, with the growth of work experience, their competitiveness did not mention lifting, missed the ability to become business experts.
19, constantly chasing new technology, because it is not applied in practice, leading quickly forgotten. Technological upgrading of iterations is far from a poor person's life can force completion of the so-called finite life skills to master the infinite is just a beautiful thing, but unrealistic. Taking into account the specific technical maturity, application scenarios and their degree of match practice, only those technology stack in order to effectively into practice faster and deeper grasp. Specific to their own career planning, the focus should be more, find a point, and then based on this extension point, to create their own technology ecosystem. Never to itself as a technology but have plenty of unrelated high degree of Swiss Army knife, much less competitive skills.
20, when communicating with others poor, can not solve the problem of the spirit of thinking to solve the problem. "Well, well, well, do not say, stopped, and I do not fight with you, as you say to, there is a problem you are responsible." If the target is in line to solve the problem to solve the problem, we can present the facts and arguments, the advantages and disadvantages of various options exist on the next plane, and then we re-objective sake of discussion, come up with the same solution. You will often encounter some people when discussing the issue, the final result is a party no longer willing to debate and compromise, but compromise is not convinced that this is a direct refuse to work, rather than solving the problem.
21, tracking is not complete, lead to naught.If people owe a lot of money, surely you will in any case leave no stone unturned to recover this money back. It is unfortunate that, in their daily work, we track a task when Queyuanburu account so hard to recover, and then follow along with a no then. One can imagine that if all this state, your project schedule, your sales target, how to reach your market share, imagine that one day you become senior leadership, your men are brothers in this state tracking problem, and that you really have a lot of trouble all else fails.
22, failing to act specification. This is very common, mouth set, another set, that is, when Knowledge and Behavior action. Is actually easier said than done, is not self-monitoring, self-regulation does not, the people will become lazy. "This on-line version anxious, first function realization Besides, there is time to come back reconstruction optimization" is not often heard such a routine, they have reconstructed it afterwards? Afterwards you have to look at what bad code? If something out of the emergency after the sound is also permitted, afraid of a pretext, and afterwards abandoned to the winds.
But wanted to delay action. Everything is ready and we have to have to act, when in fact many will never be complete when the first move to say, in the process of re-action is sure to encounter problems, to solve it wants. Otherwise, some just in front of struggling, there will be poetry and distant. "Success" in speaking, want to succeed and be successful are two different things, although one word.
You can not learn from the strengths of others. He said writers who, in fact, the IT sector also has a contempt chain, we are always consciously or unconsciously see practicing with this contempt chain. Even grasshopper same time there is a chain of mutual dislike. But learning this stuff, to be open-minded, can not say you could not understand him, she refused him everything, even if it is good, it really is against themselves. You have people dislike you? You find him something that you do not have it?
23, it will be a lot of development languages, but not all proficient.Daniel does not rule out to do, most people's words, so you write a resume, it really does not make people look at the high, it is easy for others to leave what will be, and basically nothing will impression. Do not chase the speed of new technology, technology iterations faster than you learn more, do not tend to seek more in-depth, beyond the fur, and the application of a technology is not to write a "hello world" even if the application to real business scenes, solve practical needs in order to play a technology pain points of the true.
24, a single software development skills. In addition to encoding software life cycle to achieve, as well as requirements analysis, system design, test, deploy, publish on-line, operation and maintenance operations, etc., only that piece of code is too narrow, especially after long hours staring, limitations will increasingly more obvious. Development language is a tool, not a hammer the same thing with a hammer. To improve their adaptability skills have extension line, behind the career path will be broader, but not limited to technical line. The pursuit of full stack is not wrong, but should be appropriate and can not be blind to resume on a few lines, to dabble seemingly useful, but it does not actually use the technology.
25, lack a sense of crisis. Last year's hot topic of the event is the resurgence of a 40-year-old IT person to commit suicide. The snowball outbreak of the "midlife crisis" big discussion on this issue. Eight zero midlife crisis is not open around the problem, Eileen Chang in "Eighteen Springs" Lane said, "after the middle-aged men, often feel lonely, because he opened his eyes, surrounded by his people to rely on , but he can not rely on the people. "the phone screen before you thought about this problem?
--------------------- 
Author: Armymans 
 Original: https: //blog.csdn.net/qq_43652509/article/details/91838682