Ten years of wind and rain, the growth path of an ordinary programmer (E)

Ten years of wind and rain, the growth path of an ordinary programmer (E)

author demon birth
date 2019.06.09

Growth, choice and lose (on)

I. Introduction: The Evolution of Life

Between 14 years to 18 years, I have experienced the joy of life, sad funeral, marriage, death of children, the grandfather, Old Zhao died.
On the individual positions from project manager to head of development, ashamed yes, yes Zhao sick leave was given me this opportunity.
The project has experienced in the past few years, after the core collection, management decisions, Kim Sam transformation, data migration, big data development, the tax police and other exchange programs.
Project types OLTP, OLAP, have to take over maintenance, there is reconstruction, there is zero-based.

Which involved the technology stack I witnessed the company's evolution from ancient to modern times:

• ORM from datawindown, ormap to ibatis, Mybaits
• From the self-development framework sm @ rtFrame to spring, springboot
• Strapping Tools from ant to maven, gradle
• HTC from distal to render freemark, jQuery + layui, antdesign
• Oracle11g stores data to 12c, mpp, noSql, hadoop, elasticsearch
• Processing data from the kettle, ogg to sqlloader, kafka, flum, mapreduce, storm, spark
• The system architecture is separated from the perpendicular to the SOA services and integrated service to the micro
• Service Management from ESB to the API gateway

So, in these years, mainly done? I learned something?

Now think about it, it seems most of all remember. Just pick a few things that impressed me most, for example.
Positive, there are counter-examples.
In summary, the lesson is to get it.

Second, the growth: obtain and Lessons

2.1 planning and execution

Consciously involved in developing work plans, decomposition milestone plan and weekly plan, a correct understanding of the different team in each person's ability, reasonable arrangements for personnel plan and 跟踪执行a.

Why recommended weekly schedule?

Why talk about here is the weekly schedule, rather than day plan, monthly plan? By day plan too oppressive, easy for developers thinking tension , daily tracking is also a waste of time; while more than a week plan is too loose, it will lead to unpredictable risks in the middle, increasing the difficulty of adjustment.

How different members assigned reasonable workload?

In the work plan, a lot of technical personnel to do after the team leader has a common problem, always with their ability to measure others, resulting in unpredictable risks.

Why must Tracking Program?

After planning for the implementation of the plan you will need to keep track of, monitoring before and after the change, the estimated risk. Summarized plan late on Friday, but that does not mean not to say in the middle, implementation of the plan the best time to be at the track on Wednesday, for the developers do not have relatively large pressure, but also timely communication of risk can not be completed on time , to adjust.

Make complaints

• Standing will be
  in the best practices of some companies, but also includes early (late) standing will, in fact, I was somewhat despised, because the progress of staff within a teamleader even ten people can not keep up, a little bit from the masses.

• And head butt
  in the job promotion, some people seem to head butt will be mastered, forget ever Tucao people in the system.

get

In tracking each week plan, limit the ability of team members to find out, give team members a little bit but not too much more than the amount of work.
On the progress tracking milestones in the project schedule and staff we need to grow, to make a balance between the intensity of work (overtime), internal test capability team leader of the tour.
After the swap position, sometimes you will understand why the leadership of the previous Tucao piece of have this kind of arrangement.
But, do not forget the early heart, temper forward.

lesson

If there is lack of resources, do not back yourself, such as the members of the poor of the point, the line a little technical risk, especially situations involving coordination of external resources, must be promptly reported, fight for resources.

Do not think what is this, I do two hours of overtime to get. First, the exhausted themselves, and second, there is no credit elbow grease.

Things under pressure in the case of the hands of the event have not been resolved, resulting in the progress of frustration, loss of trust is the company's money, leadership, and team morale.

2.2 Individual capacity building

To-back, to service deployment, business communication systems from the development of the data model from requirements to design, project from pre-project to project. Unwittingly became a so-called full-stack engineer.

get

The breadth and depth of expertise to enhance what?

Span

• Language
  JavaScript, java, python
• The front end of
  the table web, mobile, H5, applets;
• Delivery
  CI / CD concept and tools, ant / maven / gradle
• Service container
  weblogic, tomcat, nginx;
• linux system
  redhat, centOS, Ubuntu
• Virtualization
  OpenStack, KVM, VMware, docker
• Test
  cases, planning and reporting with, smoke, cover the back, artificial, automation, functionality, security and performance
• Performance
  CPU, memory and IO, process, thread and pipe, QPS, TPS and PV, pressure, load, stability

Depth
on the depth of my biggest upgrade should be Oracle, which also benefited from the sharing of our technology Zhao, remember that sharing also recommended a book - "receipt, not just oracle".
Mastered example, table spaces, user, table design, index optimization, system tables, redo, flush, DBF file and IMPDP / EXPDP, AWR reports oracle of theory and practice and be related tools, such as at this time to go in mysql and other structures and unstructured database, easy.

What have you learned operational capacity?

After the declaration, collection, collection and management of core business registration, invoices, and other instruments, and master some metadata, data warehouse, data processing, data quality, data analysis, the concept of design as well as some related tools.
Communicate with customers able to say what time the little bar.

Some project management soft skills

Participate in and led the project pre bidding, project to project initiation, execution, on-line, operation and maintenance and a series of project activities.
Communication from the very beginning of the project the intention to collect the original requirements, to analyze writing requirements specifications, interface design prototype, followed by the preparation and audit of the tender specifications, project approval processes with the company's audit, project midway code and documentation audit, evaluation of the project and other security front line, strengthening security and so forth.

• Productivity tools

Here are a few specialized tools used to say it touches down, office2016 not to mention the suit.
Interface prototyping recommended Axure + antDesign,
processes and architecture design is recommended online tools ProcessOn (local is visio, PPT),
mind mapping and team collaboration can also be used ProcessOn (local is xmind + excel),
data model design and I using a processOn (you can use local powerdesign).

Forgive me, became ProcessOn brain residual powder, easy to use addictive (laughs).

Make complaints

Sometimes very difficult to go to management posts have the energy to continue to do technology, if there are pieces of technology to do the heart, attention to open source, to keep sensitive technology.

lesson

• Prototyping

Prototyping is very important!
Prototyping is very important!
Prototyping is very important!

The so-called a picture is worth a thousand words, and sometimes customers do not even understand what they want, always said, "you do first edition came out to see it."
Ignorant force yet?

Before confirming three requirements with the customer, do not do, do not do, do not do!
Most of the pressure then do not really invest human began to dry.
Unless, you are a political task.

• Coordination and management

For customers, the higher third-party management to be good, timely synchronization related information, be sure not to let the stakeholders to generate information gap, resulting in deviation from the target and progress.

For customers, if the schedule variance to get in communication understanding. There are no problems to report, is a bomb out of trouble, why not Diao? Points did not mind it?
But also to have communication skills, I lackluster in this regard, because it is often not enough to speak of art, is Diao.
And every week should meet with customers, business demand for demonstration and validation in progress, so that customers have a sense of participation. In particular collaborative project involving multi-sectoral enterprises and units, the customer does not participate in a sense, will not take the initiative to help you solve the problem. You take the money work, should not it?

For when the superior, timely reporting of progress and risks, some problems can not be solved, do not fill in the blank to a higher level, but multiple-choice questions. Even when no problem, we must find some multiple choice questions from the project to the leadership to do something, so that the leaders have a sense of participation.
But things within the project, in fact, as the parent should as far as possible not to leapfrog to intervene. Chiang Kai-shek is so lost in the country, is not it?
Ren said, and cut off the top of the hands and feet, cut ass middle, cut off the head of the grassroots.
That said, what does this mean? Senior leaders do not themselves, find fault, leapfrog work.
In my previous company, there is a director of what is good, is too hands-on work, exhaustive, lead project manager directly subordinate became a project assistant, there is no power. Do more wrong, listen to orders like a thing, right?
Do middle for their own small groups intend to do, regardless of the interests of the company.
In my experience of several projects, some research and development, testing, operation and maintenance of the leader were wearing their own set of small thinking, not goal-oriented project, but they are not back to the pan as a guide. In this way you can do well?

For third-party, not to mention the upstream companies, mostly in collaboration outsourcer company should promptly close watch on the progress, need each other to provide project deliverables according to milestone plan, and be a real demonstration of the system in the middle. Otherwise, you as a total package, the customer is not Diao subcontractors, but you. After all, the tender, the money is yours ah.

2.3 Ability Team

Weekly technology sharing, code checks bi-weekly, monthly project summary. Good working atmosphere, friendly relationship between colleagues, pleasant working mood.

In fact, a few years of work, the most proud of is not the number of completed projects, but you can learn after something, to share in his team's brother, after an item master, quickly He threw brothers, and so that they can also work independently.

I never wanted to do what can not be replaced, if a person can not be replaced, so much risk means the company.

Also I do not want people to think outside the box to support the company's waste, as from the day the company will go out uncompetitive.

get

I am proud that we set out from the project, whether it's corporate headquarters or elsewhere in the project team, able to work independently and soon became the core backbone.

I am proud that during my project manager, you grow up fast, and very deep feelings. In 18 years, we have one after another from the company after leaving (I was 17 the second half of the outgoing project manager), we have each become a different company's team leader, still occasionally get together and talk and drink, I miss the year.

lesson

In fact technology sharing code inspection summary of these projects is not well implemented. In addition to prestige project managers do not have enough people to monitor implementation. Some things a drag, then let the matter rest.

On membership, each colleagues also have their own edges, to ensure the quality of the job done on the line, no need to ask to love each other. Forced to bridge, but less happy.

Third, the choice: Management and Technology

In a company / team / project group, with some qualifications, the post is to continue to do technical or management into the post?
Sometimes forced into management posts or passively how to do?
To a certain age, you can continue to do technology?
To find fault with or affected by the project manager do?
Technology research and development, technology management, project management, how to choose? Which for their own?

12 points, today I will never finish, the next write it.

Fourth, the loss of: Life and Survival

Ibid.