Programmers' Personal Work Summary and Self-evaluation

Programmers' Personal Work Summary and Self-evaluation

Personal summary and plan complement each other and should be based on personal plan, which is always formulated on the basis of personal summary of experience. Below I collected the personal work summary and self-evaluation of programmers for your reference!

The first article: Programmer's personal work summary and self-evaluation.

Hello, everyone, my name is xxx. I am cheerful, willing to communicate with others, honest, upright, self-motivated, and have a strong learning ability. My work in the school league club has further strengthened my organization and coordination ability, and I have a strong sense of social responsibility.

My computer skills: programmer language skills: English (general); Mandarin (standard) familiar with windows, able to skillfully use office software such as word and powerpoint; Familiar with C, c#, html, xml, understand data structure (C), software engineering, C, c++, java, ajax. Mastering c# language skillfully. Familiar with development tool vs.netxx/xx; And use b/s to develop a property network management system. Engaged in the development of educational software in the company.

I used to set up a property management system.

Software environment: windows system development environment: vs.net XX (C #) SQLXX project description: This system mainly includes two parts: the front desk mainly realizes administrator login, property management personnel information, announcement information, household arrears information, household complaints, household repairs, arrears inquiry, etc. The backstage mainly manages this website, which mainly realizes the management of accepting property information, property management, announcement management, basic setting and system maintenance.

XX years -XX years? Excellent league member? Title? A third-class scholarship? 、? First place in the school basketball competition? XX years -XX years was rated as? Director of the Propaganda Department of the General Branch of the Student Union? 、? First place in the school calligraphy competition?

XX years -XX years? Excellent student cadres? 、? Excellent team work?

Through the above self-evaluation, I can better understand myself and my strength in all aspects. As an experienced computer programmer, I am proud of myself.

Part II: Programmers' personal work summary and self-evaluation.

This year, I experienced three changes, from school to enterprise, from students to employees, from theory to practice. Around these three changes, I always maintain a good attitude and grow step by step.

I started working in xxx company in June of 20xx. In the first few months of work and study, under the guidance and care of leaders and colleagues, I learned professional knowledge, asked my predecessors for experience and learned professional skills from my colleagues. It was in this process that I realized my own shortcomings, the strength and charm of the team, and I quickly realized and integrated into this team, which made a good start for my future work.

During this working time, I made a relatively difficult project xxx online consulting system. Why is it difficult? Because I haven't done this project before, I have asked all my friends and searched the internet, but I haven't found a solution. Then I looked through the books and searched the Internet. Many things happen. Finally, I found a small example of a chat room, but the function is far from perfect. So I studied this example bit by bit, from ignorance to gradual understanding, from ignorance of AJAX technology to skillful use. Then I started to develop it myself, and finally I developed it. Although it is not perfect and its function is not very powerful, it is the result of my efforts, and I believe it will develop stronger and more perfect in the future.

Through the internship process, I know the short-term confusion and emotional trough. With the help and care of my colleagues and personal efforts, I can successfully break through the predicament and find my self-confidence and enrichment!

Here, this is my work report and my experience during the probation period. I hope that the company leaders can comprehensively consider my work attitude, work ability and work performance according to the requirements of regular employees. I will continue to devote myself to my future work with full enthusiasm and repay the company with my efforts!

The probation period in 2008 is coming. Now I will sort out my work this year and make the following self-evaluation:

This year, I experienced three changes, from school to enterprise, from students to employees, from theory to practice. Around these three changes, I always maintain a good attitude and grow step by step.

Chapter 3: Programmer's personal work summary and self-evaluation.

Let me introduce myself first. I have been engaged in the development of ASP.NET for one year and graduated in 2009. 1 1 started to work in XX. I worked as asp before, and started to work as ASP.NET in February of XX. Due to the transformation of the company, I am now taking more than a dozen people to develop ASP.NET, mainly about the industry management software of quasi-financial industry.

Summary of personal annual work of software development programmers

. The annual summary was also written at the meeting, but it was limited to the work summary and the work plan for XX years, and there was little self-summary. So, today I made an annual summary of myself, mainly from the aspects of technology, management and life. Welcome seniors to correct me when passing by.

I studied electrical automation at school, and the program foundation is limited to some knowledge of C basic course. Later, I switched from vb and html to asp, and spent a lot of time on asp, so I was familiar with asp. Later, due to the company's business needs, I changed the development platform to asp.NET. At first, I was not very interested in ASP.NET, thinking that it was only an extension of ASP (I didn't know the three-tier architecture at that time, and the data access was all in the page! ), and later attracted several bluebirds from Peking University to finally realize the strength of ASP.NET, and gradually mastered ASP.NET through personal efforts. At the present level, I can only say that I think it is just an introduction, and I will talk about it later for various reasons.

I believe that students who have changed from process-oriented to object-oriented have a feeling that object-oriented is really awkward at first, involving attributes, especially various relationships between classes. At that time, they always wanted to pass many parameters in a process-oriented way. So I have been thinking about objects, jumping out of the concept and understanding them in my own way, gradually realizing the essence of page objects and gradually understanding the relationship between objects at different levels, 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 transmitted by a third party, some need to be visible by subordinates, and some need to be done by subordinates. Understand that object-oriented comes from reality, not a utopian theory. The relationship between these objects can be summed up as the relationship between father and son, husband and wife, leaders and subordinates, colleagues and friends. In contrast, the page process often seems to be pushed to the user at once, in which the data level and data access method are not clear. In simulated reality, it is easier to understand than object-oriented, but it is difficult to express it accurately and directly.

On the other hand, object-oriented is its design pattern, which was not clearly put forward in the previous process-oriented process. Excellent process-oriented code requires high cohesion and low coupling. Personally speaking, this is just a software development method. Technology? Theoretical summary; Is the design pattern realized? Tao? Because it expresses the relationship between specific code modules from a larger direction and a more abstract level, it can be considered that the design pattern is an experience completely summed up from practical application. There is no such term between the two, but I believe that predecessors must have used this idea and applied it to practical work. Of course, everyone will have their own? Design pattern? You can learn from the ideas of your predecessors to improve yourself, but you can't. Design pattern? And design patterns.

Specific to the implementation model of asp.net, it is not difficult to really understand its mechanism and method. Remember that b/s can't do without post or get, all autopostback and selectedindexchanged are calling forms to pass values, and the source files generated by runat=server are also ordinary html tags. Microsoft's idea of making software development easier is very good, and the times are improving. Many years ago, you wrote mis in C to prove that you are awesome. Many years later, you don't have to write in C? Student management system? 、? Library management system? That only shows that your brain is one-track-minded, and developing languages has advantages and disadvantages, because the application situation is different. Similarly, you can't compare a dagger with a cannonball, nor can you compare C with php. Programmers have a paranoid mentality, but remember that the users you face have the final say, and whether the program can meet the needs, usability, stability and cost should be put first.

There were only four people on the development team, including me. At that time, I was just running with the mentality of accepting challenges. In addition, I am more emotional and have a good team relationship. However, serious problems have gradually emerged: randomness of work, weak team spirit and sloppy working methods. In my impression, several people began to promise that the project could not be completed, and finally worked overtime until six o'clock in the morning and went to work at half past seven after a nap. Several colleagues are.

Later, with the passage of time, the problem became more and more obvious: the project could not be completed, and the company's treatment made the new employees feel worthless, so the boss complained and the employees complained, so I had to walk in the middle? Fire fighting? This period is the most tiring time for our department, but it is also the most fulfilling time. Later, my former employee told me? Never find that feeling again? This is what I can imagine. During this period, the boss trusted me very much, and the management method gave me a lot of work advice. Later, I gradually understood that management should be? Everyone makes rules to follow? , and should not? People care about people? .

It is easy for people to fall into a misunderstanding: leaders always pay attention to every employee, which often leads to employees perfunctory leadership, loose management, decreased sense of responsibility, and tight management, which leads to tension between employees and leaders. On the other hand, the limited leadership time and energy will inevitably consume a lot of energy in daily supervision and cannot be put into overall management.

So what? Set the system-set the division of labor-set the schedule? Make clear the daily rules and regulations. 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 were formulated by myself, and then your opinions were sought and finally implemented. We also encountered many problems in the middle. For example, at first, we were allowed to use qq internally. Later, employees spent more time chatting with qq, which greatly affected work efficiency. Finally, they decided to ban it. There was a lot of resistance at first (it seems that programmers like to hang a few qq in the group to get a group owner, although most of them are novices). Finally, the situation gradually improved.

In terms of project division of labor, the division of labor is clearly defined according to the technical level, and the project development plan is formulated. Because the technology was not very mature at first, many times my side strongly urged me to use barbaric methods and accompany me to work overtime if I can't finish overtime. During this time, I can feel that employees have slight complaints about me but generally recognize it.

During this period, the company recruited new employees, and the increase in personnel made me realize the importance of team management. During this period, many problems such as version control, coding specification, document management and bug management have been solved one by one. Technically, I mainly use my spare time to learn new knowledge and then carry out various trainings, mainly PS/' target =' _ blank'>；; In photoshop, css, js, sql and other aspects, on the one hand, training has improved the technical level of employees, on the other hand, I have gained the most in the process of learning and training, because at this time I have more personal requirements to think about and am deeply interested in technology, so my later work has gradually entered a virtuous circle.

Low pay, harsh conditions, long working hours and great work pressure are the biggest problems of the team. In this regard, the decision-making level of the company has serious misconceptions in some aspects, which leads to more complaints from technicians about the company. In this regard, I can only comfort my brothers around me at the cost of my wife, because I understand that the problems of the company are the same as those of the current software industry in China, and they blindly pursue the maximization of benefits, not seeking quality, but seeking speed. The whole social atmosphere has caused the unbalanced development of the software industry. There are countless companies composed of three or four development teams in China, and the living conditions of the whole programmer class can be imagined, such as crazy overtime, low code quality, high maintenance cost, poor stability and poor user experience. Of course, this situation can't escape. For individuals, any false and empty slogan is meaningless. The most important thing for programmers as technicians is their mentality. They face all kinds of problems with a good attitude, find problems, solve problems and complain when they find problems. It migrant workers? Personally, I think it people's self-positioning is the most incorrect. Imagine that a person even looks down on his career. Can he do his job well? ), the most important thing is to solve problems.

When interviewing employees, I repeatedly mentioned three points: work attitude, development potential, work ability from front to back, and mentality is the most important. Everyone in big companies wants to sharpen their heads and squeeze in, but the quota is limited, so most programmers are concentrated in second-rate and third-rate software companies. At this time, it is necessary to do a good job in personal career orientation. In my personal experience, when choosing a company, new employees often pay the most attention to salary and development potential. Programmers are a profession that can't muddle along, and their ability to work is very important, but not the most important. Work attitude is often related to their personal ideological understanding and working environment. My personal experience is that they must not be too emotional, which is not good for their work or personal development. In other words, even if you want to resign tomorrow, you have to resign today.

Employees with insufficient sense of responsibility are particularly worthy of attention. They tend to be too self-conscious and self-centered. Many times, when their work is not recognized, they feel dissatisfied and unhappy, I will take the initiative to talk to him. I know you manage a real person, he is not a machine at your mercy. People have emotions and often have knots. Find out the reason, enlighten more, and care for every member with your heart. Prepare for the worst for employees who are really not suitable for development in this team. Programmers have the same characteristics as today's college students, one is to become redundant from the favored son of heaven, and the other is to become popular in China today from a person with high IQ? It migrant workers? . On the other hand, programmers are often concentrated in men aged 20-25, and there will be a series of problems such as emotion, loss and psychological immaturity. However, people at this stage are often the easiest to communicate with and have strong plasticity. Proper guidance and reasonable methods will be a hundred times stronger than barbaric management.

?

;