June 8, 2014 completed the "Seven years of work", the primary school graduation ceremony has not begun, junior high school first grade end has arrived.
On the middle school did not transfer school, continue in Sonoscape, continue to record growth and harvest.
1. Harvest 2014.06 ~ 2015.06
This year, the main focus on team building, standardized development, the regular code was forced to put aside.
1.1-Part SVN library
Since March 2014, the department has set up the SVN repository. Management Department General Information: onboarding, training ppt, product line, department meeting records, daily document module, project management, new guidance, work plan and Summary, assessment records, personal work directory.
The main purpose is to share the information in the Department, so that the new people have information for reference, to quickly understand the status quo, so that the elderly have a place to show the results, expand influence. Another purpose is to manage the results of work outside the code base and Project library. To do with the objective assessment of data, the process of disclosure, the process is generally fair, the results are broadly fair.
1.2 Technical Organization Direction
2014, the number of software developers close to 30 people, in view of the maturity of personnel to improve, the original project grouping way is too rough, and then adjusted to the technical direction of the group: requirements, project management, software applications, software Foundation, software applications, software based on the subdivision of two or three groups, each group of people, easy visual management.
In the second half of the year, with the responsibility of the authentic Demand department expanded, the software part of the demand for personnel, output to the demand department; In early 2015, our project management team leader, also exported to the project Management department as the head; Before 2013, there are output algorithm personnel to the system department, the bottom software personnel output independent for the General Software department. Software for other departments to output the counterpart, these colleagues in the more professional departments have better development, software development department more purely focus on the application software, everyone win.
2015 also introduced a few senior software personnel, more than 40 personnel. The technical direction is fine-tuned as follows: Application, basic image, application is subdivided into 4 groups, base image is subdivided into 3 groups. Each group 5~7 person, have one or two senior engineer as leader. Strengthen the team leader of the project, the Department's responsibility requirements, the group, platform-based construction, put in the team responsible for improving self-requirements; daily through the improvement of weekly plan, personal diary, weekly communication, to carry out the team's daily work.
At the same time, the software testers, also pull into the software family together. Apply software development of the group, the daily management of the way to build a complete software team.
1.3 Automatic Tools
The second half of 2014, encountered a "software random panic" bug. The development of fewer machines, not easy to reproduce random bugs, because the new function development tasks urgent, not timely processing. Results after the release of a number of random crashes, the provisional organization of the problem. With the help of Dr Tang, the "Automated test (function call)" mechanism written by Python, the "crash dump crawl" mechanism, was solved in 3 weeks (1 weeks tool mechanism, 1 weeks of perfect upgrade, 1 weeks analysis improvement). In the 2015 release, the automatic tool smoke test, stress test, help the software to find out nearly 10 hidden crashes before release, although the release time is postponed, but avoids the more dangerous crash problem.
In the Code self-examination aspect, introduced the Gtest Unit Test tool (basic image leader "Handsome Z" Introduction, the group implementation is good, in the application group promotion also waits for time, because our design sucks, the UI and the logic coupling degree is too high); introduced the Cppcheck to do static check (application Leader "H elder brother" introduces, Find out a lot of basic programming problems, now too many novice); introduced the code line number calculation tool Cloc (Dr Tang introduced, replaced the script written by his shell), introduced the SVN statistical tool STATSVN (engineering F introduced, can be the project file, SVN submission to do statistical analysis). My contribution is in the server, wrote the shell command, with Crond, SendMail made automatic report sent to the mail.
In addition, the introduction of the Redmine tool for development task management, collation process, SOP, improved configuration and properties, started trial in August 2014. The original plan was to manage all the development tasks, and the task breakdown was less than 1 weeks; later adjusted to manage the project function point tasks that can be verified (task time is not mandatory, more detail tasks are managed in the weekly plan), and the testers are added to the task (this year the plan is to join the needs and really achieve the same three).
Also tried the Web Auto build Tool Jenkins (formerly old partner J introduced, but follow up because the task was tight and did not follow up).
1.4 4th Level Process
2014, after an external review of the baptism, the company up and down the process, standardization awareness has been strengthened. The project management department began to improve the process by improving the 1 and 2 levels.
In the past, many small processes or SOP:CVS operations, software release releases, task management processes, defect management processes (assistance), software Requirements Specification review processes (review assistance) were organized and promoted, mainly within the scope of development, or in small areas. After the increase in personnel, in addition to the implementation of the bottom of the need for processes, but also need a higher, across multiple professional, or multi-tasking 3, 4-level process.
Product projects, we are "user/market-driven research and development", in software version development, according to the scope of resources commitment, progress, quality, to "deliverable/test-driven development." So in 2015 the main push was a "software version development process". There has been a "software development process", but the document is a document, the actual operation is real, no connection, this experience, more practical considerations. The following is an introduction.
* Upstream and downstream relationship: Software version development process, located in the smallest external release software products, under the product project, the professional sub-project, in modules, tasks, defects above.
* Stage: Seven stages of "requirements recognition, planning, design, development self-test, integration testing, Confirmation, release";
* Roles and Responsibilities: involving 4 Roles "version manager, demand interface person, development interface person, test Interface Person", responsibility is not described, generally understand;
* Deliverables list: Each role will produce deliverables at each stage, listing the deliverables list;
* Software version type: The deliverable list differs depending on the type of software version "registered, formal, changed, special" (only the deliverables are cropped and the process is not cropped);
* Deliverable Type: The deliverable type is divided into "registration must, project must, version requirement, process record".
Now do the preaching, have written by the previous problems tortured needs, development, test colleagues, very interested, willing to try. Effect how, wait for the second half to verify.
2. Experience the lessons
A year flash the past, take some time to do a stage to learn lessons, it is very worthwhile.
2.1 Work
Major time spent in work on daily improvement, there are many gains.
2.1.1 Principles
The basic principle of doing good work is "positive initiative", other statements have "attitude", "self-drive", "Passion", "spontaneous combustion" and so on. In short: give you less money (or short-term money), and you will be willing to do the same (for a longer period of time, of course).
2.1.2 Mode
Last year summed up a few lessons: "Values", "starting from reality, achieving goals", "documentation, continuous improvement", "process supervision, results management" is actually the mode of work. A few additions this year:
* "visual deliverables, third party audits"
We show our contributions, abilities, attitudes, and so on through results. In the east came a beautiful woman, indicating in the "Yan value, figure, posture, clothing" and so on one or a number of items have been recognized; The West came a macho, indicating in the "chest muscle, abdominal muscles, brachial two head muscle, the brachial three head" and so on are appreciated. Since it is the result, if made easy to identify the user, the recognition is higher, such as 张丰毅secret, in the "Chibi" wearing clothes, we think it is the elderly, in the "Real Man" in a topless, can defeat the soldiers. Visual deliverables, not through their own boast, but through the 3rd party Audit show, the effect is better and more convincing to the user. Or 张丰毅secret example, in the "Day up", batting an eye do a number of pulley exercises, we have been worshipped as the new vigorous God.
Do we write code that has been promoted to a software PRODUCT module + instructions for delivery? Has the user after use, through the word of mouth to advertise for us? Take a closer look at the reality, how many of you are not aware of the internal implementation, but you are considered to be a third-party audit evidence of the ads to conquer, approved products? How many of these products have third-party audits displayed? When shopping, think more, can see some social common behavior.
* "Promotion practice should be process-based, templating, platform-based, it-based"
Since ancient times, we have re-analysis, re-theory, and light implementation, light practice of the tradition, which in the industrial society, Business Society is a fatal flaw. The survival period, the practice first, survives is the hard truth, the development grows up, must be the thought, the action unification, the theory practice unifies, otherwise will become the discrete empty skeleton, or the fat cannot stand up. This requires the middle-level, grassroots backbone of the company's strategic landing implementation, promotion and improvement.
From the training Teacher's summary (Huawei came out of the lecturer), promote the practice to "four modernizations" (process, templating, platform, it): the process of the provisions of roles, stages, activities, templating to remove human dependence, platform to ensure consistency of information unity source; It reduces manual execution errors. Otherwise, the practice and theory is not easy to contact, the implementation of many human factors, will cause "insufficient practice, prove that the theory is not", to obtain "This method is very good, but not suitable for our company status" conclusion. Has anyone in your company come to this conclusion? We have, I believe most of them have.
2.1.3 Practice
Practice is the only criterion to test truth. Deng Xiaoping put a basic principle of social survival, rose to the theoretical height, and get everyone's worship. From a certain point of view, we have to ignore the importance of practice, only to point out that the "truth" feel bluntness? Xiaoping said the right, nothing else to say. A few practical experiences are outlined below:
* Understanding Consistency
Brooks, author of the Myth of Man and month, puts forward the term "conceptual integrity", which explains why the maximum delay of a complex system is difficult for a long project person to achieve. In our project development, constantly repeating the "understanding of consistency" caused by the progress of delay, risk out of control, poor quality, in fact, from the project personnel point of view, has been working hard, but the direction is wrong.
Before doing things, take the time to discuss the scope, quality, schedule, risk, resources and other elements of the project to agree, and written, for the subsequent improvement is necessary.
* Execution Details
Wang in particular wrote a book, "details determine success or failure," with a large number of examples to describe how the details of the success of a little stolen. The point at which details determine success or failure may have a "butterfly effect" at an extreme angle, and many companies survive by responding quickly. But do not pay attention to detail, can not develop to high-end, it is impossible to continue to develop, because the high-end is a detailed composition.
Work, a detailed composition of our daily tasks, do not pay attention to detail does not prevent you to become a senior engineer, grass-roots cadres, but the long-term accumulation, a small error, will prevent further development.
2.2 Live
In the last 3 years, the typical "work-centered", most of the spare time also directly, indirectly contributed to the work, the wife owes a lot. Remember only the following points:
Swimming
Before the lady can not swim, I will only be the first time in the water on the dog planing. My wife's colleagues often go swimming, so we also bought entry equipment, to Shenzhen Bay Sports Center to learn swimming (there is no excuse to say that the equipment is poor, poor environment and can not swim). To this year altogether swam 10 cretin, the lady breaststroke basically can swim 25 meters. The learning means is watching video, holding breath, floating, kicking, paddling, breathing and so on.
Learning car
Before the lady can not ride a bike, I will only ride (on the bus can still get on the bus). Spring Festival to Wal-Mart to buy New Year's Day, the lady complained that there is no fresh feeling, so bought a bicycle, during the Spring Festival has a pastime, in the parking lot practice (cars are not a few, is suitable for cycling), Practice 4, 5 times, the lady has reached my level, can ride away (the middle fell several times, One of them broke the rear brake knob (the handle is plastic, the quality is general).
2.3 Personal Growth
Shenzhen Shekou has a slogan "Empty talk endangers, hard work hing bang", which is our guidance and warning, but also this year's self-growth point, big suggestions less, the practice of the post more.
Some good experience, in other successful companies have successfully applied, we read books, training also feel very practical, but applied to the company this position will not be smooth sailing. Are we still willing to endure improvements or revolutions, like children, to be afraid of embarrassing mistakes, to imitate new ways of learning new ideas, and to do better in this post?
3. Outlook
The beginning of the end, no summer vacation, followed by the start of second day work process.
Again to the annual entrance examination of the season, a variety of guarantees for the success of the program has been innovative. Every year at this time, write a year of summary, very good.
Eighth year of work
