5 self-inspection reports on company procedures.

# Report # Introduction The written expression in the self-inspection report should be practical and realistic, and the achievements should be affirmed. There should be no false statements and exaggerations. All matters explained by data must be true and accurate. The following is the unorganized self-inspection report of company procedures, welcome to read!

1. Company program self-inspection report.

I have been employed for one year on X, and my role and responsibilities have changed from a student who just finished an internship to an independent developer. Although I have predicted that there will be many difficulties in my work, in the actual project development, what I encountered is far simpler and simpler than I imagined. In the development process, there are endless problems. It is still a long process to meet the company's product needs and become a qualified program developer. I encourage myself to study hard and behave well every day, and I will be fine in the future. At the same time, I sincerely thank the company for providing me with the opportunity and platform for learning, and also giving me a little more confidence in the future. I. Work Review

During my first year in the company, I successively contacted the company's gps platform, smart watch positioning, comprehensive fire management system of xx Railway Bureau station, management system of xx financial office, management system of xx security office, and video monitoring system of command center, and made a corporate website for xxxx during this period. When I first entered the company, I had never touched a webcam, and I had no idea about it at all. Under the training of the company, I gradually became familiar with all kinds of cameras, and now I have xx camera development kit, so I can skillfully carry out secondary development. In my spare time, I also study hard, communicate with others, learn advanced development technology, and ask others for development technology.

Second, the main problems

1. Because I was not very familiar with the business requirements at first, during the process of analyzing and understanding the requirements to be developed, there were many cases of constant modification and rework because of the requirements. In the financial communication with xx, this question has troubled me many times. The demand of the other party is unknown, and the demand changes every time, which leads to the problem of inefficiency.

2. In the development, I used many fields that I didn't know or knew but were not familiar with. In this field, I need to keep learning.

3. In the working stage, sometimes I prefer the convenience of my own work and ignore the quantity and difficulty of other colleagues' work. How to write some functions is convenient for you. Now the company is getting bigger and bigger, and there are more and more people in our department, which is not conducive to multi-person cooperation.

4. The work organization is not clear enough, and it is necessary to prioritize; In the case of short development time and many things, there must be a detailed and clear plan, some need to be completed immediately, and some can be completed slowly. There is still a lot of room for optimization in this regard.

5. The knowledge learned is not extensive enough; In a project, many technologies are often involved. More knowledge makes you more flexible. I will strengthen my study in this field in the future.

Third, work experience.

1. At the first step of each project, we must clearly communicate with customers. Only by understanding the needs of the project can we really do it well. We need to ask our customers to provide all the information related to the project. At least one or two programmers who are familiar with the business and process need to record the requirements at any time every time we meet with them.

2. At work, a senior leader is more sure of technology and experience. He will do the task in detail, knowing in detail when and to what extent the pictures on each page or even one page are ready, so that the progress of the work can be praised in a planned and directional way and the work efficiency is very high. When cooperating with xx, xx and others, we must pay attention to the synchronization of multiple tasks to ensure that each sub-module can run synchronously.

3. It is really important to summarize our daily work, so that we can know what we have done in a planned way every day, instead of working aimlessly, so we should develop the work habit of keeping diaries, such as weekly diaries, monthly diaries and annual diaries.

4. Work is not static. Maybe one day you will go to other positions to help, so the skills of colleagues should learn from each other. Maybe one day, the company needs you to use other skills to help, so it is also important to learn from each other. Your job cannot be limited to programming.

2. The company program work self-inspection report

First, at the beginning of March, following the tide of job hunting, my classmates and I rushed to the job fair on various occasions, watching a lot of nervousness and picky during the interview, and we were still scared. Now I think about the uneasiness at the beginning, and I still have a lingering fear. However, I am lucky to meet my current leader and a group of like-minded colleagues in various choices.

Second, diligence is a good training.

Finally, I am fortunate to be a member of xx e-commerce. I am very grateful to my colleagues around me. When I first entered the technical department, because many things had not been touched before, when I humbly asked my colleagues, they were patient and generous enough to answer all my difficult questions. I am grateful for this, but I also warned myself that I should do the same to my new colleagues in the future and try my best to help them answer questions.

This is the first formal project I have just contacted in the company. I still remember that I was both excited and nervous when the manager listed us as work members and assigned corresponding tasks. I am excited that I can finally fight side by side with them, but I am nervous that I can't achieve the effect of satisfying the leaders. Fortunately, the team I belong to is really good: there are differences of opinion, even if they are red-faced, it will not affect the consistency of their relationship at all; The night before we tested the server on the project, we were doomed to be "active" and deploy various test environments in cooperation with the test. Everyone was determined to do it well. That night, a group of us worked until midnight. And that's when I feel most guilty: because there is a bug in the part of the function I am responsible for, the follow-up function can't go smoothly. That night, my palms were full of sweat and my heart was full of mixed feelings, but fortunately, with the patient guidance of the manager and the concerted efforts of everyone's Qi Xin, our project successfully entered the testing link. Only then did I know that in my work, the functions I am responsible for must be completed with good quality and quantity before the specified completion time to prevent it from being impossible.

Then, with the arrival of the new leader of the company, everything seems to have started a new journey: the back-end system of transportation capacity, the revision of cms3 3,0, Dongling Group, and the business Go that is still being optimized and upgraded. In these practical projects, I slowly expanded like a withered sponge. ...

Get in touch with the new framework thinkjs, keep up with the fast pace of colleagues, use the easyui plug-in based on jQuery, improve a pure page into a decent background system bit by bit, and learn to use components that are conducive to faster work: Swiper, fileupload, etc. And understand the business logic that belongs to this team. In fact, I also want to get the handwritten code as soon as they do, but there are few bugs, the ideal is so full, but the reality is very skinny. I have to admit one of my shortcomings: I am a little stubborn. When I see new requirements, I always mistakenly think that I understand them, and lack of communication with leaders leads to some unnecessary mistakes in my work, which should be corrected in my future work, because it is really a waste of the collective.

Third, the scenery should be long and eye-catching.

I like listening to colleagues talk about their growth history, because listening to them is bright, and biased opinions are dark. If you want to be a qualified engineer, in your future work, you should improve your adaptability to new knowledge, clearly understand your own shortcomings, consult others modestly and think carefully by yourself. I remember the manager said, "A good programmer spends far more time thinking than writing code", which is what he will improve in the future. In the next 20xx years, I will also list my plans:

1, learn to communicate with leaders or colleagues in a timely and effective manner to avoid repetitive work;

2. Cultivate your overall awareness, open your eyes and focus on the team as a whole;

3, cultivate a strong heart, cultivate the ability to calm down to all kinds of emergencies, do more simple work and think more;

4. For regular expressions that have been short-board, we should study them in depth, and don't be timid when we mention them again.

3. The company program work self-inspection report

Half a year's work is over, which makes me feel great. I have been in the company for more than a year. Doing back-end development work is what I am doing. I feel full here and have confidence in myself. I can clearly know when to do something, and I will definitely adjust my mentality in the future. Through the accumulation of this half a year, I also know my own dribs and drabs very clearly. I think. The first half of the year is indeed a very substantial half year. I still have to look back. Looking back on my work experience in the past six months, I have given myself a lot of time and space. I have always wanted to enrich this job, and some things still need to be done more in place. This half year is a very good process. Although my daily work is very tense, I have been doing well in these details. This aspect still needs to be carefully considered. These six months have really touched me a lot. I always hope to do things well at this stage in a good state. There have been many breakthroughs in the past six months. I feel that there are some things to be taken seriously. There is no doubt that I want to enrich myself. No matter what I do, there should be such a process. Some things are just a slow process. In the past six months, I have developed a lot of things and my work has reached a very tense stage.

I will also constantly improve my ability in all aspects. No matter what I do, I should have this attitude. Besides work, there are many things that need to be accumulated a little. I will let myself continue to do this job well, and I will continue to play a good role no matter what the environment is. There is no doubt about it. I need to think about this. I can see some of my shortcomings. There are still some things that need to be corrected in the past six months. I believe these things can be adjusted in future study. I am very grateful for the dribs and drabs in the past six months. Some things take time to transition. I need to cheer myself up. I know where my shortcomings are. I should think seriously. I still have a lot of things to do in this regard. Looking back on my shortcomings in the past six months, I think I need to further adjust my mentality in this regard and correct my own shortcomings.

I will definitely think about these details in the second half of my work, which is a very good process for me. I believe I can handle the related work well, and I can further adjust my mentality in this respect. I'm very touched by my work in the past six months, and I will definitely continue to work hard.

4. The company program work self-inspection report

I have been working as a programmer in the company for more than a year. During this year, I learned a lot. Everyone grows up in constant summary and perfects himself in constant examination. In this year, I also completed my work in a down-to-earth manner in summary and inspection. Now I will summarize the work of this year as follows: 1. Ideological aspect:

In strict accordance with the qualities that a programmer should possess, I am self-disciplined, dedicated, responsible and enterprising, actively and conscientiously study professional knowledge, have a correct working attitude, be conscientious and responsible, obey the company's arrangement, actively cooperate with all my friends to improve the ERP system and work hard.

Second, the work:

Love your job, be able to treat every job correctly and seriously, be dedicated to your job, serve everyone enthusiastically, seriously observe labor discipline, go to work on time, make effective use of working hours, stick to your post, and work overtime on time if necessary to ensure that the work can be completed on time. In the past six months, with the goal of doing better, I have cultivated a sense of innovation and successfully completed the following duties:

Cooperate with quanu to develop and improve SRM system

Independent development of Quansap log maintenance system.

Third, there are shortcomings:

With the help and advice of company leaders and department leaders, my work has been greatly improved. Of course, I still have many shortcomings, such as simple and immature thinking in dealing with problems and impatience at work. I need to learn more professional knowledge to improve my work level.