Years of Software Development

when I went to school, I learned software engineering. I think I learned well, at that time, the best thing to learn was c ++ and the data structure, every day, we need to complete various C ++ questions and algorithm Questions left by a bunch of instructors, even the system structure should be programmed using C ++. At the end of the period, a bunch of C ++, software engineering, database jobs, and small jobs should be completed.
at that time, the most rewarding task was to complete an algorithm question that was not completed by many people around you, then I proudly claimed that I have compiled the statement _ ^.
the longest task is the big job of Software Engineering: A library management system built on J2EE, for good looks, I also downloaded various templates and JavaScript files from the Internet and tried them one by one. One of my colleagues said that your colleagues in the same group showed up on your big homework, so I think it's beautiful to bubble up...
the fastest job to complete is the database's big job, 2 days to analyze the demand, drawing the E-R, write the statements for Data creation, table creation, index creation, view creation, stored procedure, and trigger, and complete the document, then, we use J2EE to compile the Program in one day, which is a proud ^_^

During the internship, I first started a company that was the earliest in China to do PLM. A doctor took me and another student and made some simple work. net training, and then the two of us completed a small Asp.net program together, I was pulled to the PLM project team for development, and my classmates did tests in several projects. At that time, there was a new kind of momentum, not afraid of tigers. I liked to argue about everything. I started my doctor to make a summary and detailed design, and then took me for development. At that time, I always liked to ask why I should do this? Isn't that good? This should not be the case here, and so on. Then I am eager to argue with my doctor. It may be because my doctor has a bad temper and always argues with him. Although he is right most of the time, but he will still patiently explain it to me until I understand that it is indeed better. The doctor was also very generous. During a debate, he found that there was indeed a problem with his design. He admitted it very frankly and asked the project manager to explain the problem and re-design it from that time, he made the outline design, and the detailed design and coding were done by me. He is the first professional mentor in my life and the best professional mentor I have ever met, under his leadership, I have completed a lot of complicated designs and coding, and that sense of accomplishment has never been forgotten. In my subsequent work, I have never argued with people that way. Maybe there is no one to argue with, because in most jobs, leaders are leaders and cannot be insulted. What I do most often in my subsequent jobs is silence.

After graduation, I successfully entered a company, became a programmer, and interviewed C ++. After the result, I made Java, and then I kept doing Java, make network applications.

The first project after graduation was to build an ERP system for well-known Japanese automobile companies. At that time, we used Waterfall Model Iteration for development. In each phase, we started from the demand analysis and then designed the project in an outline, customer validation, detailed design, test cases, coding, standalone testing, combined with testing, release, and then a cycle starting from demand analysis, each phase will take several months, phase 1 was released after several years.
At the time of entry, I started Issue 1.5. My first task was to make a detailed design and coding for the change request. It was very simple and I thought there would be no problem after I completed it. After the leader review, I would like to modify it, so he directly ran to ask what to change, and leader said, "The change is very simple, but you need to write more details in the document, let the development know, and immediately know where to change it, it also indicates why, who changed it, and when it was changed,CodeWe also need to mark these words. I asked why to add these words, and the leader said "convenient". At that time, it was not clear what the meaning of the two words was, and I couldn't figure out where it was convenient. However, in the next three years, let me understand why the leader says "convenient ".
It may be based on my seriousness and ability. A month later, the leader threw me a page of Japanese paper, telling me to write a requirement. I don't know much about Japanese. I can even guess that I have a rough idea, then, I took the paper and ran to the leader to confirm the requirement. The leader gave me a bunch of demands mentioned and not mentioned in the document, I started my first Requirement Analysis in English. At that time, there were only a few Chinese people who could speak Japanese. We wrote English design books to confirm with the Japanese, then, confirm the demand analysis with leader and Japanese, and then make a brief design. At this time, the Japanese asked us to use VBA for this module, which is separated from the ERP system of J2EE and made separately, I have never heard of VBA, let alone it. So I started to write design books, download files, learn VBA, search for problems, and ask questions in the Forum. At the completion of the detailed design, I have already tried out the basic functions. After the leader sees it, he says that VBA only understands it now, so design, coding, and standalone testing, you can do the test and related servers together. So through this module, I have gone through all the procedures of the waterfall model, and finally connected the user manual, and Linux and FTP Server SETUP manuals are all completed by me. After the release, the customer did Acceptance Tests and did not detect bugs. Leader was proud to say that we achieved zero bugs.
After that, I gradually took over more and more jobs and became the main programmer in the group. I had to work overtime as long as I had to release the program. Sometimes, on the day of release, the corresponding emergency tasks were handled overnight and completed accordingly, I can leave after the customer confirms that there is no problem. More than a year later, when leader was about to leave, I became the one who took over from leader. At that time, leader was very tired. When it came to demand, it was necessary to determine the feasibility and review all people's design and development achievements, ensure that everyone's design and development are correct, because it is a secondary development on the original system, so each design must ensure that it cannot affect the original system, consider concurrency, consider efficiency, and so on. If a bug occurs after the release, we should grade the bug, and the system interruption and system crash are all level-1 bugs, which are absolutely not allowed to occur, fortunately, in the past three years, we have never had such a bug. Every time a bug occurs, we need to explain to the customer who caused the bug and the steps, so we try to reduce bugs as much as possible. Although we cannot eliminate bugs, we spend a lot of time designing and testing.

At that time, I often worked overtime and had the energy to work overtime. However, after a few years of work, I didn't have that good physical strength to work overtime. Now I have to look at whether the company needs to work overtime frequently.

After I left, I arrived in Shanghai. The air in Shanghai is much better than that in Beijing. It was just in the rainy season that it rained heavily every day, but it was not as cold as it was when it rained in Beijing. I ran around in the rain for an interview. I accidentally went to a training institution and asked me to be a lecturer. My sister said that it was good for a girl to be a lecturer, so she became a software lecturer.

When I first got in, I wanted to be a lecturer of phase III, mainly teaching J2EE, Oracle, and other software factories. But before the phase III was started, I first brought the C language, and most of the students had no computer base, some people won't even start the system. In order to help them learn, I will get courseware, get a lot of instances, and prepare lessons every night, then, each part will be presented to them by directly typing the code in the class. The most common thing in the past is copying and pasting, but in order to let the students understand what I'm talking about, every time I press the code on the keyboard, I will not copy or paste it. Next, I started the third class. I went to the third class. When I was promoted to the third class, I asked which class I was teaching and hoped to attend the class. At that time, the principal will hold a meeting every month to talk about the school, about which sales are doing well, which is doing the worst, and the worst three times in a row will be dismissed and met once, the principal said he would honor the best lecturer. He said he did not know the lecturer, but the students spoke highly of him ...... Then, I heard my name. The moment I took the prize, it was really exciting and exciting. After that, I became a gold medal lecturer in the school and the director of phase III, ren Mingshu has been in school, maybe still, huh, huh. The person in charge of phase III shall train lecturers of phase III, trainees, trainees, lecturers, software factories, etc. They shall prepare courseware and lessons at night, and be busy every day, if you want to go to bed for a while, you may suffer from serious sleep insufficiency. To save money, the school does not want to hire more people.

More than a year later, in order to be healthy, I finally proposed to leave, leave the podium, and leave the students I love.

After a while, I started to look for a new job, just in time to catch up with the economic downturn. I did not reply for one or two months. Later, a headhunter introduced me to a foreign company, however, he said that because I have been working in Java for less than six years, I can only recommend a job at the lower level. After the interview, I have been on duty until now.

Here, I am no longer an important person in the previous project. The most important thing here is language, not technology. Unfortunately, my language is far from excellent. I am a normal codenon here, but I don't need to work overtime frequently. Here, I met my husband.

Maybe one day I will leave. After all, everyone hopes to show their strengths and be valued by others, but I hope that when I leave, where I am going, it can be a long-term development, or I have found a better path for myself.

What an old code farmer can do is to learn and learn all the things we need: language, communication, and technical skills.

Sometimes it is a kind of achievement to review what we have learned.