Summary refers to a written material that summarizes the experience or situation in a certain stage of work, study or thought. It can make us think. Let's take some time to write a summary. But what are the requirements for summary? The following is my summary of the programmer's work, welcome to read the collection.
Programmer's personal work summary 1 First of all, improve yourself and take your work seriously.
I just came to _ _ company a few months ago. I am a slightly green person. After joining _ _ company, I was attracted by the working atmosphere here. I saw the spirit of hard work of employees in an excellent company. When I first entered _ _ company, I took over a stressful position, which was a challenging job for me. My job is development and maintenance. The most important thing in my work is. I repeat the same job every day, and I think this kind of work has benefited me a lot. Although the daily work is basically the same, it is this kind of work that makes me exercise myself. I was a graduate before I came to _ _ company. During this probation period, I felt the difference between schools and enterprises. What I can learn in the enterprise is not like that in school, but may be more applicable, which makes me very moved.
During the short probation period of _ _ company, I worked hard and won't make any excuses for my mistakes. I humbly accept the opinions of my colleagues, and I take the initiative to approach outstanding colleagues. In fact, it is often such a narrow move that will benefit me for life. Maintaining such work habits will be of great help to me. I still think so. I will ask them one by one until I know that I fully understand them. I am also constantly improving myself, and I can obviously feel my progress after a long time, especially at work, which has strengthened my attitude towards work and is careful and meticulous.
Second, its own shortcomings.
Sometimes I overestimate myself at work, which is a very bad habit of mine. I'm too confident. After work, this character also made me suffer a lot and made me realize the disadvantages of this character. I will definitely learn from it and keep improving.
Programmer's Personal Work Summary 2 I have been engaged in ASP.NET development for one year. I started working in June165438+1October, and started working in ASP.NET in February _ _ _. 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. The annual summary was also written at the meeting, but it was limited to the work summary and the work plan of the year, and there was little self-summary. So I made an annual summary of myself today, 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 only a theoretical summary of software development methods. Design pattern has reached the level of Tao, because it expresses the relationship between specific code modules from a larger direction and a more abstract level. It can be considered that design pattern is a kind of 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. It must be applied to practical work. After careful consideration and continuous summary, everyone will have their own "design mode" that can be used for reference.
Specific to the implementation model of asp.net, it is not difficult to really understand its mechanism and method. Remember, b/s can't be separated from post or get. All autopostback, selected INDE-changed ... call the form to pass the value, and the server control of runat=server opens the source file it generates, which is also an ordinary html tag. 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 no longer write "student management system" and "library management system" in C, which only shows that your brain lacks one track-minded, and developing languages has its own advantages and disadvantages, because the suitable occasions are different. Similarly, you can't compare a dagger with a cannonball, or 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. When the management just stepped onto the management team, there were only four people on the development team, including me. At that time, I just managed it with the attitude 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, so they finally worked overtime until 6: 7: 30 in the morning, and several colleagues all went to work. Later, with the passage of time, the problem became more and more obvious: the project could not be completed, and the treatment of the company made the new employees feel worthless, so the boss complained and the employees complained. The middle two points are to "put out the fire", which is the most tiring but also the most fulfilling one for our department. Later, the former employee told me that "I will never find that feeling again", which 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 abide by", not "people manage 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 of employee responsibilities, strict management, and tense relationship 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 "set the system-set the division of labor-set the schedule" and make all the daily rules and regulations clear. During this period, except for 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 everyone's opinions were solicited 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 asked me to use barbaric methods, and I couldn't finish overtime-I accompanied overtime, and I could feel that the employees complained a little about me but generally recognized me.
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. On the technical level, I mainly use my spare time to learn new knowledge and then carry out various trainings, mainly photoshop, css, js and sql. On the one hand, training has improved the technical level of employees. On the one hand, I gained the most in the process of learning and training, because at this time I asked for more thinking and was deeply interested in technology, so my later work slowly entered a virtuous circle.
Low pay, hard conditions, long working hours and great work pressure are the long-standing problems in the team. In this regard, the company's decision-makers have serious misconceptions in some aspects, which leads to more complaints from technicians about the company. In this respect, I can only use my wife's value to comfort my brothers around me, because I understand that the company's problems are the same as those of the current software industry in China, blindly pursuing profits, 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 to face all kinds of problems with a good attitude, find problems, solve problems, and find that complaining can't solve problems. The most important thing is to solve the problem. 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 college students today. One is to become redundant from the favored son of heaven, and the other is to become an "it migrant worker" in China today from a person with high IQ. 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.
Programmer's Personal Work Summary 3 This year's work is over, and I know it has been greatly improved for me. As a programmer, I firmly believe that I can do better, and I have a deep understanding in my future study. In the future, I hope I can do better in this respect. As a technician, I have done a good job, and I hope I can continue to maintain a good state in my work this year.
In the past year's work, I still hope to do better, and the company has trained me a lot. In this regard, I am firmly aware of this. In the future work, I insist on doing a lot of things well. At the end of the year, I really gained a lot in retrospect. I also hope that I can deeply realize this in my future study. In the past year, I also finished a lot of work by myself. I have also worked with my colleagues in the company on some projects. In the process, I really realized this. I know I have been in good shape in this respect. In retrospect, I am clearly aware of this, and I still have a deep understanding through this project.
I think it is very meaningful to constantly implement my absolute working ability. At the end of the year, in the process, I clearly realized that these details can be done more in place. I think there will be more things to do in the future. After this year's work, I also hope I can do my work better. I still have a deep understanding. I really feel good about some things. At work, I further adjusted my responsibilities in all aspects. The company has made a lot of judgments about my personal ability. I believe that I know that all aspects of myself are very meaningful. I do my duty in the company. Of course, I also realize that my efforts are worthwhile, and I also want to strive for more value for the company.
I am also very aware of my own shortcomings. Although my daily work is very substantial, there are still some projects that are not well done and there are some details. This is really what I should adjust. I will correct my shortcomings. In the future study, I will continue to do my duty well and be more careful in the procedural work. I will make myself do better, and thank the company leaders for their concern. In the future, I will definitely work harder to improve my working ability. Doing technical work makes me feel very meaningful, and I will do it well in the new year.
Programmer's personal work summary 4 In the past year, software R&; D department unites and cooperates. In the difficult environment of the company, I worked hard to complete all the work of the company with a serious working attitude and indomitable spirit. In the software R&; D, teamwork and personal growth have achieved certain results. One year's work in the company has ended, and the summary report to the company is as follows: 1. Software development.
According to the arrangement of the company and the needs of the project. Thanks to our own efforts, with the help of Wu Jingli and the cooperation of the team, we have overcome many technical difficulties, increased our work experience and gained rich profits:
Development of 1 ASP.NET
I have done some development in other companies before, which does not involve the bottom layer, architecture and page style. Through the training of these projects in our company this year, I have grown up and learned a lot.
First, the harvest of object-oriented language. The mainstream idea of current programming is object, and everything can be represented by object. It was difficult to understand these words on the surface before, rather than from in-depth experience. Through the deepening of this ASP.NET project, we can abstract data and some external conditions into objects, which can be represented by objects, especially by classes in the language. This is true in ASP.NET, c# and java.
Two, have the ability to independently complete the knowledge of VB.NET. I haven't done vb work before, and this in-depth work has covered a wide range of fields, including common and important, and supplemented the blank parts in the actual operation of _ML and _. Through this year's development, I can be competent. Net, and can finish this work independently.
Third, there are some shortcomings. Through the development of c# software, localhost also found its own shortcomings, such as weak grasp of basic knowledge and lack of overall programming ideas. These all need to be improved and improved in the work.
2. Database development
Database is the most commonly used technology since this 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 operation. It has laid a solid foundation for future work and accumulated experience. At the same time, I used oracel and access database in the project, which is my harvest.
Advantages: Able to skillfully use database technology for development. Especially the operation of sql database, after such a long period of accumulation, a new database can be designed and constructed reasonably, and the understanding of the data structure of the database can be strengthened at the same time. Through the practice of the project, I can now skillfully use and write various sql statements. I have mastered some methods about database optimization and sql statement optimization, and I can do some simple optimization.
Disadvantages: Data is an advanced technology, not that you can write some sql statements, but that you can build several databases. It takes a long time to be a good database administrator. In view of their own shortcomings, in the future work and study, more contact and more use of new knowledge points. Enrich your experience and knowledge reserve.
Second, teamwork.
The above success and harvest, in addition to their own efforts, but also the support of the company. This team made me. Our team is also a pragmatic, diligent and innovative team, because all our team members work hard. Me and software development; Team D is a whole, and the team summary here is also my harvest in this team.
Pragmatic: the tasks and work assigned by the company are done with heart. No one in our team has done anything outside of work at work. These are all real things related to work and beneficial to the company. I believe that under the leadership of Wu Jingli, this is the case now and will be the case in the future.
Struggle: 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 finish the work of the day. If the work is really busy, in order to catch up with the progress, we should give up the weekend break and advance the project as far as possible.
Innovation: Now, when we start the project, we will discuss it. Generally, we will analyze and discuss efficiency and logic to ensure the correctness of the program and improve the efficiency of the program as much as possible.
Mutual assistance: As long as anyone in our group has technical or other problems, we will try our best to help him. The whole project will not be delayed because of one person.
Communication: We will communicate our gains in time during the project, especially some targeted technical issues. This can save a lot of time for repeated research, which is considerable time.
In communication, as long as I can, I understand, I will not be stingy. I will take the initiative to communicate with you. My team's famous saying "Strong group is strong, weak group is cut".
Third, personal growth.
After nearly a year's training and study in the company, I have really made a lot of progress, both technically and at work. What I learned in the company made me grow rapidly.
Technically, both language and logic have been greatly improved. Now in the software team, you can do some work independently and take on your own responsibilities.
Programmer's Personal Work Summary 5 Time flies, and a year's work will soon become history. As the New Year bell approaches, we reluctantly bid farewell to the fruitful 20__ years and warmly welcome the coming 20__ years. Summarize the work at the end of this year and analyze the gains and losses of my coming to the company in the past few months. Now I report as follows:
In June, 20__, I came to Beijing, the holy land I yearned for, with a curious and cheerful mood. This is my first goal after graduation, to develop in Beijing. I left the original school and stepped into Beijing with my classmates. To put it mildly, my technical career is still very lucky. Of course, this is relative to my classmates looking for a job in the local area. Faced with high tuition fees and cruel social reality, it is still difficult to choose this major for employment. After a few months in Zhongguancun, Beijing, I was lucky to find my first job as a Java program. That is to come to our company-Beijing United Chen Xing Company.
I came to your company to learn MVC and SSH, and found a job. I feel lucky to have undertaken the first project, and I can develop it independently. Here, I can finally apply what I have learned. From a technical point of view, my key word for 20 years is SSH, followed by Hibernate.
I have learned a lot in recent months, such as framework, Mysql database and so on. But it's all in the fur, and I can use it skillfully. First of all, programmers should remember the first lesson: "Education represents the past, ability represents the present, and learning represents the future." Personally, I don't think education is everything. We can learn new knowledge every day, and knowledge can be accumulated bit by bit. Anything is possible as long as we are willing to work hard. Secondly, we should determine our own development direction and make feasible plans for it. Don't say "I just graduated and I don't know what I might do in the future?" Follow your heart and do it first. Because such a view will imply through your subconscious that your behavior is idle and mediocre. Have been doing technology and become an expert in the future? Go to management and become a professional manager? Be familiar with the industry and field first, and then stand on your own feet? Or do you want to stay in the industry for a few years before switching to something else? This is very important. This is a question worthy of your deep thought. It will determine what you are doing these years and ten years. . "
In the software development team, technology is not everything, but without technology, it is absolutely impossible! In a technical team, technology is as important as personality, but appearance is more important. In the software project team, the technical level is an important weight that people attach importance to and respect. Whether doing ERP, management, system analysis, design coding, or product management, testing, documentation, implementation and maintenance, we must have a technical foundation. But without this foundation, you can't do the work. Make your own learning plan for software development expertise in detail, and pay attention to timely correction and adjustment (software development technology changes too fast). Remember: "If a software developer doesn't update his knowledge within 1 or 2 years, in fact, he doesn't belong to this industry."
Don't tell yourself that you have no time. Time is like water in a sponge. We can't lose ourselves by learning more skills. Our work comes from learning, that is, through daily study and communication, getting books in life is the ladder of human progress, especially for software developers. My project manager often says, spend a few dollars on books while you are still young. Books are the most effective way to learn knowledge. Don't expect to meet "foreign experts" at work and take pains to teach you. Only through self-study can we turn a book into our own wisdom and truly own it. Don't be limited to the superficial use of a technology, even if it is only used once or twice occasionally.
For a programmer, try to learn the relevant knowledge points in his field, understand all platforms, such as JavaEE, J2ME, JavaSE, VB, VCC#, C++, and try to understand them. Although the routines of the program are basically the same, they also have their own advantages. I study Java, of course, Java is very powerful, and I love the Android system developed by Google. I have to wonder, 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 and Hibernate, and take the time to see how the masters abstract, analyze, design and realize the common solutions to those similar problems. Try to study the jar package and understand the function and implementation method of each jar, so as not to encounter some confusing problems in the future work, because you know a lot and know why! Program in a language, but don't be bound by it. "Code Encyclopedia" said: "Go deep into a language programming, don't be superficial". The in-depth development of a language is far from enough, and any programming language has its own reasons.
Sometimes we encounter some problems. If you use only one method, sometimes you can't solve the problem or get stuck in it. This is what you need and inspiration. The inspiration comes from there. You can learn from the design ideas of excellent open source frameworks such as Spring, Hibernate and JBoss. The design ideas of IoC and AOP can be used for reference in Java, and their routines can be used for reference in other languages. This is our inspiration. As the saying goes, "stones from other mountains can attack jade." Develop the habit of summarizing and reflecting, consciously refine the daily work results, form your own personal source code library, solve some problems in the general system architecture, and even evolve into a framework. When we are developing a program, why should others prompt you to write comments on each method, indicating what this code is for? This is the basic key to being a good programmer, and this is your basic skill. Of course, not all of them are useful codes when writing codes, and some functions are universal. Why can't we package the jar for him and use it later or in the future? Why are there so many awesome frameworks? These are all refined by programmers, forming a set of code structure and system, which is very easy to use when people use it. We can't write such a great program at present, but we can still form our own personal source code library.
The more open-minded you are, the broader your vision will be. Don't cling to your own technology and achievements, wait until it becomes obsolete and rubbish, and then make a fool of yourself. Please publish your research results in time. For example, if you see other people encounter problems online, you may have encountered this problem before. Don't be selfish and say, "I'm exhausted, find it yourself, demo." I suggest you go to your CSDN number. I think this thing is very good, technical exchange. After we exchange apples with others, everyone still has only one apple; But after the exchange, everyone has two ideas. "Everyone knows the truth, but how many can really do it? My reflection is not to be a technical expert, but to learn to be a man. Improve your professional skills and be competent for the job.
Improving software knowledge and technology is only the surface of the problem, and the essence is to improve one's ideological level of understanding, analyzing and solving problems. On the basis of being competent for the job, immediately dabble in other fields of professional knowledge, enrich their knowledge system and improve their overall quality, especially those friends whose goal is not technology. This is also my goal, make persistent efforts!