Five personal work summaries for programmers

Summary refers to written materials that summarize and summarize the experience or situation in a certain stage of work, study or thought. It can promote Let's think, let's take some time to write a summary. But what are the requirements for a summary? The following is a summary of programmer work that I compiled. Welcome to read and collect it. Programmer's personal work summary 1

1. Improve yourself and take your work seriously

I just came to __ company a few months ago and I am a slightly green person. , after entering __ company, I was attracted by the working atmosphere here. I saw the hard-working spirit of employees from an excellent company. When I first entered __ company, I took over a job that was quite stressful. This position is a challenging job for me. My job is development and maintenance. The most important thing at work is to fix bugs. I repeat the same work every day. I feel that I have benefited from this kind of working status. Although My work is basically the same every day, but it is this kind of work that allows me to exercise myself. I was a graduate before I came to __ company. During this probationary period, I felt that in school There is a big difference between working in an enterprise and what you can learn in an enterprise is not like what you learn in school, and may be more applicable. This makes me very touched.

During the probation period of just a few months in __ company, I worked diligently and would not make any excuses for my work mistakes. I humbly accepted the opinions of my colleagues and I actively try to get closer to my colleagues who are outstanding in competition. In fact, it is often such small actions that will benefit me for life. Maintaining such a working habit is of great help to me. I still think so now. If I don’t know how to do it, just ask , ask one by one, knowing that I fully understand, I am constantly improving myself over time, and over time I can clearly feel my progress, especially at work, which further strengthens my attitude towards work. Careful and meticulous.

2. My own shortcomings

Sometimes I overestimate myself at work. This is a very bad habit of mine. I am too confident. This kind of personality also made me suffer a lot, and it also made me realize the disadvantages of this kind of personality. I will definitely learn from it and improve it. Programmer's personal work summary 2

I have been engaged in asp.net development for a year. I started working in November __. I was working on asp before and started working on asp.net after February __. Due to the company After transformation, I now bring more than a dozen people together to develop asp.net, mainly for industry management software in the quasi-financial industry. The annual summary was also written at the meeting, but it was limited to work summary and annual work plan, and there was less self-summary, so today I will make a special annual summary of myself, mainly talking about this year from the aspects of technology, management, and life. What a harvest, seniors passing by welcome your corrections.

I studied electrical automation in school, and my program foundation was limited to some knowledge in basic C courses. Later, I switched from VB and HTML to ASP. I spent a lot of time on ASP, and I am familiar with ASP. Later, due to the company's business needs, the development platform was turned to asp.net. At first, I was not very interested in asp.net, thinking it was just an extension of asp (I didn't know about the three-tier architecture at that time, and data access was all in the page!). Later, After recruiting a few Peking University Blue Birds, I finally realized the power of asp.net. Through personal efforts, I have gradually mastered asp.net. At the current level, I can only talk about what I feel is just a beginner. There are many reasons. I will talk about it later. More on that later.

I believe that students who have switched from process-oriented to object-oriented have a feeling: object-oriented is really a bit awkward at first, when it comes to attributes, especially the various relationships between classes. At that time, I always wanted to use process-oriented There are many ways to pass parameters.

So I kept thinking about objects. I jumped from concepts and understood them in my own way. Then I gradually realized the essence of page objects. I gradually understood the various relationships between hierarchical display, hierarchical access, and encapsulated objects. Especially the relationship between objects, such as the relationship between object a and object b. Some need to be fully disclosed, some need to be hidden, some need to be passed through a third party, some need to be visible to their subordinates, and some need to be made visible to their subordinates. Subordinates complete specific operations - isn't this an actual model of reality? It should be understood in this way. Object-oriented comes from reality. It is not a theory imagined out of thin air. The relationship between these objects can be reduced to father and son, husband and wife, Relationships between leaders, subordinates, colleagues, and friends. In contrast, the page process often seems to be pushed to the user all at once, and the level of data and data access methods is not clear. In terms of simulated reality, it is easier to get started and understand than object-oriented, but it is essentially difficult to express accurately and directly. .

Another aspect of object-oriented is its design pattern. This design pattern was not clearly proposed in the previous process-oriented process. Excellent process-oriented code requires high cohesion and low coupling. From the perspective of personal In terms of understanding, this is only a "technical" theoretical summary of software development methods; the design pattern has reached the "Tao" level because it expresses the relationship between specific code modules from a larger direction and a more abstract level. relationship, it can be considered that design patterns are experiences that are constantly summarized from practical applications. There is no such term, but I believe that predecessors must have used this idea. It comes from practical applications, and of course it must When applied in actual work, think carefully and constantly summarize that everyone will have their own "design pattern". You can learn from the ideas of predecessors to improve yourself, but you cannot design patterns for "design patterns".

Specific to the implementation model of asp.net, it is not difficult to truly understand its mechanism and methods. Remember that post or get is inseparable from b/s, and all autopostback, selectedinde-changed ...all call the form to pass the value, and add the server control runat=server to open the source file it generates, which is also an ordinary html tag. Microsoft's idea of ??making software development easier is a good one. The times are advancing, and for many years The fact that you used C to write mis in the past proves that you are very good. Many years later, if you no longer use C to write "student management system" and "library management system", it only shows that your brain is missing, and development languages ????have their strengths. The shortcomings are because they are applicable to different situations. For example, you cannot compare a dagger with a cannonball, or compare C with PHP. Programmers have a paranoid mentality, but one thing to remember is that the users you face are You have the final say on whether the program can meet your needs. Ease of use, stability, and cost should be discussed first. When I first took up the management position, there were only four people in the development team including me. At that time, I just did management with the mentality of accepting challenges. In addition, I am more emotional, and the relationship between the team was good, but seriously Problems gradually emerged: the work was random, the team spirit was weak, and the work style was reckless. What impressed me most was that a few of them began to promise that the project would not be completed, so they ended up working overtime every day until 6 a.m., and then took a nap to resume at 7:30 a.m. At work, several of my colleagues are young men of about the same age and very motivated. Later, as time went by, the problem became more and more obvious: the project could not be completed for a long time, and the company's treatment made the new employees feel unworthy. This resulted in a situation where the boss complained about the employees and the employees also complained. I was in the middle of the two points. I had to "put out the fire". This was the most tiring time for our department, but it was also the most fulfilling time. Later, the previous employee told me that "I will never feel that way again." This is what I can imagine. of. During this period, it was mainly because the boss had great trust in me and gave me a lot of guidance on work, mainly on management methods. Later, I gradually realized that management should be "everyone sets the rules and abides by them", rather than "people manage people".

It is easy to fall into a misunderstanding in people management: leaders pay attention to each employee all the time, which often ends up causing employees to be perfunctory about the leader, management is loose, employees will decline in responsibility, and management is tight. In order to cause tension between employees and leaders, on the other hand, leaders with limited time and energy must spend a lot of energy on daily supervision and cannot devote themselves to overall management.

So "customize the system-define the division of labor-define the progress" and clarify all 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 are all mine. I formulate it myself, then solicit everyone’s opinions and finally implement it. We also encountered many problems in the process. For example, we were allowed to use QQ internally at first. Later, employees spent more time chatting on QQ, which greatly affected work efficiency. Finally, we decided to ban it, and there was a lot of resistance at first (it seems that programmers like to hang up a few... I went to the QQ group to find a group leader (although most of the group members were rookies). In the end, I held many meetings to talk one by one and explain the truth, and the situation gradually improved.

In terms of project division of labor, we clearly divided the work according to the technical level and formulated the project development plan. Since the technology was not very mature at the beginning, many times I made strong demands and used barbaric methods, which made it impossible to complete the overtime work - I accompanied I work overtime. During this time, I can feel that the employees are slightly complaining about me, but overall they still approve of me.

During this period, the company recruited new personnel, and the increase in personnel made me realize the importance of team management. During this period, many issues such as version control, coding standards, document management, and bug management were solved one by one. In terms of technical level, I mainly use my spare time to learn new knowledge to recharge, and then carry out various trainings, mainly in photoshop, css, js, sql, etc. On the one hand, the training has improved the technical level of employees, and on the other hand, I myself am learning and training I got the most from the process, because at this time I have more personal requirements to think about, and I have a deep interest in technology, so the later work slowly entered a virtuous circle.

Low remuneration, difficult conditions, long working hours, and high work pressure are difficult problems in the team. In this regard, the company's decision-makers have serious wrong ideas in some aspects, which has led to increased complaints from technical staff against the company. In this regard, I can only comfort the brothers around me by trying to persuade my mother-in-law to fight, because I understand that the current company's problems are the same as the common problems in China's software industry. Blind pursuit of profits, not quality, but speed, the entire social atmosphere has caused The development of the software industry is uneven. There are countless companies in China consisting of development teams of three or four people. The living conditions of the entire programmer class can be imagined, including crazy overtime, low code quality, high maintenance costs, poor stability, and poor user experience. Of course, we cannot escape this situation. For individuals, any false and empty slogans are meaningless. The most important thing for programmers as technicians is their mentality. They should face various problems with a good mentality, discover problems, and solve them. Problems, finding problems and complaining will not solve the problems. The most important thing is to solve the problems. The three points I repeatedly mentioned when interviewing employees are: work attitude, development potential, and work ability, in order from front to back. Mentality is the most important. Everyone in large companies wants to squeeze in, but the quota is limited, so the majority The vast majority of programmers are concentrated in second-, third- and fourth-rate software companies. At this time, it is even more important to position one's career well. Based on my personal experience, new employees often value salary and development potential most when choosing a company. Programmers are a profession that cannot be messed around with. Work ability is important, but not the most important thing. Work attitude is the most important. Work attitude is often related to personal ideological understanding and professional environment. My personal experience is that you must not be too emotional. Being emotional is detrimental to both work and personal development. That is to say, even if you are tomorrow If you want to resign, you must do what you have to do today seriously and carefully.

Employees who lack a sense of responsibility for work are particularly worthy of attention. They often have too strong self-awareness and pursue self-centeredness. Many times, their work is not recognized and they feel unfulfilled and unhappy at work. I will take the initiative to talk to him. I understand: you are managing a real person, he is not a machine at your mercy. People have emotions and often have knots in their hearts. Find the reasons, enlighten them more, and care about them with your heart. every member. For employees who are really not suitable for development in this team, be prepared for the worst. The career of programmers has the same characteristics as today's college students. One is from being a favored person to being redundant, and the other is from being a person with high IQ to becoming an "IT migrant worker" popular in China today. On the other hand, programmers are often concentrated among men between 20 and 25 years old, and a series of problems such as emotionality, sense of loss, and psychological immaturity will occur. 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.

Programmer's personal work summary 3

This year's work has ended. I know that this has been a great improvement for me. As a programmer, I firmly believe that I can do it. It's better. I still have a deep understanding of it in my future study. In the future study, I hope that I can do a better job on this point. As a technician, I still do a very good job. I hope I can continue to maintain a good condition during my work this year.

In the past year of work, I still hope to do better. The company has trained me quite a lot. In this regard, I have firmly realized this. In the future work During this period, I persisted and did a lot of things well. Looking back at the end of the year, I have indeed gained a lot. I also hope that in my future studies, I will be deeply aware of this. In the past year, I have also learned a lot. I have completed a lot of work and collaborated on some projects with my colleagues in the company. During this process, I was indeed deeply aware of this. I know that I have maintained a good state in this regard. Looking back now I am clearly aware of this, and I still have a deep understanding of it through this project.

My absolute work ability needs to be constantly implemented. I feel that this is very meaningful. At the end of the year, during this process, I clearly realized that these details can be done. More in place, I feel that there will be more things that can be done well in the future. After this year's work is over, I also hope that I can do a better job. I still have a deep understanding of wanting to do a better job. , in some things, I really feel that it is very meaningful. I have further adjusted my responsibilities in all aspects at work. The company still makes a lot of judgments on my personal abilities. I believe that at this point I know myself. All aspects are very meaningful. I have to fulfill my responsibilities in the company. Of course, I also realize that my efforts are worth it. I also want to strive for more value for the company.

I am also clearly aware of my shortcomings. Although my daily work is very fulfilling, I still do not do well enough on some projects and there are some detailed problems. This is indeed what I should do. I will correct my shortcomings. In the future study, I will continue to do my responsibilities well. I should be more careful in the program work and I will make myself do better. , I am grateful for the care of the company leaders. I will definitely make better efforts in the future and strive to improve my work ability. Doing technical work makes me feel very meaningful. I will definitely do a good job in the new year. Programmer's personal work summary 4 In the past year, the software R&D department worked together as a team. Under the difficult environment of the company, I worked hard to complete all the company's work with a serious work attitude and perseverance. In software R&D, teamwork Certain achievements have been made in terms of personal growth. One year of work in the company has ended, and the summary report to the company is as follows:

1. Software development

According to the company's arrangements and project needs. Thanks to our own efforts, with the help of Manager Wu and the cooperation of the team, we have overcome many technical difficulties, increased our work experience, and gained huge profits:

1. Development of ASP.NET< /p>

I have done some development in other companies before, which did not involve the underlying layer, architecture, and page style. Through this year of training in these projects in our company, I have grown and learned a lot.

1. Gains from object-oriented languages. The current mainstream thinking in programming is objects, and everything can be represented by objects. It used to be difficult to understand these words on the surface, rather than from deep experience. Through the deepening of this ASP.NET project, we can abstract data and some external conditions into objects. These objects can be represented by objects, specifically by classes in the language. This is true in ASP.NET, C# and Java.

2. Have the ability to independently complete VB.NET knowledge. I have never done anything in VB before, and with the in-depth work this time, the fields covered this time are also very wide, and the commonly used and important ones are covered, and the blank parts in ML and practical operations are also supplemented. Through this year's development, I am competent. net and be able to complete the work independently.

3. There are some shortcomings. Through the development of C# software, localhost also discovered its own shortcomings, such as a weak grasp of basic knowledge and a lack of overall programming ideas. These need to be improved and improved in our work.

2. Database development

Database is the most commonly used technology since the project. In the past, we only knew some simple and common operations on the database. After this year's actual combat, we have accumulated some rich experience in database operations. It laid a solid foundation and accumulated experience for future work. At the same time, oracle and access databases were used in the project. This is my gain.

Advantages: Able to skillfully use database technology for development. Especially the operation of SQL database, after such a long period of accumulation, it is basically possible to reasonably design and build a new database, and at the same time, it also strengthens the understanding of the data structure of the database. Through the practice of the project, I can now skillfully use and write various SQL statements. I have mastered some methods on database optimization and SQL statement optimization, and can do some simple optimizations.

Disadvantages: Data is an advanced technology. It does not mean that you can write some SQL statements, but that you can build several databases. Becoming a good database administrator takes a long time. Aiming at your own shortcomings, you should be more exposed to and use new knowledge points in your future work and study. Enrich your experience and knowledge base.

2. Teamwork

The above successes and gains are due not only to my own efforts, but also to the support of the company. This team makes me who I am. Our team is also a pragmatic, hard-working and innovative team because our team members work hard. The software R&D team and I are a whole, and the team summary here is also my gain from this team.

Pragmatic: All tasks and work assigned by the company are done with care. No one in our team does anything other than work at work. These are all real work-related things that are beneficial to the company. I believe that under the leadership of Manager Wu, this is the case now and it will be the same in the future.

Hard work: No matter how difficult every task given by the company is, if the work is not completed we will work overtime at night and try our best to complete the day's work. If the work is really busy, in order to catch up with the schedule, we will give up weekend breaks and try our best to advance the project.

Innovation: Now when we start a project, we will conduct a discussion. Generally, we will conduct an efficiency and logical analysis and discussion to ensure that the program is correct and improve the efficiency of the program as much as possible.

Mutual aid: As long as anyone in our group has technical or other problems, we will try our best to help him. The entire project will not be held back because of one person.

Communication: We will communicate our results in a timely manner during the project, especially some targeted technical issues. This saves a lot of time on repeated research, which is a considerable amount of time.

As long as I know what I know and understand in communication, I will not be stingy. I will actively communicate with you. My team's famous saying is "If people are strong, the team will be strong; if people are weak, the team will be weakened."

3. Personal Growth

I have really improved a lot through the training and learning in the company for almost a year. No matter in terms of technology or work, I am not like before. What I learned in the company enabled me to grow rapidly.

Technically: Both the language and the logic of doing things have been greatly improved. Now in the software team, I can complete part of the work independently and assume my own responsibilities. Programmer's personal work summary 5

Time flies, and a year's work will soon become history. As the New Year's bell approaches, we bid farewell to the fruitful 20__ and welcome it with enthusiasm. The coming 20__ year. At the end of the year, I would like to summarize the work I have done in the past few months since I came to the company, analyze the gains and losses at work, and report as follows:

20__ In June, I came to Beijing, the sacred place I longed for, with curiosity and joy. This is my first goal after graduation, to come to Beijing for development. I left the original field where I went to school and stepped into Beijing with my classmates.

To put it mildly, I am very lucky in my technical career. Of course, this is compared to my classmates who stayed behind to find jobs locally. Faced with high tuition fees and cruel social reality, it is still difficult to choose this major for employment. , after working in Zhongguancun, Beijing for a few months, I was lucky enough to find my first job in life, working on Java programs. That is to say, come to our company - Beijing Lianhe Xingchen.

When I came to your company, I got a job after learning half of MVC and SSH. I feel very lucky that I also took on the first project, which I can develop independently. Here, I can finally put what I have learned to use. From a technical point of view, my keyword in 20__ is SSH, followed by Hibernate.

The past few months have been uneventful. I have learned a lot, including frameworks, MySQL databases, etc., but they are all superficial and can only be mastered and used proficiently. First of all, programmers should remember the first experience: "Academic qualifications represent the past, ability represents the present, and learning represents the future." I personally feel that academic qualifications do not represent everything. We can learn new knowledge every day, and knowledge can Accumulate bit by bit, as long as you work hard, everything is possible. Secondly, you must determine your own development direction and formulate a feasible plan for this purpose. Don't say anything like, "I just graduated and I don't know what I might do in the future?" "Go with your feelings and do it first." Because such a point of view will imply through your subconscious mind that your behavior is doing nothing and doing nothing. Keep working in technology and become an expert in the future? Go towards management and become a professional manager? Familiarize yourself with the industry and field first, and then stand on your own in the future? Or should you hang around in the industry first and change careers to do something else in a few years? This is very important. This is a question worth pondering for you. It will determine what you do in the past few years or ten years to "do the right thing!"

In a software development team, technology is not everything, but Nothing is impossible without technology! In a technical team, technology and character are equally important, and of course appearance is also more important. In a software project team, technical level is an important weight to be valued and respected. Whether you are doing ERP, management, system analysis, design, coding, or product management, testing, documentation, implementation, and maintenance, you must have a technical foundation. But if you don't have this foundation, you will never be qualified for your job. Make a detailed study plan for your own software development expertise, and pay attention to timely revisions and adjustments (software development technology changes too fast). Please keep in mind: "If a software developer has not updated his knowledge in 1 or 2 years, then he no longer belongs to this industry."

Don't tell yourself that you don't have time. Time is like water in a sponge. Learning more skills will not hurt us. Our work comes from learning, relying on daily learning and communication. Obtaining books in life is the ladder of human progress. For software This is especially true for developers. My project manager often said that while you are still young, spend a few dollars to buy books and read them. Books are the most effective way to learn knowledge. Don't expect too much to meet "extraordinary experts" at work and never tire of it. teach you. Only by turning books into your own wisdom through self-study can you truly possess it. Don’t limit yourself to superficial use of a technology, even if you only use it once or twice occasionally.

For a programmer, try to learn relevant knowledge points in his field, understand each platform, and learn about programs such as JavaEE, J2ME, JavaSE, VB, VCC#, and C++. Try to understand them. Although the routines of the programs are basically the same, each has its own merits. I am learning Java. Of course, Java is very powerful. I love the Android system produced by Google. Java is so awesome! I have to. Amazing, for example, when I have nothing to do, I should remind myself to learn some excellent open source products or frameworks such as JBoss, Spring, Hibernate, etc., and take the time to see how the masters abstract, analyze, design and implement general solutions to similar problems. of. Try to study the jar package and know the functions and implementation methods of each jar, so as to avoid encountering some problems that make you unclear and confused in your future work, because there are many things that you "know what they are and what they are." So”! Program in a language, but don’t let it limit your thinking.

"Code Encyclopedia" says: "Go deep into programming in a language and don't superficially read it." It is far from enough to go deep into the development of a language. Any programming language has its own reasons for existing.

Sometimes we will encounter some problems. If you simply use one method, sometimes you will not be able to solve the problem, or you will get stuck when you encounter a problem. This is what you need is inspiration. Inspiration comes from there. You can learn from the design ideas of excellent open source frameworks such as Spring, Hibernate, JBoss, etc. You can refer to the design ideas of Java's IoC and AOP. You can learn from their routines from other language programs. This is what we As the saying goes, "stones from other mountains can be used to attack jade." Develop the habit of summarizing and reflecting, and consciously refine the results of daily work to form your own personal source code library, a general system architecture for solving certain types of problems, and even evolve into a framework. When we are making programs, why do others prompt you to write comments on each method and what the code does? This is the basic key to being a good programmer. This is your basic skill. Of course, when writing Not all codes are useful codes. Some functions are universal. Why can't we package jars for them and use them in the future? Why are there so many awesome frameworks? These are all programs. It has been refined by the members to form a complete set of code structure and system, which feels very easy to use when used by others. We currently cannot write such awesome programs, but we can still form our own personal source code library.

The more open your mind is, the wider your vision will be. Don't hold on to your own technologies and achievements until they are outdated and become garbage, and then take them out and look embarrassed. Please publish your research results promptly. For example, if you see other people encountering problems on the Internet, you may have encountered this problem before. Don't hold on to your selfish mentality and say behind your back, "It's exhausting for you. Go find it yourself, sample." I suggest everyone to come to you. CSDN number, I think this stuff is very good, technical exchange. "After exchanging apples with others, everyone still has only one apple; but after exchanging ideas, everyone has two ideas." Everyone knows the truth, but how many people can really do it? My reflection is not to do it A master in technology must learn to be a good person. Improve your professional skills and become competent at your job.

Improving software knowledge and technology is only the surface of the problem. The essence is to improve one's thinking level in understanding, analyzing and solving problems. On the basis of being competent at the job, immediately dabble in professional knowledge in other fields, enrich your knowledge system, and improve your overall quality, especially those friends whose goals are not technical. This is also my goal, let’s keep up the good work!