Programmer's personal annual work summary
First self-introduction, I am engaged in asp.net development for one year, 09 graduates, started work in November XX, before doing asp, XX year after February began to do asp.net, due to the company transformation, now with more than a dozen people Engage in asp.net development, mainly about the industry management software in the quasi-financial industry. The annual summary was also written at the meeting, but it was limited to the work summary and the XX year work plan, and the self-satisfaction was less. Therefore, today I am doing my own annual summary, mainly talking about technology, management and life. The harvest, the seniors passed by and welcomed a lot of corrections.
Technology I learned electrical automation in school, the program foundation is limited to some knowledge of the c-based course, and later changed from vb, html to asp, spent a lot of time on asp, familiar with asp, and later due to the company's business needs, Turning the development platform to asp.net, I started to be not very cold on asp.net, thinking that it was a little expansion of asp. Later, I recruited a few Beida Jade Birds and finally realized the power of asp.net. After personal efforts, it has gradually I have mastered asp.net. At the current level, I can only say that I personally think it is an introduction. The reasons are many, and I will talk about it later.
I believe that from the process-oriented to the object-oriented classmates have a feeling: object-oriented start is really a bit awkward, involving attributes, especially the various relationships between classes, then I want to use the process-oriented parameters to pass on many aspects. So I always think about the object, jumping from the concept, and understanding it in my own way, I gradually realized the essence of the page object. The relationship between hierarchical presentation, hierarchical access, and encapsulation objects gradually understood. In particular, the relationship between objects, such as the relationship between object a and object b, some need to be completely open, some need to be hidden, some need to be passed by third parties, some need to be visible to their subordinates, some need to let subordinates To complete the specific operation - is this not a realistic model of reality? It should be understood that object-oriented comes from reality. It is not a theory that comes out of the air. The relationship between these objects can be reduced to the relationship between father and son, husband and wife, subordinates, colleagues, and friends. In contrast, the page process tends to be pushed all the way to the user. The data and data access methods are not clear. In the simulation reality, it is easier to understand than the object-oriented, and it is difficult to express it accurately and directly. .
On the other hand, object-oriented is its design pattern. In the previous process-oriented process, this design pattern is not clearly proposed. The code for excellent process requires high cohesion and low coupling. From the personal understanding, this is only A theoretical summary of the "technique" of the software development method; the design pattern is at the level of "dao", because it expresses the relationship between specific code modules from a larger direction and a more abstract level, and can be considered as a design pattern. It is a kind of experience that is completely summed up from the actual set. There is no such term between them, but I believe that the predecessors must also use this kind of thinking. It is applied from the actual, of course, it should be applied to the actual work, seriously Thinking constantly sums up everyone will have their own "design mode", you can learn from the ideas of the predecessors to improve themselves, not to design patterns for the "design mode."
Specific to the implementation model of asp.net, the mechanism and method to truly understand it is not difficult to understand, remember that b / s can not be separated from post or get, all autopostback, selectedindexchanged ... are to call form value With the server control of runat=server open the source file generated by it is also a normal html tag, Microsoft's idea of making software development easier is very good, the times are moving forward, many years ago you used c to write mis Prove that you are very bullish. After many years, you are not using c to write "student management system" or "library management system". It only shows that your brain has less than one rib. The development language has advantages and disadvantages because they Applicable occasions are different, similar to the dagger can not be compared with the cannonball, can not take c and php ratio, the programmer has a paranoid mentality, but one thing to remember, the user you face has the final say, the program Whether it can meet the needs, ease of use, stability, and cost should be first placed in an important position to talk about.
At the beginning of the management, when I was in the management position, there were only four people in the development team plus me. At that time, I just managed to accept the challenge. Plus, I have a lot of feelings. The relationship between the teams is good, but serious. The problem gradually emerged: the arbitrariness of the work, the weak teamwork, and the hard work. I was impressed by the fact that several projects that started to promise could not be completed, so I finally worked overtime every day, always at 6 am, and slept for 7:30. Going to work, a few colleagues are young people of the same age, full of energy. Later, as time progressed, the problem became more and more obvious: the project could not be completed, and because the company’s treatment made the new employees feel unworthy, so the boss complained that the employees complained. I was in the middle of two points. To "fire", this period is the relatively most tiring time of our department, but it is also the most fulfilling time. Later, the former employee told me that "I can't find that feeling anymore", this is what I can imagine. of. During this period, the chief executives were very trusting to me. I mainly pointed out a lot of work on the management methods. Later, I gradually realized that management should be "everyone rules to comply", and should not be "personal management."
It is easy for people to fall into a misunderstanding: when the leader goes to pay attention to each employee at all times, this often leads to the perfunctory behavior of the staff, the management is loose, the responsibility of the staff is reduced, and the management is tight, resulting in tension between the employees and the leadership. On the other hand, the limited time and energy of leadership will inevitably require a lot of energy in the daily supervision and not into the overall management.
Therefore, "customization degree - fixed division of labor - progress", clear all the rules and regulations of the day, during this period, in addition to the company's main work rules and regulations, other daily work disciplines, daily management and other rules and regulations are formulated by myself, and then seek your opinions Finally, implement it. In the middle, I also encountered a lot of problems. For example, we started to use qq internally. Later, employees used qq to chat more time, which greatly affected the work efficiency. Finally, we decided to ban it. We started to have greater resistance. In the end, we met many times and talked one by one. To clarify the truth, the situation has gradually improved.
In the division of labor, the division of labor is clearly defined according to the technical level, and the project development plan is formulated. Since the starting technology is not very mature, I have strong requirements for many times, and I use the barbaric method to complete overtime work. I am accompanying overtime. I feel that the staff complained a little about me but generally recognized it.
During this period, the company's new recruits and the increase of personnel made me realize the importance of team management. During this period, many problems such as version control, coding specification, document management, bug management, etc. were solved one by one. The technical level is mainly my personal. Use spare time to learn new knowledge charging, and then carry out various trainings, mainly photoshop, css, js, sql, etc. On the one hand, the training improves the technical level of the employees. On the one hand, I get the most in the process of learning and training, because At this time, the individual asked to think more, and my own interest in technology is relatively deep, so the post-work slowly entered a virtuous circle.
Low treatment, difficult conditions, long working hours and high work pressure are the biggest problems in the team. In this respect, the company has serious misconceptions in some aspects of decision-making, which has caused technical personnel to blame the company. In this respect, I can only To persuade the value of the wife to comfort the brothers around, because I understand that the company's problems are the same as the current problems in the Chinese software industry, blindly pursuing the maximization of interests, not seeking quality, but seeking speed, the entire social atmosphere has caused the software industry to develop unevenly. There are countless companies in the development team of three or four people in China. The survival of the entire programmers can be imagined, crazy overtime, poor code quality, high maintenance costs, poor stability, and poor user experience. Of course, we can't escape this situation. It doesn't make sense for any individual to say that any slogan is fake. The most important thing for programmers as a technician is the mentality. They face various problems with a good attitude, find problems and solve problems. The problem is that finding the problem complaining can't solve the problem, the most important thing is to solve the problem.
The three points that I repeatedly mentioned when interviewing employees are: work attitude, development potential, work ability, sorting from front to back, mentality is the most important, big companies want to sharpen their heads and squeeze in, but the quota is limited, so the vast majority Most of the programmers' comrades are concentrated in the second-rate, third-rate software companies. At this time, they should be more personally positioned. In my personal experience, new employees choose a company that tends to pay the most attention to wages and development potential. The programmer is a profession that cannot be mixed. The ability to work is very important, but not the most important. The working attitude is the most important. Working attitude is often related to the individual's ideological understanding and the environment in which the profession is located. My personal experience is never too emotional. Emotionality is not good for work or for personal development, that is, even if you are tomorrow. To resign, you must do what you are doing today with care.
Employees with insufficient work responsibilities are particularly worthy of attention. They tend to be too self-conscious and pursue self-centeredness. Many times, when work is not recognized, work is not full and unhappy, I will take the initiative to talk to him. I know: You are managing a real person. He is not a machine at your disposal. People often have emotions, have a heart, find reasons, and enlighten them to care for each member. For those who are not suitable for the development of this team, we must do the worst. The profession of programmers has the same characteristics as the current college students. One is from the pride of the sky, and the other is from the high IQ people to become the "it migrant workers" in China today. On the other hand, programmers tend to be between men and women aged between 20 and 25, and a series of problems such as emotional, sense of loss, and immature psychology will appear. However, people at this stage are often the easiest to communicate and have strong plasticity. Appropriate guidance and reasonable methods will be hundreds of times more effective than barbaric management.
Technology I learned electrical automation in school, the program foundation is limited to some knowledge of the c-based course, and later changed from vb, html to asp, spent a lot of time on asp, familiar with asp, and later due to the company's business needs, Turning the development platform to asp.net, I started to be not very cold on asp.net, thinking that it was a little expansion of asp. Later, I recruited a few Beida Jade Birds and finally realized the power of asp.net. After personal efforts, it has gradually I have mastered asp.net. At the current level, I can only say that I personally think it is an introduction. The reasons are many, and I will talk about it later.
I believe that from the process-oriented to the object-oriented classmates have a feeling: object-oriented start is really a bit awkward, involving attributes, especially the various relationships between classes, then I want to use the process-oriented parameters to pass on many aspects. So I always think about the object, jumping from the concept, and understanding it in my own way, I gradually realized the essence of the page object. The relationship between hierarchical presentation, hierarchical access, and encapsulation objects gradually understood. In particular, the relationship between objects, such as the relationship between object a and object b, some need to be completely open, some need to be hidden, some need to be passed by third parties, some need to be visible to their subordinates, some need to let subordinates To complete the specific operation - is this not a realistic model of reality? It should be understood that object-oriented comes from reality. It is not a theory that comes out of the air. The relationship between these objects can be reduced to the relationship between father and son, husband and wife, subordinates, colleagues, and friends. In contrast, the page process tends to be pushed all the way to the user. The data and data access methods are not clear. In the simulation reality, it is easier to understand than the object-oriented, and it is difficult to express it accurately and directly. .
On the other hand, object-oriented is its design pattern. In the previous process-oriented process, this design pattern is not clearly proposed. The code for excellent process requires high cohesion and low coupling. From the personal understanding, this is only A theoretical summary of the "technique" of the software development method; the design pattern is at the level of "dao", because it expresses the relationship between specific code modules from a larger direction and a more abstract level, and can be considered as a design pattern. It is a kind of experience that is completely summed up from the actual set. There is no such term between them, but I believe that the predecessors must also use this kind of thinking. It is applied from the actual, of course, it should be applied to the actual work, seriously Thinking constantly sums up everyone will have their own "design mode", you can learn from the ideas of the predecessors to improve themselves, not to design patterns for the "design mode."
Specific to the implementation model of asp.net, the mechanism and method to truly understand it is not difficult to understand, remember that b / s can not be separated from post or get, all autopostback, selectedindexchanged ... are to call form value With the server control of runat=server open the source file generated by it is also a normal html tag, Microsoft's idea of making software development easier is very good, the times are moving forward, many years ago you used c to write mis Prove that you are very bullish. After many years, you are not using c to write "student management system" or "library management system". It only shows that your brain has less than one rib. The development language has advantages and disadvantages because they Applicable occasions are different, similar to the dagger can not be compared with the cannonball, can not take c and php ratio, the programmer has a paranoid mentality, but one thing to remember, the user you face has the final say, the program Whether it can meet the needs, ease of use, stability, and cost should be first placed in an important position to talk about.
At the beginning of the management, when I was in the management position, there were only four people in the development team plus me. At that time, I just managed to accept the challenge. Plus, I have a lot of feelings. The relationship between the teams is good, but serious. The problem gradually emerged: the arbitrariness of the work, the weak teamwork, and the hard work. I was impressed by the fact that several projects that started to promise could not be completed, so I finally worked overtime every day, always at 6 am, and slept for 7:30. Going to work, a few colleagues are young people of the same age, full of energy. Later, as time progressed, the problem became more and more obvious: the project could not be completed, and because the company’s treatment made the new employees feel unworthy, so the boss complained that the employees complained. I was in the middle of two points. To "fire", this period is the relatively most tiring time of our department, but it is also the most fulfilling time. Later, the former employee told me that "I can't find that feeling anymore", this is what I can imagine. of. During this period, the chief executives were very trusting to me. I mainly pointed out a lot of work on the management methods. Later, I gradually realized that management should be "everyone rules to comply", and should not be "personal management."
It is easy for people to fall into a misunderstanding: when the leader goes to pay attention to each employee at all times, this often leads to the perfunctory behavior of the staff, the management is loose, the responsibility of the staff is reduced, and the management is tight, resulting in tension between the employees and the leadership. On the other hand, the limited time and energy of leadership will inevitably require a lot of energy in the daily supervision and not into the overall management.
Therefore, "customization degree - fixed division of labor - progress", clear all the rules and regulations of the day, during this period, in addition to the company's main work rules and regulations, other daily work disciplines, daily management and other rules and regulations are formulated by myself, and then seek your opinions Finally, implement it. In the middle, I also encountered a lot of problems. For example, we started to use qq internally. Later, employees used qq to chat more time, which greatly affected the work efficiency. Finally, we decided to ban it. We started to have greater resistance. In the end, we met many times and talked one by one. To clarify the truth, the situation has gradually improved.
In the division of labor, the division of labor is clearly defined according to the technical level, and the project development plan is formulated. Since the starting technology is not very mature, I have strong requirements for many times, and I use the barbaric method to complete overtime work. I am accompanying overtime. I feel that the staff complained a little about me but generally recognized it.
During this period, the company's new recruits and the increase of personnel made me realize the importance of team management. During this period, many problems such as version control, coding specification, document management, bug management, etc. were solved one by one. The technical level is mainly my personal. Use spare time to learn new knowledge charging, and then carry out various trainings, mainly photoshop, css, js, sql, etc. On the one hand, the training improves the technical level of the employees. On the one hand, I get the most in the process of learning and training, because At this time, the individual asked to think more, and my own interest in technology is relatively deep, so the post-work slowly entered a virtuous circle.
Low treatment, difficult conditions, long working hours and high work pressure are the biggest problems in the team. In this respect, the company has serious misconceptions in some aspects of decision-making, which has caused technical personnel to blame the company. In this respect, I can only To persuade the value of the wife to comfort the brothers around, because I understand that the company's problems are the same as the current problems in the Chinese software industry, blindly pursuing the maximization of interests, not seeking quality, but seeking speed, the entire social atmosphere has caused the software industry to develop unevenly. There are countless companies in the development team of three or four people in China. The survival of the entire programmers can be imagined, crazy overtime, poor code quality, high maintenance costs, poor stability, and poor user experience. Of course, we can't escape this situation. It doesn't make sense for any individual to say that any slogan is fake. The most important thing for programmers as a technician is the mentality. They face various problems with a good attitude, find problems and solve problems. The problem is that finding the problem complaining can't solve the problem, the most important thing is to solve the problem.
The three points that I repeatedly mentioned when interviewing employees are: work attitude, development potential, work ability, sorting from front to back, mentality is the most important, big companies want to sharpen their heads and squeeze in, but the quota is limited, so the vast majority Most of the programmers' comrades are concentrated in the second-rate, third-rate software companies. At this time, they should be more personally positioned. In my personal experience, new employees choose a company that tends to pay the most attention to wages and development potential. The programmer is a profession that cannot be mixed. The ability to work is very important, but not the most important. The working attitude is the most important. Working attitude is often related to the individual's ideological understanding and the environment in which the profession is located. My personal experience is never too emotional. Emotionality is not good for work or for personal development, that is, even if you are tomorrow. To resign, you must do what you are doing today with care.
Employees with insufficient work responsibilities are particularly worthy of attention. They tend to be too self-conscious and pursue self-centeredness. Many times, when work is not recognized, work is not full and unhappy, I will take the initiative to talk to him. I know: You are managing a real person. He is not a machine at your disposal. People often have emotions, have a heart, find reasons, and enlighten them to care for each member. For those who are not suitable for the development of this team, we must do the worst. The profession of programmers has the same characteristics as the current college students. One is from the pride of the sky, and the other is from the high IQ people to become the "it migrant workers" in China today. On the other hand, programmers tend to be between men and women aged between 20 and 25, and a series of problems such as emotional, sense of loss, and immature psychology will appear. However, people at this stage are often the easiest to communicate and have strong plasticity. Appropriate guidance and reasonable methods will be hundreds of times more effective than barbaric management.
recommended article
- Annual work summary of energy saving and consumption reduction
- Coal mill annual summary and future plans
- Summary of the annual work of the soft environment construction of the Radio and Television Bureau
- Annual summary of the director of the teaching department
- Broadcasting host annual personal work summary
- National Summary of National Assessment for National Defense Students
- School District Investigator Annual Work Summary
- Summary of the work of the Youth League Committee in 2019
- Annual assessment personal summary
- Engineering Department 2019 Annual Work Summary
- Stylistic Education Bureau 2019 Annual Work Summary
- Summary of the 2019 annual assessment work
popular articles
- Summary of the 2019 annual assessment work
- Injured sentence
- Deaf people jingle 2019
- Strong words
- English famous words
- Qq space mood phrase
- Summary of the work of the new rural instructors in 2019
- Summary of personal work in 2019
- I want to say something to the teacher.
- a good saying that loves labor
- The latest high school inspirational maxim
- Tao Xingzhi's famous sayings
- Korean swear words
- Taizai’s famous sayings
- Classical life motto
- College entrance examination inspirational quotes
- Summary of the work of the Youth League Committee in 2019
- Describe the fast time sentence 2019
- Du Yuexi's famous sayings
- Bing Xin’s famous words
- Summary of the year-end work of college students in 2019
- Teacher's famous saying
- Sad love sentence 2019
- Construction Engineering Co., Ltd. 2019 Summary
- 2014 is very touching words
- Summary of the work of 2019 old cadres
- Summary of the annual work of the department in 2019
- 2014 Corporate Annual Work Summary
- Summary of the 2019 middle school physical education teaching work
- Thanks to the friend's words 2019